GitHub MCP Server

Created By
tradesdontliea year ago
A GitHub MCP Server with SSE transport built with TypeScript and Express
Overview

what is GitHub MCP Server?

GitHub MCP Server is a Model Context Protocol (MCP) server designed to provide tools for managing GitHub repositories and task management.

how to use GitHub MCP Server?

To use GitHub MCP Server, clone the repository, install the dependencies, set up your GitHub token in the .env file, and run the server using npm start.

key features of GitHub MCP Server?

  • GitHub Integration: Create and manage issues, handle pull requests, and work with repositories.
  • Task Management: Create and organize tasks with priorities, track dependencies, mark tasks as complete, and get the next highest priority task to work on.

use cases of GitHub MCP Server?

  1. Managing GitHub issues and pull requests efficiently.
  2. Organizing and prioritizing tasks for software development projects.
  3. Tracking task dependencies to streamline project workflows.

FAQ from GitHub MCP Server?

  • Can I use GitHub MCP Server for any GitHub repository?

Yes! GitHub MCP Server can be used with any GitHub repository as long as you have the necessary permissions.

  • Is there a setup guide available?

Yes! Detailed setup instructions are provided in the repository's documentation.

  • What programming language is GitHub MCP Server built with?

GitHub MCP Server is built with TypeScript and Express.

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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