GitHub MCP Server

Created By
brukhabtua year ago
A Management Control Panel server for GitHub projects using Issues API
Overview

what is GitHub MCP Server?

GitHub MCP Server is a Management Control Panel (MCP) server designed for managing GitHub projects using the GitHub Issues API, allowing users to manage tasks and team collaboration without directly using GitHub's Projects feature.

how to use GitHub MCP Server?

To use the GitHub MCP Server, clone the repository, install the dependencies, set up your GitHub Personal Access Token, and start the server. Access the MCP interface through your browser at http://localhost:3000.

key features of GitHub MCP Server?

  • View all your repositories
  • Create, update, and track issues across repositories
  • Assign issues to team members
  • Add comments to issues
  • Create and manage labels to categorize tasks
  • View repository milestones
  • See repository collaborators

use cases of GitHub MCP Server?

  1. Managing multiple GitHub repositories efficiently.
  2. Collaborating with team members on tasks and issues.
  3. Organizing project tasks with labels and milestones.

FAQ from GitHub MCP Server?

  • What are the prerequisites to run GitHub MCP Server?

You need Node.js (v14 or higher), npm or yarn, and a GitHub Personal Access Token with repo scope.

  • Can I customize the GitHub MCP Server?

Yes! You can add more API endpoints, create a custom frontend, implement authentication, and add database support for project metadata.

  • Is there a license for GitHub MCP Server?

Yes, it is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
brukhabtu
Star
0
Language
JavaScript
License
-
Tags

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