Windsurf (Devin Desktop) Setup

Overview

Windsurf is the agentic code editor from Cognition, built around the Cascade agent panel. Once Tempreon is connected, the agent loads your Core Imprint, searches your Knowledge Vault, and remembers what it learns, across every tool you use.

There's an extra reason to connect here: Devin Desktop natively hosts open models like GLM, Kimi, and DeepSeek alongside Claude and GPT — connecting Tempreon gives those models your context too.

Quick path: Devin Settings → Cascade → MCP Servers → add Tempreon as an HTTP server → approve in the browser.

Naming note: Windsurf became Devin Desktop on June 2, 2026, when Cognition consolidated its product line. It's the same product with the same config file — only the name and docs location (docs.devin.ai) changed. This guide uses the current menu labels; older builds say "Windsurf Settings" instead of "Devin Settings."

Prerequisites

• Windsurf / Devin Desktop installed and signed in (any plan — see the enterprise note in Troubleshooting)
• A Tempreon account with at least one available Bridge slot
• The Tempreon server URL (also shown in your Bridges dashboard)

Step-by-Step Setup

1. Open the MCP settings

1. Open Devin Settings — from the top-right profile dropdown, or through the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) with Open Devin User Settings
2. Go to Cascade → MCP Servers

You can also click the MCPs icon in the top-right menu of the Cascade panel to jump straight there. (Cmd+, opens the editor's own settings pane rather than Devin Settings — Devin Desktop is a VS Code fork.)

2. Add Tempreon to the config

Click Add Server (or open the raw config). The file lives at ~/.codeium/windsurf/mcp_config.json, and remote servers use the serverUrl key:

{
  "mcpServers": {
    "tempreon": {
      "serverUrl": "https://api.tempreon.com/functions/v1/tempreon-mcp/mcp"
    }
  }
}

Use serverUrl — it is the key Cognition's own remote-HTTP example uses. Cascade also accepts plain url for remote HTTP servers, so an existing entry using url is not broken and does not need changing.

Which agent are you in? This file configures the legacy Cascade agent. Cognition's docs flag Devin Local as the default agent for new tabs, and it reads its own files — .devin/mcp_config.local.json (default, gitignored), .devin/mcp_config.json (project), or ~/.config/devin/mcp_config.json (user) — where the field is url, not serverUrl. Fastest route there: devin mcp add tempreon https://api.tempreon.com/functions/v1/tempreon-mcp/mcp. If Tempreon does not appear on a current install, check the agent before you touch this file.

3. Authorize the connection

In Cascade, adding an HTTP server opens a browser tab to Tempreon's consent screen. Sign in to your Tempreon account, review the request, and approve, and you'll be returned to the editor with the server connected. (Cognition confirms OAuth support on every transport but does not document the exact trigger, so if the tab does not appear on its own, re-adding the entry usually prompts it.)

In Devin Local, authorize explicitly with devin mcp login tempreon, or let it prompt you the first time Tempreon is used. Expired credentials show as a Needs auth status in the server list. Each client keeps its own OAuth session, so authorizing Tempreon in another editor does not carry over.

4. Confirm the tools are active

Refresh the MCP Servers list if needed, then ask the agent "What Tempreon tools do you have access to?" If it lists Tempreon's tools, the Bridge is live.

Troubleshooting

Connection fails immediately. The URL must end in /mcp with no trailing slash: https://api.tempreon.com/functions/v1/tempreon-mcp/mcp.

Config saved but the server never appears. Check which agent you are in first — this file configures the legacy Cascade agent, and Devin Local (the default for new tabs) reads its own files and uses url. Cascade accepts either serverUrl or url, so the key name is rarely the cause.

Don't see the MCP option? As of August 2026, Enterprise plans ship with MCP turned off by default; an admin has to enable it, and admins can also restrict which servers are allowed — once even one server is allowlisted, everything not on the list is blocked. Ask your workspace admin whether MCP is enabled and whether Tempreon needs to be allowlisted.

Tools missing after connecting. Cascade caps active MCP tools at 100 total across all servers. If you run several servers, disable some tools or servers so Tempreon's fit under the cap. Cognition documents no equivalent cap for Devin Local.

Devin Local connects but Tempreon never runs. Devin Local's default configuration asks for approval before every MCP tool call — approve the prompt, or change the approval setting.

Browser authorization never opens. In Cascade, remove the server entry, save, and re-add it; in Devin Local, run devin mcp login tempreon. If OAuth still won't trigger, a stdio fallback works: replace serverUrl with "command": "npx", "args": ["-y", "mcp-remote", "https://api.tempreon.com/functions/v1/tempreon-mcp/mcp"]. That fallback is our own workaround, not Cognition guidance.

Also connect: Cursor · VS Code · Zed

Try saying...

• "Start my session." — triggers session_start to load your Core Imprint
• "Search my knowledge base for how we handle database migrations." — exercises knowledge retrieval end-to-end
• "Remember that this repo deploys through CI only, never manual pushes." — stores a working rule for every future session