GitHub MCP Server - Local Docker Setup

Created By
shesadria year ago
Local Docker setup for GitHub MCP Server with docker-compose
Overview

What is GitHub MCP Server?

The GitHub MCP Server is a Model Context Protocol (MCP) server that allows developers to integrate with GitHub APIs for advanced automation and interaction capabilities.

How to use GitHub MCP Server?

To use the GitHub MCP Server, clone the repository, configure your GitHub Personal Access Token, and run the server using Docker Compose. Access it via HTTP on port 3000.

Key features of GitHub MCP Server?

  • Easy setup with Docker Compose
  • HTTP access on port 3000
  • Configurable with various toolsets
  • Auto-restart on failure

Use cases of GitHub MCP Server?

  1. Automating repository management tasks
  2. Integrating GitHub functionalities into custom applications
  3. Enhancing development workflows with automated tools

FAQ from GitHub MCP Server?

  • What is required to run the server?

You need Docker, Docker Compose, and a GitHub Personal Access Token.

  • Can I customize the toolsets?

Yes! You can enable specific toolsets by configuring the environment variables.

  • How do I check the server status?

Use the command curl http://localhost:3000/health to check the server status.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shesadri
Star
0
Language
JavaScript
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