mcp-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_creator_profileA | Load the creator's persistent profile — their setup status, GitHub/PyPI usernames, and project history. Call this FIRST in every session. If the profile exists with setup_complete=true, skip all onboarding and go straight to building. |
| update_creator_profileA | Update the creator's profile after setup steps or project creation. Call this after: setup completes, a project is published, or GitHub/PyPI info is learned. This persists across sessions so the user never repeats setup. |
| check_setupA | Check the user's environment for required tools (uv, git, gh CLI, PyPI token). Call this after get_creator_profile if setup_complete is false. If everything is set up, skip beginner instructions and go straight to building. |
| check_pypi_nameA | Check if a package name is available on PyPI. Call this first before scaffolding. |
| scaffold_serverA | Scaffold a complete, runnable MCP server project. Pass the package name, description, and a JSON array of tool definitions. Each tool def: {name, description, parameters: [{name, type, required, description, default}], returns}. The generated server runs immediately with stub implementations. Set paid=true to add license key gating via the MCP Marketplace SDK. Set paid_tools to a JSON array of tool names to gate (omit to gate all). Set hosting="remote" for an SSE/HTTP server with Dockerfile (default: "local" for stdio). |
| add_toolA | Add a new tool to an existing scaffolded MCP server. Pass the project directory and a JSON tool definition. Creates the tool module, service stub, test, and updates server.py. |
| build_packageA | Build the MCP server package using 'uv build'. Run this after implementing your tools. |
| publish_packageA | Publish the built package to PyPI using 'uv publish'. Requires a PyPI token — either pass it directly or set UV_PUBLISH_TOKEN env var. |
| setup_githubA | Initialize git, create a GitHub repo, and push the project. Requires the gh CLI to be installed and authenticated. Run this after publishing to PyPI so the repo URL can be included in the LAUNCHGUIDE. |
| generate_launchguideA | Generate a LAUNCHGUIDE.md for MCP Marketplace submission. Creates a formatted file ready to submit at mcp-marketplace.io. Limits: tagline max 100 chars, features max 30 items, tags max 30. |
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 10 tools
Each tool has a clearly distinct purpose with no overlap: setup (check_setup, get_creator_profile), scaffolding (scaffold_server, add_tool), building/publishing (build_package, publish_package), GitHub integration (setup_github), documentation (generate_launchguide), and utilities (check_pypi_name, update_creator_profile). The descriptions make it easy to differentiate between similar-sounding tools like scaffold_server and add_tool.
All tool names follow a consistent verb_noun pattern with snake_case throughout (e.g., scaffold_server, publish_package, generate_launchguide). There are no deviations in naming conventions, making the set predictable and easy to parse for an agent.
With 10 tools, the server is well-scoped for its purpose of creating and managing MCP servers. Each tool earns its place by covering distinct aspects of the workflow: from initial setup and scaffolding to building, publishing, and documentation. This count is neither too sparse nor bloated.
The tool set provides complete coverage for the MCP server creation lifecycle: environment setup (check_setup, get_creator_profile), project creation (scaffold_server, add_tool), building and publishing (build_package, publish_package, check_pypi_name), GitHub integration (setup_github), documentation (generate_launchguide), and persistence (update_creator_profile). There are no obvious gaps, and agents can follow a seamless workflow from start to finish.