Connect Contextick to Devin

Devin's desktop app — formerly Windsurf — reads MCP servers from a JSON config file. You'll create a Contextick API key, paste it into that file along with the Contextick endpoint, and you're done.

What you'll need

Devin's desktop app (formerly Windsurf).
A Contextick API key. Create one at your account page under MCP connection → API keys → Create API key.

Two things about the key. It's shown once, right after you create it — copy it then, because you can't view it again. And the name you give the key becomes the origin recorded on everything saved through it, so calling this one "Devin" means you can later tell what you saved in Devin from what you saved elsewhere.

Steps

Create an API key at your account page and copy it.
In Devin, open Settings → Devin Local → MCP Servers → Devin MCP Marketplace → Add custom MCP. Devin opens its config.json file for you.
Add Contextick:
```
{
  "mcpServers": {
    "contextick": {
      "serverUrl": "https://contextick.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_CONTEXTICK_API_KEY"
      }
    }
  }
}
```
Replace YOUR_CONTEXTICK_API_KEY with the key you copied. If your config.json is empty, paste the whole block above. If it already has other servers under "mcpServers", add only the "contextick": { … } block — leave the others as they are.

Note that Devin calls the endpoint field serverUrl, not url — if you're copying a snippet from another tool's docs, that's the field that will bite you.
Save the file and refresh the MCP server list (or restart Devin). Contextick should appear as connected.

Check it worked

Test it in two parts, and make the second part a new conversation. If you ask in the same one, Devin can answer from what you just said without ever calling Contextick — so a broken connection would still look like it worked.

Save something you'd actually want back. At the end of a session where you worked out a rule, say: "Save the deploy rules we just agreed on to Contextick."
Start a new conversation and ask: "What are our deploy rules?"

If it comes back in the new conversation, you're connected — and you've just seen the point of it: you didn't have to explain the rules again. That note is also available in Claude, ChatGPT, or any other AI you connect to Contextick.

If it doesn't show up

Contextick isn't listed. Refresh the MCP server list, then restart Devin. Check the JSON is valid; a stray comma is the usual culprit.
You used url instead of serverUrl. Devin documents serverUrl for remote servers. Use that.
It's listed but every call fails. That's almost always the key — check you pasted it exactly, with no extra spaces, and that Bearer is still in front of it.
You lost the key. Keys are shown once. Create a new one and delete the old one from your account page.

Official docs

Devin's own MCP guide: MCP in Devin. (Windsurf became Devin's desktop app, and its docs now live on the Devin documentation site.)