Why does Windsurf say there are too many tools?

Cascade allows 100 tools in total and FishOut exposes 115. Add the disabledTools list on this page to the fishout entry, or turn tools off in the Cascade panel, until the total is 100 or fewer.

Is Windsurf now Devin Desktop?

Windsurf’s Cascade documentation now lives under Devin Desktop and uses ~/.config/devin/ paths. Older builds still read ~/.codeium/windsurf/mcp_config.json.

Does Windsurf support OAuth for remote servers?

Its documentation says OAuth is supported for each transport type. FishOut answers with a standard OAuth challenge, so no key is needed.

Which FishOut tools are safe to disable?

Billing (checkout, plan changes, the billing portal, AppSumo), agency administration and custom domains: sixteen tools nobody calls from an editor. That leaves 99, including every mention, keyword, label, draft and Daily brief tool.

Our admin allowlists MCP servers. What do I ask for?

The server URL, https://mcp.fishout.ai/mcp. Once a team admin allowlists anything, every server not on the list is blocked, so FishOut has to be added explicitly.

MCP · Editor

Connect FishOut to Windsurf (MCP Setup)

Windsurf’s Cascade agent — documented as Devin Desktop since the rebrand — connects to remote MCP servers with OAuth. It also caps every agent at 100 tools in total, and FishOut exposes 115. That is fixable in one list, and this page gives you the list.

Start free Read the MCP docs

Setup steps checked against Windsurf's own documentation on 20 October 2026.

[01] CONNECT IT/ SETUP

Add FishOut to Windsurf

https://mcp.fishout.ai/mcp, on every plan.

Add the server

The config file is ~/.config/devin/mcp_config.json on macOS and Linux (%APPDATA%\devin\mcp_config.json on Windows). Older Windsurf builds used ~/.codeium/windsurf/mcp_config.json — check which one your build has. A remote server takes serverUrl.

~/.config/devin/mcp_config.json

{
  "mcpServers": {
    "fishout": {
      "serverUrl": "https://mcp.fishout.ai/mcp",
      "disabledTools": [
        "create_checkout",
        "create_billing_portal",
        "change_plan",
        "bind_appsumo_license",
        "set_agency_funding",
        "assign_agency_client",
        "onboard_agency_client",
        "update_agency_brand",
        "update_agency_client",
        "grant_agency_member",
        "revoke_agency_member",
        "list_agency_clients",
        "get_agency_configuration",
        "add_custom_domain",
        "verify_custom_domain",
        "remove_custom_domain"
      ]
    }
  }
}

Cascade supports OAuth on remote servers; refresh the MCPs section of the Cascade panel and complete the FishOut sign-in when it prompts.

Or use an API key

Headers interpolate environment variables with ${env:NAME}, which keeps a key out of the file.

mcp_config.json (inside "fishout")

"headers": {
  "Authorization": "Bearer ${env:FISHOUT_API_KEY}"
}

Check it worked. Open the MCPs section of the Cascade panel: FishOut should be on, with its tool count at 99 or fewer. Ask how many mentions came in yesterday.

[02] WORTH KNOWING FIRST/ LIMITS

Before it bites

Stated before you hit them.

Cascade can use at most 100 tools at a time, across every server. FishOut has 115, so without disabledTools it will not fit even alone. The list above removes 16 billing, agency and custom-domain tools a listening workflow never calls.

If you run other MCP servers too, disable more — the 100 is a total. Keep list_mentions, get_mention and count_mentions.

Team admins can restrict MCP to an allowlist; once anything is allowlisted, everything else is blocked. Enterprise users have to switch MCP on in settings first.

Not tested by us yet, so the 100-tool fit is from Windsurf’s documented limit and our tool count, not a recorded run.

[03] WHAT IT LOOKS LIKE/ WINDSURF

A question in Windsurf

Invented brands; a real call.

Windsurf · Cascadefishout · mcp

Is anyone talking about the rate-limit headers we added? I want to know before I document them.

list_mentionsread-onlyarguments

{
  "filter": {
    "query": "rate limit",
    "sort": "newest"
  },
  "limit": 10
}

saltworks/client-pyissue #232d

Respect RateLimit-Reset instead of a fixed sleep

Reply nowQuestion

One: a client library wants to honour RateLimit-Reset instead of sleeping. Worth a line in docs/rate-limits.md that the header is in seconds — want me to add it?

[04] WATCH ANY PLATFORM/ SAME SERVER