Schemadriftgate MCP

What schemadriftgate-mcp does

schemadriftgate-mcp MCP server provides a hosted service for reviewing changes to MCP tool schemas. Its purpose is to identify potentially breaking changes before an agent calls an incompatible tool interface. The service also supports approval records, compatibility receipts, explanations of breaking changes, and audit-log exports for release review.

The repository documents the hosted product rather than implementing the production service. The public MCP endpoint is available at https://schemadriftgate.clauxel.com/mcp, and the service is offered as a paid remote MCP.

How it works

An MCP client connects to the remote endpoint using Streamable HTTP. Requests use JSON-RPC and must include an HTTP bearer token in the following form:

Authorization: Bearer <token>

The token is issued through the product website after selecting a plan and creating or requesting API access. Once connected, an MCP-compatible client can invoke the service tools for drift checks, schema approvals, receipt recording, change explanations, and audit-log export.

The service exposes a registry name of com.clauxel.schemadriftgate/schemadriftgate-mcp. Its server card is published at https://schemadriftgate.clauxel.com/server-card.json.

Setup and configuration

To configure schemadriftgate-mcp MCP server:

1. Open the product website and choose a plan.
2. Create or request an API token.
3. Add https://schemadriftgate.clauxel.com/mcp to an MCP client that supports Streamable HTTP remote servers.
4. Send JSON-RPC requests with the bearer token.

The supplied material does not specify a local installation process, package command, configuration-file format, or environment-variable name. The repository is a documentation and directory-submission reference; it does not include the private production source code.

Tools and capabilities

The documented MCP tools are:

• check_schema_drift: Check for drift between tool schemas.
• approve_tool_schema: Record approval for a tool schema.
• record_tool_receipt: Record a compatibility receipt.
• explain_breaking_change: Explain a breaking schema change.
• export_audit_log: Export release audit logs.

Together, these tools cover the documented workflow of checking schema changes, approving compatible interfaces, recording evidence, investigating breaking changes, and exporting audit information.

Limitations and notes

schemadriftgate-mcp MCP server is a paid hosted service, not a self-contained local server in this repository. Production calls require a bearer token issued by the product website. The documentation does not identify specific MCP client products, provide pricing details, describe token expiry or scopes, or define the exact request and response schemas for each tool.

Unauthenticated browser visits to the MCP endpoint return a JSON error rather than internal service details. Client configuration therefore needs to support remote Streamable HTTP connections and bearer-token authentication.