spec-drift-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPEC_DRIFT_ROOT | No | The project root path that serves as the base for spec source paths. Defaults to current working directory. | |
| SPEC_DRIFT_SPECS | No | The directory where spec files are located, relative to the root. Defaults to 'specs'. |
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 |
|---|---|
| list_specsA | List every entity spec (the single source of truth) and the source symbol it governs. Call this first to see which types are spec-controlled. |
| explain_specB | Return the full field-level spec for one entity so you know exactly what to implement before writing code. |
| check_driftA | Compare the spec against the actual TypeScript source and report every drift: fields missing in code, extra fields absent from the spec, and type mismatches. Run this before committing, or right after editing a spec-controlled type. |
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 clear, distinct purpose: listing specs, explaining a spec, and checking drift. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern with underscores: list_specs, explain_spec, check_drift.
Three tools is minimal but appropriate for the focused domain of spec drift detection. Each tool is essential and well-scoped.
The set covers the full workflow: list available specs, get detailed spec, and check for drift. No obvious missing operations for the stated purpose.