MCP server for Cursor agents

Cursor supports remote MCP servers with custom headers, which is all Tillpad needs. Tillpad isn't an official Cursor plugin. For developers connecting Cursor to an MCP server. Pro is $9 a month. Checked October 2026.

mcp.json

Cursor documents project config at .cursor/mcp.json and personal config at ~/.cursor/mcp.json. A remote server uses url and headers. Header values can include ${env:NAME} (Cursor MCP). The help page says to save the file and restart Cursor (MCP integrations).

Set TILLPAD_API_KEY in the environment Cursor inherits before it starts. The value is the tp_ secret, without the word Bearer. The header below adds Bearer.

{
  "mcpServers": {
    "tillpad": {
      "url": "https://tillpad.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${env:TILLPAD_API_KEY}"
      }
    }
  }
}

This does not configure Grok Bot

Cursor's Grok Bot security doc says the Grok Bot network switch is separate from MCP configuration for the editor (Grok Bot security). Use the Grok Bot page for that client. Do not assume this file is read by a Grok Bot.

HTTP API

The same key calls REST. Search, memory, email, and schedules are on their own pages.

curl -s -X POST "https://tillpad.dev/api/rag/search" \
  -H "Authorization: Bearer tp_…" \
  -H "Content-Type: application/json" \
  -d '{"query":"email before noon","topK":5}'

Other clients

Questions people ask

Does Tillpad MCP use OAuth in Cursor?

No. Leave out the auth client id block. Send the bearer header. Tillpad does not publish an OAuth authorization server.

Where does the spending cap show up?

Tool results include budget when the tool spends or reads quota. GET /api/budget and get_usage view=budget return the cap before you spend.