Skip to main content

Cursor with Verdictan

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

Configure MCP​

Make the client token available to the Cursor process:

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

Create .cursor/mcp.json:

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

Launch Cursor from an environment that can access the token. Open the MCP settings. Verify that the server and tools are active. Cursor Agent CLI can examine configured servers with cursor-agent mcp list. It can list tools for one server with cursor-agent mcp list-tools verdictan.

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

Model-traffic boundary​

An MCP configuration does not change the model endpoint for Cursor chat, agent, or tab completion. Do not point Cursor's generic network proxy at the Verdictan model API. Only use a model-routing path that the installed Cursor version explicitly documents as a custom compatible endpoint. Verify it with verdictan events tail --follow.

Next steps​