Skip to main content

Cursor with Keeptrusts

Cursor supports remote MCP servers in project-level .cursor/mcp.json and user-level ~/.cursor/mcp.json. Use that integration to make Keeptrusts tools and resources available to Cursor Agent.

Configure MCP​

Make the client token available to the Cursor process:

export KEEPTRUSTS_MCP_TOKEN="<client-api-token>"

Create .cursor/mcp.json:

{
  "mcpServers": {
    "keeptrusts": {
      "url": "https://<published-hostname>/mcp",
      "headers": {
        "Authorization": "Bearer ${env:KEEPTRUSTS_MCP_TOKEN}"
      }
    }
  }
}

Launch Cursor from an environment that can see the token, then open its MCP settings and verify that the server and tools are active. Cursor Agent CLI can also inspect configured servers with cursor-agent mcp list and list tools for one server with cursor-agent mcp list-tools keeptrusts.

See Cursor's MCP documentation for current configuration locations and transport support.

Model-traffic boundary​

Adding MCP does not change the model endpoint used by Cursor chat, agent, or tab completion. Do not point Cursor's generic network proxy at the Keeptrusts model API. Only use a model-routing path that the installed Cursor version explicitly documents as a custom compatible endpoint, and verify it with kt events tail --follow.

Next steps​