Specwise
Specwise lets a coding agent validate API contracts and compare OpenAPI versions.
Validate OpenAPI 3.0/3.1/3.2 or Swagger 2.0 documents, returning all errors with JSON Pointer, line, and column, plus lint warnings.
Diff two OpenAPI 3.x documents from text, files, or a file against a git ref, classifying changes as breaking, warning, non-breaking, or info with a semver suggestion.
Validate a JSON Schema against its meta-schema and optionally validate data against it, with instance/schema paths and line info for text input.
Supply documents as YAML/JSON text, JSON objects, or local file paths; local files are read only when passed by path.
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., "@Specwise diff 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.
hybridforgelab-specwise-mcp: moved to bytestay-specwise-mcp
This package has moved to bytestay-specwise-mcp. Hybrid Forge Lab is now ByteStay.
This last version only installs bytestay-specwise-mcp and forwards to it. It prints a one-line notice on stderr and gets no more updates.
Switch
Replace hybridforgelab-specwise-mcp with bytestay-specwise-mcp in your MCP client config:
"command": "uvx",
"args": ["--from", "bytestay-specwise-mcp", "specwise-mcp"]Or with Claude Code:
claude mcp add specwise --env RAPIDAPI_KEY=your-rapidapi-key -- uvx --from bytestay-specwise-mcp specwise-mcpThe environment variables are the same, so your keys keep working.
Related MCP server: MCP-DOC-MID
Links
Package: bytestay-specwise-mcp
Source: Bytestay/specwise-mcp
Specwise API: specwise.bytestay.pt
Available Tools
3 toolsdiff_openapiARead-onlyIdempotent
Compare two OpenAPI 3.x documents. Each change is breaking, warning, non-breaking or info; breaking says
whether any is breaking, and semver suggests the version bump.
Typical use after editing a spec: revision_path="openapi.yaml", base_git_ref="main".
Inputs: base, revision, base_path, base_git_ref, +1 more.
validate_json_schemaARead-onlyIdempotent
Check a JSON Schema against its meta-schema and, if given, validate data against it. Every error has the instance path, the schema path and, for text input, the line.
Inputs: draft, schema, instance, schema_path, +1 more.
validate_openapiARead-onlyIdempotent
Validate an OpenAPI 3.0/3.1/3.2 or Swagger 2.0 document. Returns every error (not just the first) with its JSON Pointer, line and column, plus lint warnings.
Inputs: spec, spec_path.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool targets a clearly distinct operation: validation of OpenAPI, diffing of OpenAPI, and JSON Schema validation. While validate_openapi and validate_json_schema both validate, the domains (OpenAPI document vs. JSON Schema + data) are explicitly separated, leaving no realistic ambiguity.
All three tools follow a strict verb_object pattern: validate_openapi, diff_openapi, validate_json_schema. Predictable and consistent throughout.
Three tools is slightly thin for a spec-tooling server, but each is a distinct, well-scoped capability with no filler. A 3-tool set is on the low edge of the ideal band but defensible for a focused lint/diff utility.
The core spec lifecycle for validation and comparison is covered, including breaking-change detection and semver suggestions. Gaps exist around formatting/bundling or schema conversion, but agents can work around these; the surface is coherent for a focused toolset.
Maintenance
Related MCP Connectors
Detect breaking changes, generate changelogs, diff, and validate OpenAPI specs.
Validate OpenAPI and JSON Schema, convert specs, curl to code, JSONPath, and free test data.
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
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI clients to validate OpenAPI specs, compare versions, detect breaking changes, and generate changelogs.4MIT
- FlicenseAqualityDmaintenanceEnables 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 agents to analyze OpenAPI contracts for deterministic integration risks, plan auth, sync, action, and webhook candidates, and diff contract versions for likely breaking changes through read-only tools.MIT

apidrifterofficial
AlicenseNot gradedqualityBmaintenanceEnables agents to plan and run requests from OpenAPI documents, verify live API responses against specs, diff spec versions for breaking changes, and snapshot or compare MCP servers including tool descriptions.26Apache 2.0