Cursor
Add Ratel Local to Cursor through its standard MCP configuration.
Cursor can run Ratel Local as a standard stdio MCP server. The setup is manual: Ratel Local 0.4.0 has no Cursor import or link adapter.
Do not use a Cursor agent flag
ratel-mcp mcp import --agent cursor and ratel-mcp mcp link --agent cursor
are not supported. Those commands only adapt Claude Code and Codex configuration.
Add Ratel Local manually
Add upstreams to Ratel
Run from your project when you use project or local scope.
npx -y @ratel-ai/mcp-server@0.4.0 mcp add \
--scope user context7 -- npx -y @upstash/context7-mcp
npx -y @ratel-ai/mcp-server@0.4.0 mcp listUse --scope project for shared project configuration or --scope local for private
project overrides. See MCP servers.
Add the Cursor MCP entry
Create .cursor/mcp.json in the project, or ~/.cursor/mcp.json to make the gateway
available in every workspace. Follow Cursor's
MCP configuration reference.
{
"mcpServers": {
"ratel-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ratel-ai/mcp-server@0.4.0",
"serve",
"--auto-config",
"--project-root",
"${workspaceFolder}"
]
}
}
}--project-root makes Ratel load the workspace's project and local configuration even
when Cursor starts the process from another directory. User configuration always loads
first; project and local entries override it by name.
Restart and verify
Open Cursor Settings → Tools & MCP. Confirm ratel-mcp is enabled and connected,
then start a new chat.
Cursor CLI users can inspect the same entry:
cursor-agent mcp list
cursor-agent mcp list-tools ratel-mcpThe tool list should include search_capabilities and invoke_tool. It also includes
get_skill_content when Ratel loads at least one skill.
Move existing Cursor servers
Cursor's native MCP entries are not imported automatically.
- Copy the current
.cursor/mcp.jsonor~/.cursor/mcp.jsonsomewhere safe. - Add each upstream to Ratel with
ratel-mcp mcp add. - Add and verify the single
ratel-mcpentry above. - Remove the migrated native entries from Cursor's
mcpServersobject. - Restart Cursor and begin a new chat.
Leaving a migrated server both native and behind Ratel exposes duplicate tool schemas. Ratel's backup command does not cover Cursor files that you edit yourself.
Verify the gateway
Ask Cursor to call the discovery tool directly:
Call Ratel's search_capabilities tool with:
{"query":"look up current React framework documentation","topKTools":3,"topKSkills":1}
Return the raw result.See Progressive disclosure for the request and response contract.
If Cursor shows the server as connected but the tools are missing, toggle ratel-mcp
off and on, then start a new chat. Continue with
Troubleshooting.