MCP in Cursor.
One JSON file, global or per project.
Cursor reads MCP servers from mcp.json: a global file in ~/.cursor/ for your personal tools, and an optional .cursor/mcp.json per project for shared ones. Tools run in Agent mode. Here's the setup, the file format, and the toggles that trip people up.
Add a server
For a remote server like Amie's, the whole config is a URL. Put this in ~/.cursor/mcp.json to have it in every workspace:
{
"mcpServers": {
"amie": {
"url": "https://mcp.amie.so"
}
}
}{
"mcpServers": {
"my-local-server": {
"command": "npx",
"args": ["-y", "@some/mcp-server"]
}
}
}Open Cursor Settings and go to the MCP section: the server appears with its status and tool list. Amie shows a sign-in prompt there; approve the OAuth flow in your browser and the dot turns green. You can also add servers from this settings page directly instead of editing the file.
Using the tools
MCP tools run in Agent mode, not plain chat. Ask naturally (“find 30 free minutes tomorrow and book a call with alex@example.com”) and the agent picks the right tool; Cursor asks for approval before each call unless you allow a tool to run automatically. If tools stop firing, check the MCP settings page first: servers can be toggled off, and too many enabled servers makes tool selection worse. Fewer, broader servers beat a long list of single-purpose ones, which is the case for one Amie connection over separate Google Calendar, todo, and notes servers.