Windsurf

Windsurf Cascade supports HTTPMCP servers remotely. Connect it directly to the platform with the MCP endpoint and a Bearer token.

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 Windsurf
• 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 Windsurf

1. Create a the platform OAuth token

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

2. Establish the token in your environment

   export PROBO_API_TOKEN="your_api_token_here"

   Open Windsurf again after setting the variable so that the app can read it.

3. Open the MCP configuration

   In the Cascade panel, open MCPs and select View Raw ConfigWindsurf stores this configuration at:

   ~/.codeium/windsurf/mcp_config.json

4. Add the remote server

   {
     "mcpServers": {
       "probo": {
         "serverUrl": "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. Refresh the server list

   Save the file, return to the MCP panel and click on RefreshConfirm that probo is connected and activate the tools you want Cascade to use.

Verify the connection

Start with a read-only request:

Use Probo to list the organizations I can access.

Cascade 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": {
      "serverUrl": "http://localhost:8080/api/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${env:PROBO_DEV_TOKEN}"
      }
    },
    "probo-production": {
      "serverUrl": "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

• Open the configuration MCPs → View Raw Config to confirm that you have edited the active file.
• Validate JSON and click Refresh.
• Restart Windsurf after changing environment variables.

The server returns 401

• Confirms that the environment variable is available for the Windsurf 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 serverUrl ends at /api/mcp/v1. The uncompleted route /api/mcp is not a valid endpoint for the MCP platform.

Instrumentele sunt indisponibile

• Confirms that individual tools are enabled in the MCP panel.
• 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 Windsurf, see Windsurf MCP documentation.