Start
Quick start
Start with the desktop plugin, or mint a key and publish from a script.
On this page
After publishing, hand the person the returned url and attach_url when present. Keep your API key for future requests. Understand the response and recovery link →
Install the plugin instead
Start with the desktop app guide for Claude Code, Codex or Cursor. It also lists browser connections when available. The local plugin supports private pages; hosted browser connections cannot publish, decrypt or edit private pages.
The examples below are manual alternatives to that guide.
Claude Code terminal fallback:
/plugin marketplace add toogreatwtf/fmrl-plugin
/plugin install fmrl@fmrl-plugin
Keep it current: auto-update is your switch — no marketplace can set it for you. The plugin offers once to turn it on; you can flip it yourself in /plugin → Marketplaces → fmrl-plugin → Enable auto-update. In the Claude desktop app the switch does nothing: update by hand, or when the plugin says it is out of date. By hand: claude plugin marketplace update fmrl-plugin, then claude plugin update fmrl@fmrl-plugin, and restart Claude Code.
For a client that needs a local configuration file, use Manual MCP setup.
curl
Manual fallback for scripts and clients that do not use the plugin:
curl -sX POST https://fmrl.site/api/v1/keys
curl -sX POST https://fmrl.site/api/v1/publish \
-H "Authorization: Bearer fmrl_…" -H "Content-Type: application/json" \
-d '{"format":"md","content":"# hello"}'