Specwise
Enables diffing an OpenAPI specification against a base Git ref, such as main, to identify breaking changes between the working file and the committed version.
Validates Swagger 2.0 API definitions, reporting errors with JSON Pointer, line, and column plus lint warnings; Swagger 2.0 can be validated but not diffed.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Specwisediff my openapi.yaml against main and suggest a semver bump"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Specwise MCP server
Let your coding agent check an API contract: validate an OpenAPI document, find the breaking changes between two versions (also against git), and validate JSON Schemas and data.
The server is open source (MIT). It calls the Specwise API, which is paid, with a free plan.
You use your own key, from RapidAPI or api.market.
Every tool call is one request on your plan.
The free Basic plan has 15 requests a month, with a hard limit, so it never runs up a bill.
1. Get a key
Related MCP server: OpenAPI Contract Guard MCP
2. Add the server to your MCP client
The server runs locally over stdio with uv. Put your key in its environment.
JSON configuration (Claude Desktop, Cursor, VS Code and most clients):
{
"mcpServers": {
"specwise": {
"command": "uvx",
"args": ["--from", "hybridforgelab-specwise-mcp", "specwise-mcp"],
"env": { "RAPIDAPI_KEY": "your-rapidapi-key" }
}
}
}Claude Code:
claude mcp add specwise --env RAPIDAPI_KEY=your-rapidapi-key -- uvx --from hybridforgelab-specwise-mcp specwise-mcpEnvironment
variable | meaning |
| your RapidAPI key |
| your api.market key, used when |
|
|
Without a key the server still starts. The first tool call then explains where to get one.
3. Tools
tool | what it does |
| every error with its JSON Pointer, line and column, plus lint warnings (OpenAPI 3.x and Swagger 2.0) |
| each change between two OpenAPI 3.x versions is breaking, warning, non-breaking or info, with a semver suggestion |
| checks the schema against its meta-schema and, if given, the data against the schema |
diff_openapi takes the two versions in one of three ways:
baseandrevisionas text;base_pathandrevision_pathas files;revision_pathwithbase_git_ref. For example, after editing a spec:revision_path="openapi.yaml", base_git_ref="main".
Every tool returns the API's JSON response.
When the marketplace reports it,
quota_remainingis added: the requests left on your plan this month.Errors are explained in plain words, with what to do next:
key refused, with the link to subscribe;
quota reached, with the plans;
input the API couldn't process, with the API's reason.
Privacy
Local files are read only when a tool is given their path. They are sent to the API for that one request.
The API processes inputs in memory and doesn't store them. See the privacy policy.
Your key is only sent to the marketplace you chose.
Limits
Documents up to about 900 KiB each.
External
$refs are not fetched. Bundle multi-file specs first (redocly bundle).The diff needs OpenAPI 3.x; Swagger 2.0 can be validated, not diffed.
The server needs Python 3.10+ (uv installs it for you).
Development
uv venv && uv pip install -e ".[dev]"
.venv/bin/pytest # unit tests, no network; 100% coverage required
.venv/bin/ruff check src tests scriptsscripts/e2e_stdio.py specwise runs the server over stdio, as a client would, and calls its tools against the real API. It needs RAPIDAPI_KEY or API_MARKET_KEY.
Licence
MIT. Specwise itself is a paid API with a free plan, run by Hybrid Forge Lab.
This server cannot be deployed
Maintenance
Related MCP Connectors
Detect breaking changes, generate changelogs, diff, and validate OpenAPI specs.
Deterministic validation for AI-generated artifacts: JSON Schema, OpenAPI response, SQL syntax.
Convert, lint and generate LLM tool schemas for OpenAI, Anthropic, Gemini and MCP
Schema-aware API monitoring: diff OpenAPI specs for breaking changes, manage endpoints.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceValidates OpenAPI documents, JSON Schemas, and JSON payloads. Also compares OpenAPI specs and displays breaking changes.-
- AlicenseAqualityDmaintenanceEnables AI clients to validate OpenAPI specs, compare versions, detect breaking changes, and generate changelogs.4MIT
- FlicenseAqualityBmaintenanceEnables LLMs to dereference and query OpenAPI/Swagger specifications, search endpoints and schemas, validate payloads, extract security schemes, and generate production-ready integration code in multiple languages.8-
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to check requests against a live OpenAPI 3.x specification rather than guessing, by resolving endpoints from a docs anchor, operationId, path fragment or tag, revealing what each operation accepts and returns with $refs resolved, and diffing a concrete payload to report missing, unknown, mistyped, or forbidden fields with suggested corrections. All five tools are strictly read-only, never touching the API the schema describes, and return actionable errors with close-match suggestions.MIT