ghcontext: Supercharge Your LLMs with Real-time GitHub Context

Created By
MarcoMuellnera year ago
An MCP server providing real-time GitHub data to LLMs, enhancing their software development capabilities.
Overview

What is ghcontext?

ghcontext is a server that provides real-time GitHub data to Large Language Models (LLMs), enhancing their capabilities in software development by ensuring they have access to the latest repository information.

How to use ghcontext?

To use ghcontext, you need to run it with a GitHub token for authentication. You can either run it directly using npx or install it globally via npm. Once set up, connect your MCP-compatible LLM to the ghcontext server endpoint to access GitHub data.

Key features of ghcontext?

  • Real-time access to GitHub repository information.
  • API documentation extraction from README files.
  • Repository structure analysis and content retrieval.
  • Intelligent caching to reduce API calls.

Use cases of ghcontext?

  1. Providing up-to-date API documentation to AI assistants.
  2. Enhancing code understanding for LLMs in software development.
  3. Assisting developers in finding specific code snippets or files in repositories.

FAQ from ghcontext?

  • What is required to run ghcontext?

A GitHub token is required for authentication to access repository data.

  • Can ghcontext work with private repositories?

Yes, ghcontext can access information from private repositories as long as the token has the necessary permissions.

  • Is there a limit to the number of API calls?

While ghcontext uses intelligent caching to minimize API calls, the actual limits depend on GitHub's API rate limits.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MarcoMuellner
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago