MCP Server Creator
Server 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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-mcp-docsC | Get documentation for the Model Context Protocol |
| generate-mcp-serverB | Generate all necessary files for creating an MCP server |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| mcp-setup |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| mcp-docs |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one retrieves MCP documentation and the other generates server files. There is no overlap or ambiguity between them.
Both tool names follow the same kebab-case verb-object pattern: get-mcp-docs and generate-mcp-server. Naming is predictable and consistent.
Two tools is a minimal set, which feels slightly thin even for a focused MCP server creation workflow. However, the pair of documentation lookup and generation does cover the core purpose without redundancy.
The server covers getting documentation and generating all necessary files for an MCP server. Minor gaps exist such as validation, updating, or listing templates, but the primary creation workflow is complete.