Model Context Protocol
Your AI already knows the repo. Now it knows the docs.
DocZoid ships a full MCP server. Any MCP client can read your documents and diagrams, create and update them, and pull the current architecture into context before it answers.
- Read-only repo access
- Works with Claude Code, Cursor, Claude Desktop
- Free for one editor
claude mcp add doczoid \
--transport http https://mcp.doczoid.io/v1{
"mcpServers": {
"doczoid": {
"url": "https://mcp.doczoid.io/v1",
"headers": { "Authorization": "Bearer ${DOCZOID_TOKEN}" }
}
}
}{
"mcpServers": {
"doczoid": {
"command": "npx",
"args": ["-y", "@doczoid/mcp"],
"env": { "DOCZOID_TOKEN": "${DOCZOID_TOKEN}" }
}
}
}Full setup, authentication, and the tool reference live at mcp.doczoid.io.
What the server can do
Read and write, not just read.
A documentation tool your AI can only read from is a search index. The point is that it can put things back.
- Read any doc, diagram, or presentation the token can see
- Create and update docs and diagrams
- Insert a PortalSnip, so generated content lands in the right places
- Pull the current architecture diagram into the model's context
MCP access is included from the Team plan, using a token scoped to the team and the documents that token is allowed to see. The same roles and permissions apply as in the app.
What people do with it
Four things that stop being manual.
Write the decision record with the diagram already in it
Claude Code just split a service. Ask it to draft the ADR in DocZoid and insert the regenerated architecture diagram as a PortalSnip. The record and the picture arrive together.
Read the runbook before touching the payment path
Point Cursor at the runbook for the service it is about to change. It reads the constraints you wrote down six months ago instead of rediscovering them in production.
Answer 'what talks to what' without opening a tab
The current architecture diagram is in your model's context. Ask the question in the terminal you are already in.
Keep the code inside the building
The server speaks MCP, so the client can be a model running on your own hardware. Nothing about your repository has to reach a vendor you did not choose.
Point your AI at your documentation.
Start free, connect the server, and ask it what talks to what.
- Read-only repo access
- Works with Claude Code, Cursor, Claude Desktop
- Free for one editor