Does Claude support API-key auth for remote MCP servers?

Yes. Claude.ai custom connectors accept a fixed Authorization header, the Messages API takes authorization_token, and Claude Desktop can bridge through mcp-remote with a --header flag.

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 · Chat assistants

Memrio for Claude

Connect Claude.ai, Claude Desktop, or your own Claude-powered product to a page set your team approved. Claude browses the registry with the same MCP tools it already knows, and cites the page it used.

Jump to setup

live

Claudememrio

Why pair them

One page set for every Claude surface

The same key works in Claude.ai, Claude Desktop, and the Messages API MCP connector.

Instructions ride along

Critical instruction blocks on a page arrive with the content, so Claude knows how to apply it.

Writes go through review

Let Claude draft updates to a page. Nothing publishes until a person approves the version.

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
Claude.ai — add a custom connector
Open Settings → Connectors → Add custom connector. Name it Memrio and paste the MCP server URL. Under Request headers add Authorization with the value Bearer plus your key (keep the space). Claude stores the header securely and sends it on every request.
Connector fields
```
Name                 Memrio
Remote MCP server URL  https://memrio.ai/api/mcp/acme
Request header         Authorization: Bearer mr_live_8f3a…
```

Claude Desktop — bridge with mcp-remote

If your Claude Desktop build does not expose request headers yet, use the mcp-remote bridge. Edit claude_desktop_config.json (Settings → Developer → Edit Config) and restart Claude.

claude_desktop_config.json

{
  "mcpServers": {
    "memrio": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://memrio.ai/api/mcp/acme",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer mr_live_8f3a…"
      }
    }
  }
}

Messages API — attach the MCP connector

Building on the Anthropic API? Pass the server in mcp_servers and Claude calls the registry tools directly from the model.

messages.ts

import Anthropic from '@anthropic-ai/sdk';

const client = new Anthropic();

const message = await client.beta.messages.create({
  model: 'claude-sonnet-4-5',
  max_tokens: 1024,
  betas: ['mcp-client-2025-04-04'],
  mcp_servers: [
    {
      type: 'url',
      url: 'https://memrio.ai/api/mcp/acme',
      name: 'memrio',
      authorization_token: 'mr_live_8f3a…',
    },
  ],
  messages: [
    { role: 'user', content: 'Summarize our refund policy for annual plans.' },
  ],
});

04
Ask, and check the source
Claude lists the page set with browse, opens the matching page with get_page, and answers from it. Open the agent in the registry to see the request log fill in.

Try it

A first prompt for Claude

“Check Memrio and tell me the shipping window we promise for international orders. Quote the page.”

Good to know

Request headers on Claude.ai custom connectors are rolling out; if the field is missing in your org, use the mcp-remote route.
The mcp-remote header uses no space after the colon on purpose — it avoids an argument-splitting bug on Windows.

FAQ

Claude and Memrio

Does Claude support API-key auth for remote MCP servers?: Yes. Claude.ai custom connectors accept a fixed Authorization header, the Messages API takes authorization_token, and Claude Desktop can bridge through mcp-remote with a --header flag.
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