Connect in Cursor

Cursor connects to remote MCP servers directly. You need an MCP token (tsk_mcp_…) from the dashboard.

Steps

In Cursor open Settings → MCP (older versions: Settings → Cursor Settings → MCP).

[SCREENSHOT: Cursor Settings, MCP section, with the 'Add new MCP server' button highlighted]

Choose Add new MCP server. Cursor opens the mcp.json file. You can also edit it yourself: ~/.cursor/mcp.json for all projects, or .cursor/mcp.json inside one project.
Add TenderScope:

{
  "mcpServers": {
    "tenderscope": {
      "url": "https://tenderscope.app/mcp",
      "headers": {
        "Authorization": "Bearer tsk_mcp_YOUR_TOKEN"
      }
    }
  }
}

Replace tsk_mcp_YOUR_TOKEN with your token. Do not commit this file if it holds a real token.

[SCREENSHOT: mcp.json with the tenderscope entry (token blurred)]

Save. In Settings → MCP the tenderscope entry shows a green dot and four tools: search_tenders, get_tender, add_to_watchlist, get_deadline_alerts.

[SCREENSHOT: MCP list with tenderscope enabled and the four tools]

Open the chat in Agent mode and ask: Find IT services tenders in Armenia with a deadline later than next week. Cursor asks permission to run search_tenders; approve it.

[SCREENSHOT: Agent chat showing a search_tenders call and the result]

If it does not work

Symptom	What to check
Red dot, `401 unauthorized`	The token must start with `tsk_mcp_`. A REST key (`sk_live_…`) does not work on the MCP URL. Check that the key was not revoked.
No tools listed	Use the exact URL ending in `/mcp`. Restart Cursor after editing `mcp.json`.
`429 quota_exceeded`	The monthly call limit is used up. See Plans and limits.