MCP Spec Generator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPECS_DIR | No | Directory path for specs output | |
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key |
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 |
|---|---|
| get_spec_templateB | Returns the SPEC_KIT_TEMPLATE used in the alfred-egit workspace |
| list_specsB | Lists existing spec folders in the alfred-egit workspace/specs directory |
| read_specB | Reads the content of an existing spec file (*-SPEC.md) inside a spec folder |
| generate_specA | Converts a User Story document into a SPEC_KIT formatted .md file named {hu-name}-SPEC.md and saves it to workspace/specs/. Returns the file path. |
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 4 tools
Each tool performs a distinct operation: retrieval of template, listing specs, reading a spec, and generating a spec. Their purposes are clear and non-overlapping, making selection straightforward.
All tools follow a consistent snake_case naming pattern with verb_noun structure (get_spec_template, list_specs, read_spec, generate_spec). This predictability aids tool selection.
Four tools are appropriate for the narrow scope of spec template management and generation. It is slightly thin but covers essential operations without redundancy.
The surface covers listing, reading, getting a template, and generating specs, but lacks update or delete operations for specs. Users cannot manage spec lifecycle completely, which may cause workarounds.