Codeium · Coding agents

Memrio for Windsurf

Cascade can plan across your whole repo — now let it plan with your company’s approved knowledge too. Add the registry once in mcp_config.json and Cascade browses your page set whenever a task touches policy, architecture, or process.

Jump to setup
live
Windsurfmemrio

Why pair them

01

Cascade reads the runbook

Ops steps and coding standards become pages the agent can open, not a PDF nobody attaches.

02

Governed by default

Only published pages in the agent page set are visible. Drafts stay private.

03

Auditable

Every browse and get_page call shows up in the request log with latency and pages hit.

Setup

3 steps, about ten minutes.

You need two values from an agent page in Memrio: the workspace MCP URL and an API key. Examples use https://memrio.ai/api/mcp/acme — swap in yours.

Create an agent and key first
  1. 01

    Open the MCP config

    In Windsurf go to Settings → Cascade → MCP Servers → View raw config, or edit ~/.codeium/windsurf/mcp_config.json directly.

  2. 02

    Add the server

    Windsurf uses serverUrl for remote servers. Headers are sent with every request.

    ~/.codeium/windsurf/mcp_config.json
    {
      "mcpServers": {
        "memrio": {
          "serverUrl": "https://memrio.ai/api/mcp/acme",
          "headers": {
            "Authorization": "Bearer mr_live_8f3a…"
          }
        }
      }
    }
  3. 03

    Refresh and test

    Click Refresh in the MCP panel. Ask Cascade something your registry answers and watch it call browse, then get_page.

Try it

A first prompt for Windsurf

Browse the registry for our database migration policy before you write this migration.

FAQ

Windsurf and Memrio

Does Memrio need a workspace or page-set header?
No. The API key is scoped to one workspace and one agent page set, so the key alone tells the server what the agent may read. Send only the Authorization header.
Which pages can the agent see?
Only published pages inside the agent page set you configured. Drafts and pages waiting on review are hidden unless you turn on "Read drafts" for a test agent.
Can the agent edit pages?
Only if you enable "Can edit pages" on that agent. It then gets get_page_source, create_page, update_page, and append_to_page. Edits are submitted as versions for human review unless the agent is also allowed to publish.

Other integrations