MCP Server Generator
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_toolsA | Search for relevant tools by query with progressive disclosure This tool implements the progressive disclosure pattern - allowing you to discover tools without loading full schemas upfront, saving context window space. Args: query: Search query (matches against name, description, categories, use cases) detail_level: Level of detail to return: - "name": Just tool names (most context-efficient) - "summary": Names + descriptions + categories - "full": Complete information including use cases and detailed descriptions Returns: JSON string with matching tools at requested detail level |
| get_tool_infoA | Get information about a specific tool with progressive disclosure Args: tool_name: Name of the tool to get information about detail_level: Level of detail: - "summary": Name, description, and category - "full": Complete information including use cases and full description Returns: JSON string with tool information at requested detail level |
| get_best_practicesA | Get MCP server development best practices Args: topic: Optional specific topic (e.g., "progressive_disclosure", "tool_design", "control_flow", "security", "state_management", "testing"). If None, returns all best practices. Returns: JSON string with best practices information |
| get_implementation_guideA | Get step-by-step guide for implementing MCP servers Args: step: Optional specific step (e.g., "setup", "implementation", "testing", "deployment", "integration"). If None, returns overview of all steps. Returns: JSON string with implementation guide |
| generate_claude_commandA | Generate Claude Code command files for guided MCP development Creates .claude/commands/ directory with slash command files that guide users through MCP server development using this generator. Args: command_name: Name for the command (e.g., "mcp-generate", "mcp-help") command_type: Type of command to generate: - "mcp_generator": Guide through MCP server generation workflow - "best_practices": Provide MCP best practices reference - "implementation_helper": Help implement generated MCP server - "custom": Use custom_prompt for fully custom command description: Optional description for the command (auto-generated if not provided) custom_prompt: Required if command_type is "custom" output_dir: Directory to create command file (default: .claude/commands) Returns: JSON string with generation result |
| generate_mcp_serverA | Generate a complete MCP server project with dual-mode architecture This is the main generation tool. Consider using search_tools or get_tool_info first to understand the full workflow, or use the generated Claude commands for guided assistance. Args: project_name: Project name (e.g., 'my-mcp-server') description: Project description author: Author name author_email: Author email tools: List of tools this MCP server will provide. Each tool should have: - name: Tool function name - description: What the tool does - parameters: List of parameter objects with name, type, description, required output_dir: Output directory (default: current directory) python_version: Python version for testing (default: '3.10') prefix: Package prefix - 'AUTO' (detect from git), 'NONE', or custom string (default: 'AUTO') Returns: JSON string with generation result including success status and project path |
| validate_project_nameB | Validate a project name for Python package compatibility Args: name: Project name to validate Returns: JSON string with validation result |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/hitoshura25/mcp-server-generator'
If you have feedback or need assistance with the MCP directory API, please join our Discord server