git-mcp

Transforms GitHub repository URLs into standardized Model Context Protocol server endpoints using pattern-matching and subdomain routing. GitMCP operates as a Cloudflare Workers application that exposes repository-specific MCP servers at predictable URLs (gitmcp.io/{owner}/{repo} or {owner}.gitmcp.io/{repo}), enabling AI assistants to connect to any GitHub project without manual configuration. The system maintains a ToolIndex that serves as the central coordinator for all repository-specific and common tools, dynamically generating MCP tool definitions based on repository content.

Implements a smart documentation discovery pipeline that prioritizes llms.txt → AI-optimized documentation → README.md with intelligent fallback logic. The system fetches repository documentation from GitHub using the GitHub API, applies content prioritization rules, and caches results to minimize API calls. This ensures AI assistants receive the most relevant, human-curated documentation first, reducing hallucinations by grounding responses in actual project documentation rather than training data.

Deploys GitMCP as a serverless application on Cloudflare Workers, eliminating infrastructure management and providing global edge distribution. The system uses Wrangler configuration (wrangler.jsonc) to define worker routes, environment variables, and service bindings (KV storage, Vectorize, FalkorDB). Deployment is automated through Cloudflare's deployment pipeline, with automatic scaling and zero cold-start latency through edge caching. This architecture enables GitMCP to serve requests from locations near users with minimal latency.

Reduces AI hallucinations by providing grounded, real-time access to repository documentation and code through MCP tools. Instead of relying on training data, AI assistants can query actual repository content (documentation, code, dependencies) through the MCP interface. The system ensures responses are based on current repository state rather than outdated or incorrect training data. This is achieved through the combination of documentation fetching, semantic search, and code analysis capabilities that provide authoritative sources for AI responses.

Provides semantic search capabilities over repository documentation using Cloudflare Vectorize for embeddings generation and vector similarity search. The system processes documentation content into embeddings, stores them in a vector database, and enables AI assistants to find relevant documentation sections through natural language queries rather than keyword matching. This allows context-aware retrieval where queries like 'how do I authenticate' can find relevant sections even if they don't contain those exact words.

Analyzes repository code structure and relationships using FalkorDB graph database integration, enabling AI assistants to understand code dependencies, function calls, and module relationships. The system builds a code graph from repository files, stores it in FalkorDB, and exposes graph queries through MCP tools. This allows AI assistants to answer questions like 'what functions call this method' or 'what are the dependencies of this module' by traversing the code graph rather than searching raw files.

Implements a pluggable repository handler architecture that supports both generic and specialized handlers for different repository types. The system uses a handler registry that routes requests to appropriate handlers based on repository characteristics (e.g., ThreejsRepoHandler for three.js, GenericHandler for dynamic repositories). Each handler implements repository-specific optimizations like custom documentation processing, code analysis strategies, or tool generation logic. This allows GitMCP to provide tailored experiences for popular projects while maintaining fallback support for any GitHub repository.

Provides standardized MCP protocol compatibility enabling GitMCP to work with 8+ AI assistants (Claude, Cursor, Copilot, custom clients) without modification. The system implements the Model Context Protocol specification, exposing tools through a standard JSON schema that any MCP-compatible client can consume. This abstraction layer ensures that repository context is accessible to any AI assistant that supports MCP, regardless of the underlying LLM or client implementation.

Integrates with GitHub API to fetch repository content, metadata, and documentation with built-in rate limit handling and caching strategies. The system makes authenticated and unauthenticated GitHub API calls, respects rate limit headers, and implements exponential backoff for retries. Caching is performed at multiple levels (Cloudflare KV, in-memory) to minimize API calls and improve performance. This allows GitMCP to reliably access any public GitHub repository while staying within API quotas.

Provides a web interface that converts GitHub URLs into MCP server endpoints and handles both subdomain-based ({owner}.gitmcp.io/{repo}) and path-based (gitmcp.io/{owner}/{repo}) routing. The system uses pattern matching to extract repository metadata from URLs, validates GitHub repository existence, and generates shareable MCP endpoint URLs. The frontend (built with Remix) displays the generated endpoint and provides copy-to-clipboard functionality for easy sharing with AI assistants.

Implements a multi-stage documentation processing pipeline that extracts, normalizes, and structures content from various documentation formats (markdown, plaintext, code comments). The system parses documentation files, extracts metadata (title, description, code examples), and converts them into a standardized format suitable for AI consumption. This pipeline includes deduplication, formatting normalization, and optional content filtering to ensure documentation is clean and AI-friendly.

Generates and validates MCP tool schemas dynamically based on repository content and handler specifications. The system creates JSON schemas for each tool (e.g., 'search_documentation', 'analyze_code'), validates schema correctness against MCP specification, and exposes tools through the MCP protocol. Tool schemas include input parameters, output types, and descriptions that enable AI assistants to understand how to use each tool. The system ensures schema consistency and compatibility across different repository handlers.