GitHub See MCP Server

Created By
JesusMastera year ago
GitHub MCP SSE Server
Overview

What is GitHub See MCP Server?

GitHub See MCP Server is a server-side implementation designed to facilitate the integration of AI capabilities with GitHub repositories through the Model Context Protocol (MCP). It manages context processing and interactions between repositories and AI models.

How to use GitHub See MCP Server?

To use the server, clone the repository, build the Docker image, and configure it with your GitHub OAuth credentials and AI model endpoints. You can run it using Docker with the necessary environment variables.

Key features of GitHub See MCP Server?

  • Real-time webhook processing for GitHub events
  • AI model communication via Model Context Protocol (MCP)
  • Event-driven architecture for handling repository actions
  • Custom configuration for repository-to-model mapping
  • Secure authentication with GitHub OAuth
  • Detailed logging and monitoring capabilities

Use cases of GitHub See MCP Server?

  1. Automating responses to GitHub events using AI.
  2. Integrating AI models to analyze code changes in real-time.
  3. Enhancing repository management with AI-driven insights.

FAQ from GitHub See MCP Server?

  • What are the prerequisites for using this server?

You need Node.js, MongoDB, valid GitHub OAuth credentials, and compatible AI model endpoints.

  • Is Docker required to run this server?

While Docker is recommended for ease of deployment, you can also run it directly on Node.js with the appropriate configurations.

  • How can I contribute to this project?

You can fork the repository, create a feature branch, and submit a pull request with your changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JesusMaster
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)

20 hours ago
Gpt Scrambler

2 days ago