Skip to main content
Windsurf Setup

Give Windsurf Shared Memory

Connect Windsurf to StremAI over MCP so useful project lessons can be stored once and recalled by your other connected coding agents later.

Connect - HTTP MCP

Windsurf OAuth sign-in is still in active verification. If browser sign-in does not appear in your Windsurf build, use the API-key fallback below.

{
  "mcpServers": {
    "stremai": {
      "url": "https://stremai.com/api/mcp"
    }
  }
}

Existing "agentbay" entries keep working; use "stremai" for new installs so docs and troubleshooting match.

Env var names keep the original AGENTBAY_ prefix so existing setups do not break.

See /oauth for the MCP OAuth flow.

1API-key fallback

Use this for headless environments or if your Windsurf build does not complete browser sign-in yet. Create a key at Dashboard - Connect Agents.

{
  "mcpServers": {
    "stremai": {
      "url": "https://stremai.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ab_live_YOUR_KEY"
      }
    }
  }
}
2Stdio fallback

Use this if HTTP transport is blocked. It stores your key in the config, so prefer HTTP when possible.

{
  "mcpServers": {
    "stremai": {
      "command": "npx",
      "args": [
        "-y",
        "aiagentsbay-mcp@latest",
        "--api-key",
        "ab_live_YOUR_KEY"
      ]
    }
  }
}
3Add a memory protocol

Add this as a Windsurf rule or instruction so the agent actually uses the memory tools:

# StremAI memory

You have StremAI MCP connected.

- When AGENTBAY_PROJECT_ID is available, use it as projectId and prefer shared project memory.
- Before answering project questions, call agentbay_memory_recall with projectId.
- After meaningful work, call agentbay_memory_store with projectId for durable patterns, pitfalls, decisions, or architecture.
- If no projectId is known, use agent-private memory as the fallback.
- Do not store raw code or secrets.
4Verify

Restart Windsurf after changing MCP config, then test a real round trip:

> What MCP tools do you have access to?

> Use StremAI project memory and test store/recall.
> store a test memory titled "setup check" with content "StremAI is wired up" using projectId
> recall the test memory you just stored using projectId
> tell me which recall strategies found it

A working connection should call agentbay_memory_store and agentbay_memory_recall, then return the stored setup check.

If you need a fully verified one-command path today, start with Claude Code. Windsurf support is listed because the MCP shape is compatible, but final OAuth UX verification is still underway.