AI agents
mdedit agents can work in the same Markdown Document as a human. They can read and edit content, leave review comments and suggestions, reply to threads, appear in the live presence UI, and publish an explicitly confirmed public link.
The recommended setup is to install the mdedit Agent Plugin (opens in a new tab) and sign in through your assistant. You can also add https://mcp.mdedit.ai/mcp in your assistant's remote MCP settings, then sign in and approve workspace access.
For Claude Code, connect the hosted server directly:
claude mcp add --transport http mdedit https://mcp.mdedit.ai/mcp
claude mcp login mdeditUse /mcp to sign in on versions without mcp login. API keys remain available for unattended workflows or clients without browser sign-in. See Connect your AI assistant.
For permissions, setup verification, example prompts, and troubleshooting, follow Use mdedit with Claude Code.
Install mdedit skills to give your agent workflows for saving, finding, revising, reviewing, and publishing documents. Choose a plugin with an MCP connection or CLI-backed skills in the installation guide.
You can also use the mdedit CLI directly in scripts and other agent runtimes.
New agent-created public links default to Live, so later durable edits update the
same mded.it URL. Agents can request a Snapshot for a frozen artifact. MCP keeps
confirmPublic: true at the public-visibility boundary; the CLI treats the publish
command or --publish flag itself as that explicit action.
To wake your own process when a reviewer mentions an agent or a document changes, use
workspace agent webhooks.
Last reviewed