GitDiagram

What GitDiagram MCP server does

GitDiagram MCP server gives AI agents access to architecture information derived from GitHub repositories. An agent can inspect a repository’s explanation, see its identified components and connections, retrieve the Mermaid representation, search diagrams stored by GitDiagram, and obtain available explainer videos.

The service is intended for codebase orientation rather than direct code editing. It helps an agent answer questions about how a repository is structured, which parts are connected, and where the relevant files or directories appear in the generated architecture. The underlying GitDiagram product also provides interactive diagrams, links from diagram components to code locations, PNG export, and Mermaid copying, although the README specifically describes the MCP interface in terms of repository analysis and retrieval.

How it works

The hosted endpoint is available at https://gitdiagram.com/mcp. Clients connect to it as a remote MCP server using HTTP. The README states that the hosted service needs no API key or sign-in, making it suitable for clients that can register a remote MCP URL.

A typical agent request names a public repository, such as fastapi/fastapi, and asks how it is structured. GitDiagram then exposes the stored or generated architecture information through MCP tools. The result can include a textual explanation, component and connection data, Mermaid source, search results for stored diagrams, or an explainer video when one is available.

The repository also offers a web interface at GitDiagram.com. Public repositories can be visualized there, while private repositories can be used through the site with a GitHub token. The provided material does not confirm that private repositories are supported by the remote MCP endpoint.

Setup and configuration

For hosted use, add the remote server URL to an MCP-compatible client. Claude, Cursor, VS Code, Claude Code, Codex, Gemini CLI, Windsurf, Zed, and LM Studio are named in the setup material or examples. Claude Code can install the project plugin, or it can add only the HTTP MCP server. Codex uses the same endpoint with its MCP command.

A local development setup is separate from using the hosted MCP service. It requires Bun, Cloudflare R2, Upstash Redis, and an OpenAI or OpenRouter API key. The documented flow is to clone the repository, run bun install, copy .env.example to .env, fill in the configuration, and start the application with bun run dev. The local web app is then available at localhost:3000.

Tools and capabilities

GitDiagram MCP server supports these documented agent-facing capabilities:

• Read a public repository’s architecture explanation.
• Retrieve identified components and connections.
• Get the Mermaid source for a diagram.
• Search diagrams stored by GitDiagram.
• Get repository explainer videos.

The broader product can generate interactive architecture diagrams and narrated videos of about one minute. Existing videos can be watched, and downloadable MP4 output is available through the product interface. New video generation is described as early access.

Limitations and notes

The remote MCP service is documented for public repositories and has no key or sign-in requirement. Private repository support is documented for the website through a GitHub token, not explicitly for MCP. Local operation has additional infrastructure and API-key requirements that do not apply to the hosted endpoint.

Video explainers are disabled by default in a local deployment. Enabling them requires VIDEO_EXPLAINER_ENABLED=1, NEXT_PUBLIC_VIDEO_EXPLAINER=1, ANTHROPIC_API_KEY, OPENAI_API_KEY, and OPENROUTER_API_KEY. The README does not provide the complete names of all local storage or infrastructure settings, so those must be taken from .env.example and the setup guide.