Practical guides for real workflows

Integrate AgentDoc with your tools.

Step-by-step guides for connecting AgentDoc to your AI coding tools, sharing knowledge across your team, and building agent workflows that stick.

AI Tool Integrations

Connect AgentDoc to your AI coding tools

One-line MCP install. Sync CLAUDE.md across repos. Give Claude direct read/write access to your docs.

One-line MCP install. Cowork writes the doc; AgentDoc gives it a URL anyone can open — no Claude account needed.

One-line MCP install. Claude Desktop publishes any draft to a shareable URL without leaving the chat.

One-line MCP install. Any MCP-capable VS Code extension (Continue, Cline) gains AgentDoc tools.

One-line MCP install. Every Codex task ships a published doc — run reports, migration plans, incident timelines.

One-line MCP install. OpenClaw publishes the artifact it just wrote — every chat reply gets a real URL.

One-line MCP install. Hermes by Nous Research publishes from Telegram, Discord, or Slack to a shareable URL.

Cursor MCP entry. Publish specs and runbooks from the editor; pull .cursorrules into every repo.

Windsurf MCP entry. Publish docs from Cascade; sync .windsurfrules across projects.

Zed context server entry. Publish docs inline from the editor with the built-in assistant.

Store system prompts in AgentDoc. Fetch the .md at runtime. Ship a prompt edit without a deploy.

Import AgentDoc as a ChatGPT Action. GPT reads the latest prompt and knowledge directly — no copy-paste.

Team processes and best practices

One AgentDoc document -> CLAUDE.md + .cursorrules + .windsurfrules + AGENTS.md, synced across every repo.

What markdown files your agents should produce, and how to keep design.md, agent.md, and process docs alive.