Use with Claude

Connect Archive to Claude to search captured content, look up creators, and manage saved views from a conversation. Setup requires only the endpoint URL — there is no client ID, no token to copy, and nothing to install.

Endpoint

POST https://app.archive.com/api/v2/mcp

Set up your client

Follow the instructions for your client. After you authorize the connection, Claude can read — and if you granted write access, update — content in the workspaces you can already access.

Open Settings → Connectors → Add custom connector.
Paste the endpoint URL above and save.
Log in to Archive when the consent screen opens, and choose whether to grant the optional write scope.
Back in the chat, enable the connector in the tools menu.

Remote MCP servers are configured through Settings → Connectors, not claude_desktop_config.json. Add the custom connector with the endpoint URL, complete the OAuth flow in the browser window that opens, then enable it per chat. Connectors are available on Pro, Max, Team, and Enterprise plans.

Claude Code — connect with OAuth

# Add the server — no token needed
claude mcp add --transport http archive https://app.archive.com/api/v2/mcp

# Then inside claude, authenticate in the browser
/mcp

Any client that speaks Streamable HTTP and OAuth 2.1 can connect with the endpoint URL alone. For stdio-only clients, bridge through the mcp-remote shim:

Stdio-only client — via mcp-remote

{
"mcpServers": {
  "archive": {
    "command": "npx",
    "args": ["-y", "mcp-remote", "https://app.archive.com/api/v2/mcp"]
  }
}
}

What happens during authorization

Claude connects with OAuth 2.1. You don’t create or paste an API token:

Claude’s first call gets HTTP 401 with a WWW-Authenticate challenge naming Archive’s protected-resource metadata.
It fetches the authorization-server metadata and registers itself via Dynamic Client Registration — nothing to configure on Archive’s side.
You log in at Archive’s consent screen and choose the scopes to grant. Without the optional write scope the connection is read-only.
Claude exchanges the authorization code for an opaque, Archive-issued access token scoped to what you approved.

Each person authorizes their own connection, and revoking one affects only that connection. Scopes are chosen at consent time only, so to change them, remove the connector and add it again.

Verify it works

Ask Claude to list your Archive workspaces. If the connection works, Claude calls getWorkspaces and returns your actual workspace names and IDs. If the tool list is empty or every call returns 401, authorization didn’t complete — remove the connector and add it again.

See Example prompts for more starting points, or Troubleshooting if something isn’t working.