Cursor reads MCP servers from a JSON file. One entry, then a browser sign-in.
Adding the server
Open Customize in the Cursor sidebar, then MCP.
Add a custom MCP server, or edit
mcp.jsonyourself and add{ "mcpServers": { "vamos": { "url": "https://mcp.getvamos.ai/mcp" } } }Save. Cursor connects and opens a browser window. Sign in to Vamos.
It worked when Vamos appears under Customize → MCP with its tools listed and a toggle beside it.
Which file
~/.cursor/mcp.json applies to every project.
.cursor/mcp.json inside a repository applies to that project only, and travels with the repo.
Expect quiet
Cursor shows almost nothing while a tool runs, and heavy research can take up to 15 minutes. That silence is not a failure. Break big requests into smaller ones rather than asking again, because a second ask starts a second run and bills twice.
If something goes wrong
It will not connect. Open the Output panel, Cmd+Shift+U on a Mac or Ctrl+Shift+U on Windows, and choose MCP Logs. Cursor writes the reason there.
You are on a company machine. An administrator can allowlist which MCP URLs are permitted. If ours is not on the list, no setting on your side will connect.