ghcontext: Supercharge Your LLMs with Real-time GitHub Context
About
An MCP server providing real-time GitHub data to LLMs, enhancing their software development capabilities.
Details
- Author
- MarcoMuellner
- Downloads
- 351
- Categories
- Developer Tools
Jump to
- API documentation extraction from READMEs and doc files
- Repository structure analysis for a codebase map
- README content retrieval directly from GitHub
- File content search for specific files or snippets
- Repository search to discover matching repositories
- Intelligent caching to reduce API calls while keeping info fresh
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
ghcontext: Supercharge Your LLMs with Real-time GitHub ContextCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install and run via npx ghcontext --GITHUB_TOKEN your_github_token or globally with npm install -g ghcontext then ghcontext --GITHUB_TOKEN your_github_token. After starting, connect your MCP‑compatible LLM to http://localhost:3000/api/mcp. The server exposes tools such as get-repository-info, get-repository-readme, and get-repository-api-docs.
search-repositories
Search for GitHub repositories by query
get-repository-info
Get detailed information about a specific GitHub repository
get-repository-readme
Get the README content of a GitHub repository
search-repository-files
Search for files in a GitHub repository
get-file-content
Get the content of a specific file from a GitHub repository
get-repository-structure
Get the directory structure of a GitHub repository
get-repository-api-docs
Extract API documentation from a GitHub repository README
search-repository-code
Search for code within a GitHub repository
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"ghcontext: supercharge your llms with real-time github context": {
"ghcontext": {
"command": "npx",
"args": [
"ghcontext",
"--GITHUB_TOKEN",
"your_github_token"
]
}
}
}
}
McpServers
{
"ghcontext": {
"command": "npx",
"args": [
"ghcontext",
"--GITHUB_TOKEN",
"your_github_token"
]
}
}
ghcontext: Supercharge Your LLMs with Real-time GitHub Context
> "But my GitHub repo changed yesterday..." - Never worry about outdated information in your AI assistants again.
ghcontext (GitHub Context Provider) bridges the gap between GitHub and Large Language Models, giving AI assistants real-time access to repository information through the standardized Model Context Protocol (MCP).
<p align="center">

</p>
🔥 Why ghcontext?
- Accurate, Real-time Information: LLMs often have outdated knowledge about repositories. ghcontext provides the latest API docs, README contents, and codebase structure - Also for private repos
- Deeper Understanding: Help LLMs grasp your project's architecture, design principles, and API usage patterns.
- Seamless Integration: Compatible with any MCP-enabled models, including Claude, GPT, and others.
- Highly Efficient: Intelligent caching reduces API calls while keeping information fresh.
✨ Key Features
- API Documentation Extraction: Automatically identifies and extracts API documentation from READMEs and dedicated documentation files
- Repository Structure Analysis: Provides a map of your codebase's organization
- README Content Retrieval: Gets the latest documentation directly from GitHub
- File Content Search: Find and extract specific files or code snippets
- Repository Search: Discover repositories matching specific criteria
🚀 Quick Start
A note on tokens
ghcontext requires a GitHub token for authentication. You are responsible for managing your token securely, and you should give it only the scopes really necessary for your use case.
For example, if you only need to read public repositories, you can create a token with the public_repo scope. ghcontext does not need write access to your repositories.
Installation
Method 1: Run without Installation using npx
```bash
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





