Manage Dynamic MCP Servers

MCP Create is a dynamic MCP server management service: it is itself an MCP server, but its job is to create, run, and manage other MCP servers as child processes, enabling a flexible ecosystem where new MCP servers can be spun up, updated, restarted, and torn down on demand rather than deployed as fixed, pre-built services.

Use it when you want an AI assistant or automation to dynamically create a new MCP server from a template, execute a tool on one of the child servers it's managing, list what's currently running, or delete a server it no longer needs. It currently supports TypeScript only, with JavaScript and Python support planned for future releases, so it is not yet usable for creating servers in those languages. Because it executes arbitrary generated code to run child servers, the project's own security notes call for sandboxing, resource limits, process monitoring for runaway or zombie processes, and careful path validation to prevent directory traversal - treat it with the caution due to any code-execution service, not as a fully hardened production sandbox out of the box.

create-server-from-template creates a new MCP server from a template for a given language, currently typescript, returning a serverId and a status message. execute-tool runs a named tool on a specific child server by serverId, passing arguments and returning that tool's execution result. get-server-tools lists the tools available on a given server. delete-server removes a server by its serverId. list-servers returns the IDs of all currently running child servers, with no input required. A typical execute-tool call passes a serverId alongside a toolName and an args object, for example calling an echo tool with a message payload on a specific running server.

Docker is the recommended path:

docker build -t mcp-create .
docker run -it --rm mcp-create

For manual TypeScript installation:

git clone https://github.com/tesla0225/mcp-create.git
cd mcp-create
npm install
npm run build
npm start

For Claude Desktop, add it to claude_desktop_config.json running via Docker. It requires Node.js 18+, TypeScript, and depends on @modelcontextprotocol/sdk, Node's built-in child_process and fs/promises modules, and uuid for generating server IDs.

Developers building or experimenting with MCP tooling who need to spin up, test, and tear down MCP servers dynamically - for example generating and validating a server from a template, or orchestrating several child servers programmatically - rather than deploying each one as a separate, statically configured service. It is released under the MIT License.