Windsurf (Devin Desktop) Setup

Overview

Windsurf is the agentic code editor from Cognition, now called Devin Desktop, and its agent is Devin Local. 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: add Tempreon to ~/.config/devin/mcp_config.json with a url entry (or run devin mcp add -s user tempreon https://api.tempreon.com/functions/v1/tempreon-mcp/mcp) → approve in the browser when prompted.

Naming note: Windsurf became Devin Desktop on June 2, 2026, when Cognition consolidated its product line, and the docs moved to docs.devin.ai. Since v3.9.19 (September 8, 2026), Devin Local is the only agent in Devin Desktop. The legacy Cascade agent, and the Cascade MCP settings that came with it, have been removed.

Prerequisites

• Windsurf / Devin Desktop installed and signed in (any plan — see the enterprise note in Troubleshooting)
• On an Enterprise plan, an admin must enable Devin Local and allowlist MCP servers first, so ask yours to turn it on and allow Tempreon
• 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. Pick where the config lives

Devin Local keeps MCP servers in its own config files, under an mcpServers key:

• User (all projects): ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows)
• Project (shared through version control): .devin/mcp_config.json
• Local override (gitignored): .devin/mcp_config.local.json

For a personal memory server, the user file is usually the right home.

2. Add Tempreon to the config

Remote servers use the url field:

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

You can add "transport": "http" if you like, but it's optional — Streamable HTTP is the default for URL-based servers. If you have the Devin CLI installed, devin mcp add -s user tempreon https://api.tempreon.com/functions/v1/tempreon-mcp/mcp writes the same entry for you (without -s user, it saves to the gitignored local file in the current project).

Coming from Windsurf? Devin Local imports MCP servers from your old ~/.codeium/windsurf/mcp_config.json by default, so an existing entry may carry over on its own. Cognition doesn't document whether a serverUrl entry converts cleanly, so if Tempreon doesn't appear, add it to Devin Local's own file with url.

3. Authorize the connection

Run devin mcp login tempreon to open a browser tab to Tempreon's consent screen, or let Devin Local prompt you the first time Tempreon is used. Sign in to your Tempreon account, review the request, and approve. Expired credentials show as a Needs auth status in the MCP list — click Authenticate to sign in again. Each client keeps its own OAuth session, so authorizing Tempreon in another editor does not carry over.

4. Confirm the tools are active

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 that the entry is in one of Devin Local's files (.devin/mcp_config.local.json, .devin/mcp_config.json, or ~/.config/devin/mcp_config.json) and uses url. Run devin mcp list to see what Devin Local loaded.

Don't see the MCP option? On Enterprise plans, an admin turns on the Devin Local agent and controls MCP access: MCP can be switched on or off for the team, and admins can allowlist servers or enforce an MCP registry so only approved servers connect. Ask your workspace admin whether MCP is enabled and whether Tempreon needs to be allowlisted.

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

Browser authorization never opens. Run devin mcp logout tempreon, then devin mcp login tempreon. If OAuth still won't trigger, a stdio fallback works: replace url 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