Does Cursor support remote MCP servers with an Authorization header?

Yes. Give the server a url and a headers object in .cursor/mcp.json. Cursor speaks Streamable HTTP and sends the headers on every request.

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.

memrio

Anysphere · Coding agents

Memrio for Cursor

Cursor’s agent is only as good as what it knows about your codebase’s rules. Add the registry as an MCP server and every Composer or Agent session can pull your conventions, service boundaries, and on-call notes before it edits.

Jump to setup

live

Cursormemrio

Why pair them

Conventions on demand

Keep the long rules out of .cursor/rules. Let the agent fetch the page that matters for the task at hand.

Same pages for every engineer

Commit .cursor/mcp.json and the whole team’s agent reads one approved source.

No secrets in git

Cursor expands environment variables in mcp.json, so the key stays on each machine.

Setup

4 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

Create the config

Add .cursor/mcp.json at the root of the project (or ~/.cursor/mcp.json for every project).

.cursor/mcp.json

{
  "mcpServers": {
    "memrio": {
      "url": "https://memrio.ai/api/mcp/acme",
      "headers": {
        "Authorization": "Bearer ${env:CONTEXT_REGISTRY_KEY}"
      }
    }
  }
}

02
Set the key
Export CONTEXT_REGISTRY_KEY in your shell profile, or paste the key directly into the headers value if the file is not committed.
~/.zshrc
```
export CONTEXT_REGISTRY_KEY="mr_live_8f3a…"
```
03
Enable in Cursor
Open Cursor Settings → Tools & MCP. memrio appears with a green dot and its tools listed. Toggle it on if it is off.

Add a rule so the agent browses first

A short always-on rule makes the agent check the registry before answering questions about your stack.

.cursor/rules/company-knowledge.mdc

---
alwaysApply: true
---
Before answering anything about our company, products, or policies, call `browse` on the memrio server, open the pages whose use-when instructions match, and answer only from those pages. If nothing applies, say so.

Try it

A first prompt for Cursor

“Look up our API error-handling conventions in the registry, then refactor this handler to match.”

FAQ

Cursor and Memrio

Does Cursor support remote MCP servers with an Authorization header?: Yes. Give the server a url and a headers object in .cursor/mcp.json. Cursor speaks Streamable HTTP and sends the headers on every request.
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