Skip to main content
Glama
angrysky56

MCP-Creator-MCP

by angrysky56
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

NameDescription
create_mcp_serverB
Create a new MCP server based on specifications.

IMPORTANT NOTES:
- AI sampling (ctx.sample) is not currently supported in Claude Desktop
- Use modern typing: dict, list, str | None instead of Dict, List, Optional
- Generated servers include proper process cleanup and error handling
- All generated code uses working MCP SDK patterns

Args:
    name: Name of the MCP server (must be valid Python identifier)
    description: Description of what the server does
    language: Programming language (python, gradio, typescript)
    template_type: Type of template (basic, fastmcp_server)
    features: list of features to include (tools, resources, prompts)
    output_dir: Output directory (defaults to configured default)

Returns:
    Status message with creation details and next steps
list_templatesC
list available templates for MCP server creation.

Args:
    language: Filter by language (optional)

Returns:
    Formatted list of available templates
get_ai_guidanceA
Get structured guidance for MCP server development.

IMPORTANT NOTES:
- AI sampling (ctx.sample) is NOT currently supported in Claude Desktop
- Use modern typing: dict, list, str | None instead of Dict, List, Optional
- Always implement proper process cleanup and signal handling
- Follow MCP SDK patterns for tools, resources, and prompts

This tool provides structured, deterministic guidance instead of AI-generated content.
For dynamic AI assistance, use Claude Desktop's built-in capabilities directly.

Args:
    topic: Topic to get guidance on (best_practices, security, performance, typing, etc.)
    server_type: Type of server for contextualized advice

Returns:
    Structured guidance and recommendations with working code patterns
save_workflowC
Save a creation workflow for reuse.

Args:
    name: Workflow name
    description: Workflow description
    steps: list of workflow steps

Returns:
    Confirmation message

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: create_mcp_server generates new servers, get_ai_guidance provides development advice, list_templates shows available templates, and save_workflow stores reusable workflows. The descriptions reinforce these distinct functions, making tool selection unambiguous.

Naming Consistency4/5

Three tools follow a consistent verb_noun pattern (create_mcp_server, list_templates, save_workflow), while get_ai_guidance uses a get_noun pattern that slightly deviates. The naming is still readable and predictable, with only minor inconsistency in verb choice.

Tool Count5/5

Four tools is well-scoped for an MCP creation assistant, covering the core workflow: creating servers, getting guidance, listing templates, and saving workflows. Each tool earns its place without redundancy or obvious gaps in this focused domain.

Completeness4/5

The toolset covers the main MCP creation lifecycle: planning (guidance), setup (templates), execution (creation), and reuse (workflow saving). A minor gap exists in managing or modifying existing servers (e.g., update or delete operations), but agents can work around this given the server's focused scope.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources