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 profile menu or Cmd+, / Ctrl+,)
2. Go to Cascade → MCP Servers

You can also click the MCPs icon in the Cascade panel to jump straight there.

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"
    }
  }
}

The key must be serverUrl — url is not recognized here.

3. Authorize the connection

When you add an HTTP server, the OAuth flow triggers automatically: a browser tab opens to Tempreon's consent screen. Sign in to your Tempreon account, review the request, and approve. You'll be returned to the editor with the server connected.

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 the key name — remote servers need serverUrl, not url.

Don't see the MCP option? As of July 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. Ask your workspace admin whether MCP is enabled and whether Tempreon needs to be allowlisted.

Tools missing after connecting. Devin Desktop 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.

Browser authorization never opens. Remove the server entry, save, re-add it. 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"].

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