Doczoid

MCP Server

Let AI agents work in Doczoid the way you do. The Doczoid MCP server gives Claude Code, Cursor and other MCP clients access to your documents, diagrams and zoids — with exactly the rights of your own account.

Endpoint

https://mcp.doczoid.io/mcp

Streamable HTTP transport. A POST to https://mcp.doczoid.io/ works too.

1. Get a token

Open app.doczoid.io and go to Settings → Profile → Connect to MCP. Create a token — it starts with dzm_ and is shown exactly once.

2. Connect your client

With Claude Code, one command is enough:

claude mcp add --transport http doczoid https://mcp.doczoid.io/mcp \
  --header "Authorization: Bearer dzm_YOUR_TOKEN"

Or add it to any MCP client's configuration (e.g. .mcp.json):

{
  "mcpServers": {
    "doczoid": {
      "type": "http",
      "url": "https://mcp.doczoid.io/mcp",
      "headers": {
        "Authorization": "Bearer dzm_YOUR_TOKEN"
      }
    }
  }
}

What agents can do

Documents

Create, read, edit and organize documents — markdown text and the diagram side by side.

Zoids

Build slide decks: add, edit, reorder and style slides and their content.

Folders

Create, rename and delete folders, and move documents between them.

Import & export

Round-trip .doczoid files, and export documents as Markdown or HTML.

Photos & images

Search free stock photos or upload images straight into diagrams and slides.

PortalSnips

Create reusable live-updating snippets and insert them across documents.

Security

An agent acts with exactly your rights — every request runs under the same row-level security rules as when you use the app yourself. It sees your teams, your documents, your private notes; nothing more.
Tokens are stored only as hashes and can be revoked anytime from the same settings page. Requests are rate-limited per token.
The server is stateless: no conversation or session data is stored between requests.
Content edits automatically snapshot a version first, so you can roll back any agent change from the document's version history.