Does Claude Code support HTTP MCP servers with headers?

Yes. Use --transport http with one or more --header flags, or write the same thing into .mcp.json with a headers object.

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

Anthropic · Coding agents

Memrio for Claude Code

Put your engineering runbooks, API conventions, and architecture decisions where Claude Code can read them before it writes a line. One command adds the registry; a .mcp.json checked into the repo shares it with the whole team.

Jump to setup

live

Claude Codememrio

Why pair them

Runbooks the agent actually reads

Deployment steps, coding standards, incident playbooks — governed pages instead of a stale wiki.

Shared through the repo

Commit .mcp.json and every engineer’s Claude Code session gets the same page set.

Let it document as it goes

Give the agent write access and it can append to a page after a fix. A reviewer approves before it publishes.

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

01
Add the server
Run this once from the repo root. Use --scope project to write a .mcp.json the team can commit, or leave it out to keep the server local to you.
terminal
```
claude mcp add --transport http memrio https://memrio.ai/api/mcp/acme \
  --header "Authorization: Bearer mr_live_8f3a…" \
  --scope project
```

Or commit .mcp.json by hand

Reference the key through an environment variable so the secret never lands in git.

.mcp.json

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

Tell Claude when to use it

Add a line to CLAUDE.md so the agent browses the registry before answering questions about your systems.

CLAUDE.md

## Company knowledge

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.

04
Verify
Run /mcp inside Claude Code. memrio should show as connected with the browse, search_pages, and get_page tools.

Try it

A first prompt for Claude Code

“Check the registry for our deployment runbook and walk me through a hotfix release.”

FAQ

Claude Code and Memrio

Does Claude Code support HTTP MCP servers with headers?: Yes. Use --transport http with one or more --header flags, or write the same thing into .mcp.json with a headers object.
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