Skip to main content
Glama

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-mcp

The environment variables are the same, so your keys keep working.

Related MCP server: MCP-DOC-MID

Available Tools

3 tools
diff_openapiA
Read-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_schemaA
Read-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_openapiA
Read-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

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    All three tools follow a strict verb_object pattern: validate_openapi, diff_openapi, validate_json_schema. Predictable and consistent throughout.

    Tool Count4/5

    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.

    Completeness4/5

    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

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables 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
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      26
      Apache 2.0