MCP Maker
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_mcp_boilerplateC | Creates a new MCP server project with all the necessary boilerplate files |
| create_tool_templateC | Generates template code for a new MCP tool with customizable parameters |
| create_resource_templateC | Generates template code for a new MCP resource |
| create_prompt_templateC | Generates template code for a new MCP prompt |
| save_mcp_docsC | Saves MCP documentation text directly and stores it for future reference |
| search_mcp_docsC | Search through stored MCP documentation for relevant information |
| get_mcp_doc_sectionC | Get a specific section of MCP documentation by key and section title |
| generate_doc_enriched_templateC | Generate an MCP server template with context from the documentation |
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 8 tools
Most tools have distinct purposes focused on different aspects of MCP development (templates, documentation, project setup), though 'generate_doc_enriched_template' and 'generate_mcp_boilerplate' could potentially overlap in creating server templates. The descriptions help clarify that one is documentation-enhanced while the other is general boilerplate.
Tools follow a consistent verb_noun pattern with clear actions like 'create', 'generate', 'get', 'save', and 'search'. There's minor deviation with 'generate_doc_enriched_template' using a compound adjective, but overall naming is predictable and readable.
With 8 tools, this is well-scoped for an MCP development assistant. Each tool serves a specific purpose in the workflow (template creation, documentation handling, project setup), and none feel redundant or unnecessary for the server's apparent domain.
The toolset covers key MCP development needs: creating templates for prompts, resources, and tools; accessing and searching documentation; and generating server boilerplate. A minor gap might be the lack of tools for testing or deploying MCP servers, but core development workflows are well-supported.