Windsurf with Verdictan

Give the Cascade agent Verdictan tools through MCP, so you can ask it to find a request in History or lint a policy. This adds tools only: Cascade's model requests keep going to its hosted models, not through your gateway.

Windsurf now ships as Devin Desktop, where Cascade is the legacy agent. This page configures Cascade. The default Devin Local agent reads MCP servers from the Devin CLI configuration instead.

Before you start

• A published gateway hostname from Gateway Setup for IDEs. MCP is not served on localhost:41002.
• A client API token for the MCP connection. See API Tokens for IDEs.
• On a Team or Enterprise plan, an admin who has turned on MCP and, if an allowlist is in use, allowed a server named verdictan.

Configure Windsurf

1. Set the token, and start the app from the same environment:

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

2. In the Cascade panel, open the ... (Actions) menu, and in the MCPs section select Open MCP config file.

3. Add a verdictan entry under mcpServers, next to any servers already there:

   mcp_config.json

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

4. Save the file. In the MCPs section, turn on verdictan and disable any Verdictan tools you don't need; Cascade can use at most 100 tools across all servers.

If VERDICTAN_MCP_TOKEN is not set when the app starts, ${env:...} becomes an empty string and every call fails with 401. See the Cascade MCP documentation for interpolation and admin controls.

Verify

1. In the MCPs section, check that verdictan is on and lists tools such as history_search and policy_lint.
2. Ask Cascade: "Use Verdictan history_search to find my recent test request. Do not change configuration."
3. Open the tool result. An empty result is valid when nothing matches.

MCP tool calls are not model requests, so verdictan events tail does not show Cascade's prompts.

Troubleshooting

Symptom	Cause	Fix
The server doesn't appear	Invalid JSON, or the server is not on the team allowlist	Validate the JSON. Ask an admin to allowlist verdictan; the ID must match the key exactly.
401 or an authentication error	The app cannot read VERDICTAN_MCP_TOKEN, or the token is inactive	Start the app from a shell that exports it, and check the token on the Console API Tokens page.
mcp_publication_required	The URL is not a published agent hostname	Use the publication hostname, not localhost:41002 or the control-plane API.
Cascade prompts don't appear in verdictan events tail	MCP does not route model traffic	Expected. To govern prompts, use a client with a custom base URL.

For more checks, see IDE Integration Troubleshooting.

Next steps

• Gateway MCP Surface: every tool and resource on the MCP endpoint.
• Monitor IDE AI Usage: traffic from editors that do route through the gateway.