oasdiff
Detect breaking changes, generate changelogs, diff, and validate OpenAPI specs.
사용해야 할까요
품질 및 안전성
도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.
컨텍스트 비용
이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.
설치
원클릭 설치
`claude_desktop_config.json` 파일에 다음을 추가하세요:
{
"mcpServers": {
"oasdiff": {
"url": "https://api.oasdiff.com/mcp"
}
}
}원격 엔드포인트
https://api.oasdiff.com/mcpstreamable-http할 수 있는 일
도구 목록
도구 (4)
🟡oasdiff_breaking_changes(base, revision)
Detect breaking API changes between two OpenAPI specifications. Pass the base (old) and revision (new) specs as YAML or JSON; returns the breaking and warning-level changes. Use this when the question is whether an API change breaks existing clients. Use oasdiff_changelog instead to list every change including non-breaking and informational ones, oasdiff_diff for the raw added/removed/modified structure, or oasdiff_validate to check a single spec rather than compare two. Both specs must be valid, self-contained OpenAPI (external $ref URLs or files are not resolved).
입력 스키마
{
"type": "object",
"properties": {
"base": {
"type": "string",
"description": "the base (old) OpenAPI specification, as YAML or JSON"
},
"revision": {
"type": "string",
"description": "the revision (new) OpenAPI specification, as YAML or JSON"
}
},
"required": [
"base",
"revision"
],
"additionalProperties": false
}🟡oasdiff_changelog(base, revision)
Produce a full changelog of every detected change between two OpenAPI specifications (base vs revision), down to informational changes. Pass both specs as YAML or JSON. Use this when you want the complete set of changes at every severity. Use oasdiff_breaking_changes instead when you only care whether the change is breaking (less noise), or oasdiff_diff for the raw structural diff without a backward-compatibility judgment. Both specs must be valid, self-contained OpenAPI (external $ref URLs or files are not resolved).
입력 스키마
{
"type": "object",
"properties": {
"base": {
"type": "string",
"description": "the base (old) OpenAPI specification, as YAML or JSON"
},
"revision": {
"type": "string",
"description": "the revision (new) OpenAPI specification, as YAML or JSON"
}
},
"required": [
"base",
"revision"
],
"additionalProperties": false
}🟢oasdiff_diff(base, revision)
Show the structural diff between two OpenAPI specifications (base vs revision): what was added, removed, or modified. Pass both specs as YAML or JSON. Use this when you want the raw structural changes rather than a backward-compatibility verdict. Use oasdiff_breaking_changes to judge whether changes break clients, or oasdiff_changelog for a severity-classified changelog. Both specs must be valid, self-contained OpenAPI (external $ref URLs or files are not resolved).
입력 스키마
{
"type": "object",
"properties": {
"base": {
"type": "string",
"description": "the base (old) OpenAPI specification, as YAML or JSON"
},
"revision": {
"type": "string",
"description": "the revision (new) OpenAPI specification, as YAML or JSON"
}
},
"required": [
"base",
"revision"
],
"additionalProperties": false
}🟢oasdiff_validate(spec)
Validate a single OpenAPI specification against the OpenAPI and JSON Schema rules. Pass the spec as YAML or JSON; returns the findings (empty when the spec is valid). Use this when you have one spec and want to check it is well-formed. For comparing two specs, use oasdiff_breaking_changes, oasdiff_changelog, or oasdiff_diff instead. The spec must be self-contained (external $ref URLs or files are not resolved).
입력 스키마
{
"type": "object",
"properties": {
"spec": {
"type": "string",
"description": "the OpenAPI specification to validate, as YAML or JSON"
}
},
"required": [
"spec"
],
"additionalProperties": false
}커뮤니티
증거