MMD Studio
Open app

Agent integration account required

MMD Studio ships a skill file at mmd.studio/SKILL.md that teaches any agent how to create, read, update, delete, and share your diagrams via the REST API. Combined with an API token, it's enough to fully drive the app from a conversation.

Supported agents

Anything with a web-fetch / tool-call capability works. Tested with:

  • Claude Code — the Claude Code CLI with native skill support.
  • Claude Desktop — via the built-in fetch tool.
  • Cursor — paste the skill URL + token into a chat.
  • Any custom agent — curl from a shell tool call works.

Option A — fetch on demand

Tell the agent to read the skill at the start of the conversation. Zero setup, works everywhere. 

Read https://mmd.studio/SKILL.md and follow those instructions.
My MMD_TOKEN is mmd_...

Now create a diagram showing the OAuth handshake between a client
and a server, then flip it to link-shareable and give me the URL.

The agent fetches the markdown, parses the API contract, and makes the right calls.

Option B — install locally (Claude Code, persistent)

For regular use, save the skill into Claude Code's user skills directory so it gets auto-loaded every session: 

mkdir -p ~/.claude/skills/mmd-studio
curl -sS https://mmd.studio/SKILL.md -o ~/.claude/skills/mmd-studio/SKILL.md

# Put the token somewhere persistent
echo 'export MMD_TOKEN="mmd_..."' >> ~/.zshrc  # or ~/.bashrc
source ~/.zshrc

From then on, you can say "use the mmd-studio skill to…" and Claude Code will route to it automatically without needing to fetch anything at runtime. The skill file has Claude Code frontmatter (name + description) so the routing picks it up.

Example prompts

A few concrete asks that exercise different parts of the API:

  • "Create a new flowchart on mmd.studio for the user signup flow: landing page → email form → verify email → dashboard. Make it link-shareable and give me the URL."
  • "List all my mmd.studio diagrams and tell me which are shared."
  • "Update my 'Auth handshake' diagram to add a refresh-token step after the access-token response."
  • "Here's a share link: https://mmd.studio/d/<id>. Summarize what the diagram shows."
  • "Delete the 'scratch-test' diagram from my mmd.studio account."

Tips

  • Keep the token out of chat history. Put it in an env var and reference $MMD_TOKEN in prompts.
  • Let the agent generate the UUID. The skill file explains how (uuidgen, crypto.randomUUID(), etc.) — don't hard-code ids.
  • Read before writing. If you're updating a diagram, fetch it first so you don't blow away fields you didn't mean to touch.
  • Validate the Mermaid syntax. The server doesn't parse Mermaid — a syntactically broken diagram will persist fine but render as an error in the UI.

Future: MCP server

A remote MCP server at mmd.studio/mcp is on the roadmap, so MCP-native clients (Claude Desktop, Cline, etc.) can connect with a token and get the tools as proper MCP tools — no skill file required. Until then, the REST + SKILL.md path works just as well.