Connect Cursor to Agent Authority

Connect Cursor in the editor and CLI to SecureAuth Agent Authority so every MCP tool call is checked and audited

When you finish, every MCP tool call Cursor makes is checked against your policies and recorded in the audit log. Cursor, in the editor and its CLI, reaches your approved tools through one SecureAuth Agent Authority gateway URL, and each developer signs in as themselves.

Setup

  1. Add the MCP server. Add the following to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for global):

    {
      "mcpServers": {
        "secureauth": {
          "url": "https://your-gateway-url/gateway/mcp"
        }
      }
    }
  2. Authenticate.

    agent mcp login secureauth

    Or authenticate via the browser prompt on first MCP tool use in the editor.

    The agent is auto-registered on first connect. Works in both the editor and CLI (agent).

Connecting to just one MCP? To stay under an agent's tool limit, point the URL at a single MCP — /gateway/mcp/{slug} instead of /gateway/mcp. Grab the exact URL from the resource's detail page; see Scope a connection.

Next steps

  • Create a policy – control which tools Cursor can call.
  • Monitor activity – watch its tool calls appear in the dashboard and audit log.
  • Audit log – filter and search every tool call Cursor makes.

On this page