Specwise MCP Server
Related Servers
Alternatives to Specwise MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to validate OpenAPI documents and JSON Schemas, validate data against a schema, and diff OpenAPI versions—including against a git ref—to classify breaking changes and suggest semver updates.MIT
- AlicenseAqualityDmaintenanceEnables AI clients to validate OpenAPI specs, compare versions, detect breaking changes, and generate changelogs.4MIT
- AlicenseBqualityAmaintenanceLocal OpenAPI contract checks and breaking-change detection between spec versions for AI coding agents.2102 npmMIT
- FlicenseNot gradedqualityDmaintenanceValidates OpenAPI documents, JSON Schemas, and JSON payloads. Also compares OpenAPI specs and displays breaking changes.-
- AlicenseNot gradedqualityBmaintenanceEnables 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.Apache 2.0
TDQS
Scored across 3 tools
Each tool targets a distinct operation: validating an OpenAPI document, diffing two OpenAPI documents, and validating a JSON Schema. The two 'validate_' tools could superficially be confused, but the descriptions make the format boundary (OpenAPI vs JSON Schema) explicit, so an agent can select reliably.
All three tools follow a clean verb_noun snake_case pattern (validate_openapi, diff_openapi, validate_json_schema). 'diff' is used consistently as a verb and the noun portion names the artifact being operated on.
Three tools is a tight, well-scoped surface for a spec-quality server, with no filler. It is on the lean side — a couple more operations would not feel excessive — but nothing here is redundant.
The core lifecycle of 'validate my spec, compare it to baseline, validate underlying JSON Schema' is covered end to end, including multi-error reporting and semver hints. Minor gaps exist: no $ref bundling/resolution, no Swagger-to-OpenAPI conversion, and no standalone lint mode.