Specmatic MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_contract_testB | Run Specmatic contract tests against an API using OpenAPI specification |
| run_resiliency_testB | Run Specmatic resiliency tests with boundary condition testing against an API using OpenAPI specification. This enables SPECMATIC_GENERATIVE_TESTS to test how the API handles contract-invalid requests |
| manage_mock_serverA | Manage Specmatic mock servers - start, stop, or list running servers for frontend development. Supports complete mock server lifecycle management. |
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 targets a distinct aspect of Specmatic: mock server lifecycle, contract testing, and resiliency testing. No overlap.
All tool names follow a consistent verb_noun pattern with underscores: manage_mock_server, run_contract_test, run_resiliency_test.
Three tools is well-scoped for a focused server covering essential functionality without being too few or too many.
Covers mock server management, contract testing, and resiliency testing. Minor gap: no tool for loading/configuring OpenAPI specs, but core workflows are complete.