API Contract MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_ROOT | No | Default project/repository root |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apicontract_statusB | Health check for API Contract MCP. |
| apicontract_validateB | Validate a response against an expected schema/JSON. |
| apicontract_endpointsB | List endpoints from OpenAPI JSON. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: health check, response validation, and endpoint listing. There is no overlap or ambiguity between them.
All tools share a consistent 'apicontract_' prefix and use lowercase names. There is minor inconsistency between nouns ('status', 'endpoints') and verbs ('validate'), but the pattern is still predictable.
Three tools is on the smaller side but appropriate for a focused API contract utility. Each tool serves a clear, non-redundant function, and the count does not feel artificially inflated or overly thin.
The tool set covers core health check, validation, and endpoint discovery, but lacks broader contract lifecycle operations like importing, diffing, or managing multiple contracts. Agents can perform basic tasks but may need external tooling for full contract workflows.