Autodocument MCP Server

If you want an AI assistant working directly with Autodocument, the autodocument mcp server is the bridge. MCP server for automatic documentation generation using OpenRouter.

What Autodocument does

An MCP (Model Context Protocol) server that automatically generates documentation for code repositories by analyzing directory structures and code files using OpenRouter API.

Key capabilities

• Smart Directory Analysis — Recursively analyzes directories and files in a code repository
• Git Integration — Respects .gitignore patterns to skip ignored files
• AI-Powered Documentation — Uses OpenRouter API (with Claude 3.7 by default) to generate comprehensive documentation
• Test Plan Generation — Automatically creates test plans with suitable test types, edge cases, and mock requirements
• Code Review — Performs senior developer-level code reviews focused on security, best practices, and improvements
• Bottom-Up Approach — Starts with leaf directories and works upward, creating a coherent documentation hierarchy
• Intelligent File Handling —
• Creates documentation.md, testplan.md, and review.md files at each directory level

Tools it exposes

Once connected, the assistant can call these 4 tools directly:

• Prerequisites — The Prerequisites tool exposed by this server
• generate_documentation — Generates comprehensive documentation for a code repository: { "path": "/path/to/your/project", "openRouterApiKey": "your-api-key-here", // Optional "model"
• autotestplan — Generates test plans for functions and components in a code repository: { "path": "/path/to/your/project", "openRouterApiKey": "your-api-key-here", // Optional
• autoreview — Generates a senior developer-level code review for a repository: { "path": "/path/to/your/project", "openRouterApiKey": "your-api-key-here", // Optional

Installing the autodocument mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply one environment variable: OPENROUTER_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Node.js (v16 or newer) - An OpenRouter API key

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Autodocument sits in that group, and the shape of its toolset — Prerequisites, generate_documentation, autotestplan among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by PARS-DOE.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the autodocument mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.