Codemesh

Register the CodeMesh server using the Claude Code CLI or by editing your client's config file directly. The npx command downloads and runs the latest version automatically.

claude mcp add codemesh npx -y codemesh

In your project root, create a .codemesh/config.json file that lists every MCP server CodeMesh should be able to orchestrate. Each entry needs a unique id, a human-readable name, and a type of stdio, http, or websocket.

{
  "servers": [
    {
      "id": "weather",
      "name": "Weather Server",
      "type": "stdio",
      "command": ["npx", "-y", "@modelcontextprotocol/server-weather"]
    },
    {
      "id": "filesystem",
      "name": "Filesystem Server",
      "type": "stdio",
      "command": ["npx", "-y", "@modelcontextprotocol/server-filesystem", "/tmp"]
    }
  ],
  "logging": {
    "enabled": true,
    "level": "info",
    "logDir": ".codemesh/logs"
  }
}

CodeMesh exposes exactly three tools to the AI agent: discover-tools (get an overview of all capabilities across all connected servers), get-tool-apis (fetch TypeScript function signatures for specific tools), and execute-code (run a TypeScript block in a sandboxed VM2 environment with a 30-second timeout).

When a sub-server needs API keys or secrets, pass them in the env block within the server entry in .codemesh/config.json. You can reference system environment variables using ${VAR} or ${VAR:-default} syntax.

{
  "servers": [
    {
      "id": "maps",
      "name": "Maps Server",
      "type": "stdio",
      "command": ["npx", "-y", "@modelcontextprotocol/server-maps"],
      "env": {
        "GOOGLE_MAPS_API_KEY": "${GOOGLE_MAPS_API_KEY}"
      }
    }
  ]
}

Restart your MCP client after saving the config. Ask the agent to call discover-tools to confirm CodeMesh can see and enumerate all configured sub-servers.