Cursor

Cursor supports remote MCP servers directly. Connect it to the platform with an URLMCP and a Bearer token; no local proxy package is required.

Attention

OAuth tokens are limited by both their scope and platform permissions. Use a dedicated token, keep it out of version control and review tool calls before approving writing operations.

Prerequisites

• A current version of Cursor
• Access to a court of the platform
• A scoped the platform OAuth token

Endpoint

Choose the end point for your platform environment:

Environment	MCP URL
the platform US	https://us.probo.com/api/mcp/v1
the platform EU	https://eu.probo.com/api/mcp/v1
Custom	https://your-probo-instance.com/api/mcp/v1

The ___ZBT_I18N_RUNTIME_BLOCK_172__ segment is required.

Configure Cursor

1. Create a the platform OAuth token

   On the platform, open the account menu, select OAuth tokens, and create a purpose token called Cursor. Authentication guidance and guidance.

2. Choose the configuration scope

   Create one of these files:

   • .cursor/mcp.json in a project for a project specific connection
   • ~/.cursor/mcp.json for a connection available in each project

3. Establish the token in your environment

   export PROBO_API_TOKEN="your_api_token_here"

   Restart the cursor after setting the variable so that the application can read it. remote MCP servers do not support the cursor option ___ZBT_I18N_RUNTIME_BLOCK_178__.

4. Add the remote server

   {
     "mcpServers": {
       "probo": {
         "url": "https://us.probo.com/api/mcp/v1",
         "headers": {
           "Authorization": "Bearer ${env:PROBO_API_TOKEN}"
         }
       }
     }
   }

   Replace the URL if you use the EU region or a self-hosted court.

5. Enable the server

   Open Cursor settings, go to Tools & MCP, and confirm that probo is enabled and connected.

Verify the connection

Start with a read-only request:

Use Probo to list the organizations I can access.

The cursor should ask for approval before you run the tool and then return your platform organizations.

List the open risks for organization org_xxx.
Summarize overdue compliance tasks without changing anything.

Multiple the platform instances

Give each medium its own server name and token:

{
  "mcpServers": {
    "probo-development": {
      "url": "http://localhost:8080/api/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${env:PROBO_DEV_TOKEN}"
      }
    },
    "probo-production": {
      "url": "https://us.probo.com/api/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${env:PROBO_PROD_TOKEN}"
      }
    }
  }
}

Use separate token names so that credentials cannot be sent to the wrong court.

Troubleshooting

Serverul nu este listat

• Confirms that the file is named mcp.json, not mcp_config.json.
• To configure the project, confirm that the path is .cursor/mcp.json.
• Validate JSON and restart the cursor.

The server returns 401

• Confirms that the environment variable is available for the Cursor process.
• Confirm that the title starts with Bearer .
• Generate a new token if the existing token has been revoked or has expired.

The server returns 404

Confirms that the URL ends with /api/mcp/v1. The route /api/mcp which is not a version is not a valid endpoint for the MCP platform.

Instrumentele sunt indisponibile

• Check the server status under Tools & MCP.
• Confirm the platform’s role to access the requested organization and operation.
• Try the same end point with MCP Inspector.

For the specific configuration behavior of the cursor, see Cursor MCP documentation.