mcp-server-id-mapping
MCP Server ID Mapping
Summary
Plugin mcp.json uses mcpServers object with command/args/env per server—same shape as workspace .cursor/mcp.json. MCP Apps deeplink: cursor://anysphere.cursor-deeplink/mcp/install?name=$NAME&config=$BASE64_ENCODED_CONFIG (see cursor.com/docs/mcp/install-links.md). Users toggle servers in Settings -> Features -> Model Context Protocol. CRITICAL LegioX rule: mcp.json key legiox-mcp is NOT CallMcpTool server—runtime id is project-0-ringdom-legiox-mcp from Cursor MCP registration (verify SERVER_METADATA.json under ~/.cursor/projects//mcps/). Always read tool descriptor JSON before CallMcpTool. Premium plugin ships legiox-mcp; reggie-mcp optional; community plugin must not require paid MCP. Use beforeMCPExecution hook to block destructive patterns if needed. Never commit API keys—document LEGIOX_ env vars in README.
When to use
- add MCP server to Cursor plugin
- generate MCP install deeplink for LegioX
- CallMcpTool server id mismatch legiox-mcp vs project-0-ringdom-legiox-mcp
- MCP server disabled or not loading from plugin
- premium vs community MCP tier gating
- hook beforeMCPExecution or afterMCPExecution