oasdiff

Detect breaking changes, generate changelogs, diff, and validate OpenAPI specs.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
100%
Calidad de los nombres
80%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~715Tokens (definiciones de herramientas)
~785 BTamaño de respuesta típico
Impacto moderado en la atención (0.56% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "oasdiff": {
      "url": "https://api.oasdiff.com/mcp"
    }
  }
}

Puntos de conexión remotos

https://api.oasdiff.com/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (4)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟡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).

Esquema de entrada

{
  "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).

Esquema de entrada

{
  "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).

Esquema de entrada

{
  "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).

Esquema de entrada

{
  "type": "object",
  "properties": {
    "spec": {
      "type": "string",
      "description": "the OpenAPI specification to validate, as YAML or JSON"
    }
  },
  "required": [
    "spec"
  ],
  "additionalProperties": false
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada4 herramientas
verificadoversión no registrada4 herramientas