read thedocs.

[ docs // guides & reference ]

Connector setup guides, tool references, auth flows, and platform concepts — everything you need to run StackJack, in one place.

34 connectors documented // 6,712 tools referenced // setup, auth & platform guides

No pages match that search. Clear it

← All documentation

Connect Windsurf (Devin Desktop) to StackJack

Windsurf — now Devin Desktop, by Cognition — connects to remote MCP servers through its Cascade agent (renamed Devin Local after the June 2026 rebrand). MCP is the Model Context Protocol, the open standard AI tools use to call external tools. It can sign in with just the server URL — no headers.

The rebrand was delivered as an over-the-air update, so your app may show either name. The configuration file path below is unchanged and works for both.

Prerequisites

  • Windsurf / Devin Desktop installed (a current build; the app updates itself).
  • A StackJack account that is a member of your workspace. Any team member can connect — no admin-created credentials needed for the sign-in path.
  • Your StackJack MCP endpoint URL: https://mcp.stackjack.io/mcp.
  1. Open SettingsCascadeMCP Servers, or edit the config file directly:

    • macOS/Linux: ~/.codeium/windsurf/mcp_config.json
    • Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
  2. Add an entry with only the serverUrl (note the key name — not url):

    {
      "mcpServers": {
        "stackjack": {
          "serverUrl": "https://mcp.stackjack.io/mcp"
        }
      }
    }
    
  3. Restart the app. On first use, Cascade opens a browser to sign in — use the same email, password, and MFA you use for the StackJack Portal.

Manual credentials (fallback)

An owner, co-owner, or Administrator creates an MCP client in the portal first (see Managing MCP credentials). Base64-encode CLIENT_ID:CLIENT_SECRET, add a headers block, and restart the app:

{
  "mcpServers": {
    "stackjack": {
      "serverUrl": "https://mcp.stackjack.io/mcp",
      "headers": {
        "Authorization": "Basic <BASE64_OF_CLIENT_ID:CLIENT_SECRET>"
      }
    }
  }
}

Tool limits

Cascade has a hard limit of 100 total tools across all MCP servers combined. StackJack can expose hundreds of tools depending on your connectors and plan, so the primary fix is catalog mode: switch StackJack to compact or minimal mode so it serves a small tool list and Cascade discovers the rest on demand, keeping you under 100 without hiding anything. An admin must first enable catalog modes for your organization on Endpoints; until then StackJack serves the full tool list. Trimming the client's tool selection or disabling other MCP servers you aren't using helps too. See Choosing tools for each client and managing harness tool limits.

Troubleshooting

  • No sign-in prompt after adding the server — restart the app; the config file is read at startup.
  • Sign-in says no account was found — sign up in the portal first, or ask your team admin for an invite.
  • For anything else, see Connection troubleshooting.