Autonomous Docs

You can run Autonomous Documentation MCP as a self-contained documentation engine that analyzes your codebase, generates Mintlify-style docs, and keeps them in sync as your code evolves. It exposes a dedicated MCP server you can connect to from your MCP client to perform analysis, generate documentation, create a changelog, and more with automated validation and synchronization.

How to use

You interact with the Autonomous Documentation MCP through an MCP client. Start by configuring the MCP client to connect to the local or remote MCP server, then unleash its capabilities to analyze your codebase, generate MDX-backed documentation, extract an API reference, validate content, and sync changes.

How to install

Prerequisites: you need Node.js 18+ and npm or yarn, plus Git for changelog generation.

# Clone the repository
git clone https://github.com/perryjr1444/autonomous-docs-mcp.git
cd autonomous-docs-mcp

# Install dependencies
npm install

# Build the project
npm run build

Configuration

Add the MCP server configuration to your client configuration to connect to the Autonomous Documentation MCP. The server example below runs locally using Node and points to the built entry file.

{
  "mcpServers": {
    "autonomous-docs": {
      "command": "node",
      "args": ["/path/to/autonomous-docs-mcp/dist/index.js"],
      "env": {}
    }
  }
}

Security and validation notes

Expect the MCP to validate links, code examples, and frontmatter as part of the documentation generation and synchronization workflow. Do not include sensitive data in generated docs, and respect existing .gitignore patterns when scanning the codebase.

Troubleshooting

If you encounter issues starting or coordinating with the MCP server, verify that the server process is running and that the command and path to the entry file are correct.

Development

The project is organized to analyze a codebase, generate documentation, extract API references, validate content, and synchronize with source changes. It uses TypeScript with Node.js tooling and ships a dist build for runtime execution.

Examples and usage patterns

Common usage patterns involve analyzing a project, generating documentation to a dedicated output directory, and then validating the generated content. You can also generate a changelog from git history and extract code examples for inclusion in docs.

Available tools

analyze_codebase

Autonomously analyze the entire codebase structure to identify documentation needs and API surfaces.

generate_documentation

Create complete Mintlify-style documentation with MDX files, navigation, and frontmatter.

generate_api_reference

Generate an API reference from code annotations, JSDoc, or docstrings.

create_docs_config

Generate a docs.json configuration with navigation and theme settings.

validate_documentation

Validate MDX files, links, and code examples for quality and correctness.

sync_documentation

Sync documentation with codebase changes and detect updates.

generate_changelog

Create a changelog from git history using semantic versioning.

extract_code_examples

Extract and organize code examples from tests, demos, and source files.