Integrations · MCP
Push documents into Magpie from your MCP client.
Connect your MCP client to Magpie. Say “push this to Magpie” and the document lands in your Inbox canvas, ready to read on any device where you’re signed in, even with no signal.
Tested with Claude Code and Claude Desktop. The Codex CLI and Cursor configs below follow the same spec but haven’t been tested with a real push yet. Not yet with chat apps that need OAuth.
Demo video coming soon
20 seconds: push a plan from the terminal, then read it on a phone in airplane mode.
What it does
Push a document
The push_to_magpie tool sends a title and full markdown. It lands as a new block in your Inbox canvas, which is created on the first push.
Push somewhere else
Name another canvas and the document goes there. If no canvas has that name, Magpie creates it.
Rendered like any block
Headings, tables, task lists, syntax-highlighted code and mermaid diagrams all render on the canvas.
Read it offline
On devices where you're signed in, the app keeps a copy of your cloud canvases. Open Magpie once on Wi-Fi and the inbox opens on the train.
Only what it needs
The list_magpie_canvases tool shows your folder and canvas names, so the client can pick a target. It can't read what's on your canvases.
Set up in three steps
- 1
Create a token
Open Magpie and sign in with your email (you get a one-time code, no password). Then go to Menu → Settings → MCP connections and choose Create token. Copy the
Open Magpiemgp_…token: it’s shown only once. You can revoke it in the same place. - 2
Add Magpie to your client
Claude Code: run this once, with your token in place of
mgp_...claude mcp add --transport http magpie https://www.magpie.md/api/mcp --header "Authorization: Bearer mgp_..."Claude Desktop: add this to
claude_desktop_config.jsonand restart Claude. It usesnpx mcp-remote, so you need Node.js installed.{ "mcpServers": { "magpie": { "command": "npx", "args": [ "-y", "mcp-remote", "https://www.magpie.md/api/mcp", "--header", "Authorization: Bearer ${MAGPIE_TOKEN}" ], "env": { "MAGPIE_TOKEN": "mgp_..." } } } }Codex CLI: keep the token in an environment variable and add the server once.
export MAGPIE_TOKEN=mgp_... codex mcp add magpie --url https://www.magpie.md/api/mcp --bearer-token-env-var MAGPIE_TOKENCursor: add this to
~/.cursor/mcp.json.{ "mcpServers": { "magpie": { "url": "https://www.magpie.md/api/mcp", "headers": { "Authorization": "Bearer mgp_..." } } } }Other clients: any MCP client that supports streamable HTTP and a custom
Authorizationheader can usehttps://www.magpie.md/api/mcp. - 3
Ask it to push
Try “push this plan to Magpie”. Then open Magpie on your phone and go to your Inbox canvas. To read it on the go, add Magpie to your home screen: Share → Add to Home Screen in Safari, or Install app in Chrome.
What it doesn’t do yet
Chat apps that only accept OAuth connectors
Web and mobile chat apps whose custom connectors need OAuth can't connect yet: Magpie only supports personal tokens today. Push from a desktop or terminal client; read on any signed-in device.
Encrypted canvases
Our server never has your passphrase, so it can't write into an end-to-end encrypted canvas. Pushes go to plain-text cloud canvases. You can encrypt a canvas after reading it, but pushes to it then stop.
Merge simultaneous edits
If you edit the inbox canvas on another device at the moment a push lands, the later write wins. Safer merging is on the list.
Privacy: pushed documents are stored as plain text in your Magpie cloud, like any other unencrypted cloud canvas. Tokens are personal and revocable. Read the privacy policy.