A dynamic MCP server management service that creates, runs, and manages Model Context Protocol (MCP) servers dynamically. This service itself functions as an MCP server and launches/manages other MCP servers as child processes, enabling a flexible MCP ecosystem.

• Dynamic creation and execution of MCP server code
• Support for TypeScript only (JavaScript and Python support planned for future releases)
• Tool execution on child MCP servers
• Server code updates and restarts
• Removal of unnecessary servers

Note: Docker is the recommended way to run this service

# Build Docker image
docker build -t mcp-create .

# Run Docker container
docker run -it --rm mcp-create

# Clone repository
git clone https://github.com/tesla0225/mcp-create.git
cd mcp-create

# Install dependencies
npm install

# Build
npm run build

# Run
npm start

Add the following to your Claude Desktop configuration file (claude_desktop_config.json):

{
  "mcpServers": {
    "mcp-create": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "mcp-create"]
    }
  }
}

{
  "name": "create-server-from-template",
  "arguments": {
    "language": "typescript"
  }
}

{
  "name": "execute-tool",
  "arguments": {
    "serverId": "ba7c9a4f-6ba8-4cad-8ec8-a41a08c19fac",
    "toolName": "echo",
    "args": {
      "message": "Hello, dynamic MCP server!"
    }
  }
}

• Node.js 18 or higher
• TypeScript (required)
• Dependencies:
  • @modelcontextprotocol/sdk: MCP client/server implementation
  • child_process (Node.js built-in): Child process management
  • fs/promises (Node.js built-in): File operations
  • uuid: Unique server ID generation

• Code Execution Restrictions: Consider sandboxing as the service executes arbitrary code
• Resource Limitations: Set limits on memory, CPU usage, number of files, etc.
• Process Monitoring: Monitor and forcibly terminate zombie or runaway processes
• Path Validation: Properly validate file paths to prevent directory traversal attacks

MIT