Integration

Connect your AI coding agent to DocuGen with MCP

Documentation goes stale on the first day of coding, because what the developer learns while implementing never goes back to the spec. The DocuGen MCP server closes that loop inside the editor: the agent reads the briefing before writing code, and records what diverged when it is done.

How do I connect my coding agent to DocuGen?

DocuGen runs a hosted MCP server at https://docugen.dev/api/mcp. To connect a coding agent, create an API key on the DocuGen Developer page using the AI Agent (MCP) preset (new keys start read-only), then register that URL in your MCP client with the key sent in an X-API-Key header. In Claude Code that is a single command: claude mcp add --transport http docugen https://docugen.dev/api/mcp --header "X-API-Key: SUA_CHAVE". There is nothing to install and no local process to run. Once registered, the agent can list projects, read product requirement documents and technical specifications, edit a section, add a comment and submit the document for human review. Every agent edit saves the previous version first and moves the document to review, so no change is silent. Assistants such as ChatGPT and claude.ai connect with sign-in instead of a key: add https://docugen.dev/api/mcp as a custom connector and authorize on DocuGen. Without an account, https://docugen.dev/api/mcp/public shows the document catalog. API keys require a Pro, Invited or Enterprise plan; with sign-in, Free reads and Pro also edits.

Claude Code · bash
claude mcp add --transport http docugen https://docugen.dev/api/mcp --header "X-API-Key: SUA_CHAVE"
Endpoint
https://docugen.dev/api/mcp

The loop it closes

  1. The agent pulls the project briefing: business context, product requirements, execution plan and technical specifications.
  2. It implements against that briefing instead of guessing, because the specification is the source of truth in the conversation.
  3. When the implementation diverges, the agent edits the affected section and sends the document for review, with a summary of what changed.
  4. You review the change in DocuGen, with the previous version saved and the difference visible.

Setup, step by step

1. Create an API keyOn the Developer page, create a key and choose the AI Agent (MCP) preset: new keys start read-only. It grants reading, editing, review, comments, document generation and project creation, and nothing else.
2. Register the serverRun the claude mcp add command with your key. In Cursor and other clients, add the same URL and header to the MCP settings.
3. Ask for the briefingTell the agent to read the DocuGen project before implementing. It will fetch the briefing and follow it.
4. Send the change backWhen the implementation diverges, ask the agent to update the specification. The change lands as a new version waiting for your review.

What the agent can do

ToolWhat it does
docugen_list_projectsList the projects the key can reach.
docugen_create_projectCreate a new project, ready for its BND.
docugen_get_projectProject details and its document index.
docugen_list_documentsDocuments of a project, filtered by type or status.
docugen_get_documentRead a document or a single section.
docugen_get_agent_packThe whole project as one AGENTS.md briefing.
docugen_update_documentEdit the document, a section, or add or rename a section, with the previous version kept.
docugen_submit_for_reviewClose the edit and send it for human review.
docugen_discard_changesUndo the open edit session.
docugen_archive_documentArchive a document that is no longer current.
docugen_restore_documentBring an archived document back.
docugen_add_commentReport a divergence without rewriting the document.
docugen_generate_documentGenerate the BND, the PRD or a specification with AI.
docugen_get_jobFollow the progress of a generation and get the link to review the document.
docugen_list_document_typesPublic catalog: the document types DocuGen generates, no account needed.
docugen_get_document_templatePublic catalog: the sections of one document type.
docugen_list_examplesPublic catalog: ready-made example documents.
docugen_get_startedPublic catalog: how to create an account and start.

The other end of the loop: meetings

Requirements rarely start in a document, they start in a call. DocuGen connects to Microsoft Teams, Google Meet and Notion to import meeting transcripts and turn them into structured requirements, so the specification your agent reads begins where the decision was actually made.

See the meeting transcript section of the User Guide

Questions

Which AI coding tools work with this?
Any client that speaks MCP over HTTP, including Claude Code, Cursor, Codex and VS Code. There is nothing to install: the server runs on DocuGen and you register a URL.
Can the agent overwrite my documentation?
No edit is silent. The first change by an agent saves the previous version, the document moves to review, and the owner is notified. You approve or revert.
What happens if I edit the same document while the agent is working?
Your edit wins and the agent draft is never thrown away. DocuGen saves the agent work as a version, closes the edit session, and applies your change on top. The agent is told the session ended and has to read the document again before writing.
Do I need a paid plan?
Yes. The MCP server uses the developer API, available on the Pro and Enterprise plans.
Does DocuGen read meeting transcripts too?
Yes. Connect Microsoft Teams, Google Meet or Notion, import the transcript, and DocuGen turns the conversation into structured requirements you can generate documents from.

Stop shipping code against a specification nobody updated.

Start free