connect claude
Connect fmrl to Claude for public pages you can share by link.
Public pages only. If your agent runs on your machine (Claude Code, Claude Desktop, Cursor), install the plugin instead: private pages, every tool, and updates you can switch on once.
connect
- Review Name (
fmrl) and MCP server URL, then select Continue. - On the next screen, leave Authentication on Sign in now and OAuth client on Use Claude’s published identity. Select Add.
Manual setup
In Claude on the web, open Customize → Connectors → Add → Add custom connector. Enter fmrl in Name and paste this into MCP server URL, then follow the steps above:
https://fmrl.site/mcpApprove the connection on fmrl, then return to Claude.
About consent and your key
Claude sends you here to consent. The page names the app and the host the connection goes to, and offers a key: a new one named after the app, or, in a browser that already holds keys, one of those. Allow, and you are back in Claude. No account is made; the key is the whole identity, and the browser you consented in lists what it publishes under your canvases.
the first thing to ask
Ask for fmrl_whoami and check that the key prefix matches the one you approved.
Understanding the first result
It answers the key’s prefix (fmrl_ and four characters), its name (the app’s, or the name of the key you chose), how many of this month’s 25 free publishes it has used, and when its agent was attached to your identity: when you consented. The prefix is the one the consent page showed; if it is not, disconnect and connect again.
Results and permissions
what claude shows
Each call is a card with the tool’s name and its result; a page’s link is in the result. Claude asks before it uses each tool. To stop it asking for reads, open the connector under Customize → Connectors and set the read-only tools to Always allow; publishing, editing, watching and deleting can stay on Needs approval, or be allowed the same way. Private pages never go through this connection: the connector refuses it and tells Claude not to retry as a public page. The plugin or the paste form seals a private page before it leaves your machine.
Troubleshooting and reconnecting
when something goes wrong
- “Authentication required”, or Claude says the connector needs reconnecting. A connection lasts 30 days, or until it is disconnected from your account page. Reconnect from Customize → Connectors; from the browser you first consented in, or one signed in to your account, the consent page preselects the key this app had, so its pages, watches and inbox come back with it; elsewhere it offers a new key, and the old key’s pages stay where they are.
- The consent page says to start again from the app. The page is good for five minutes and one answer. Go back to Claude and connect again rather than reloading it. If the URL answers “not found” instead, hosted MCP is not on at that address: check the URL above.
- A tool is refused. The refusal says why, to Claude. A private page: not here; use the plugin or the browser. An edit of a page this key did not publish: pass Claude the token at the end of the page’s recovery link (
/c/<token>, 22 characters) asmanage_token, those characters alone and never a whole link: a private page’s link carries its key after#p=, and that key must never reach a chat. A page Claude cannot find: it is not this key’s, it has expired, or it was removed.
Disconnect from Claude’s connector settings, or from your account page, which lists every app connected to a key this browser holds. Either ends the connection, not the key. Limits and every tool: the API reference, under Hosted MCP.