GitHub MCP Server
Provides tools to interact with the GitHub API, including retrieving authenticated user info, repository metadata, file contents, listing issues, and creating issues.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GitHub MCP ServerShow me the metadata for the repo octocat/Hello-World"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GitHub MCP Server (Streamable HTTP, stateless)
TypeScript MCP server that exposes 5 GitHub tools over stateless Streamable HTTP.
No sessions / no mcp-session-id — each POST is independent (good for gateways and multi-instance deploy).
The GitHub access-token header is required only for tools/call.initialize, tools/list, and other discovery methods work without a token.
Tools
Tool | Description |
| Authenticated user for the token |
| Repository metadata ( |
| File or directory contents ( |
| List issues (PRs filtered out) |
| Create an issue ( |
Related MCP server: @cloud9-labs/mcp-github
Requirements
Node.js 18+
A GitHub personal access token (classic or fine-grained) with the scopes your tools need
Read tools:
repo(or public-only fine-grained read)create_issue: issues write on the target repo
Setup
npm install
npm run build
npm startDev (no build step):
npm run devDocker
docker build -t github-mcp .
docker run --rm -p 3000:3000 github-mcpMCP endpoint: http://localhost:3000/mcp.
Server listens on http://localhost:3000/mcp (override with PORT).
Authentication
MCP method |
|
| No |
| Yes |
On tool calls, send a GitHub personal access token:
access-token: ghp_your_token_hereAlternatively:
Authorization: Bearer ghp_your_token_hereMissing token on tools/call → 401 JSON-RPC error.
Client configuration
Point any Streamable HTTP MCP client at:
http://localhost:3000/mcpSend the GitHub token on tool-call requests (many clients set it for all requests to the server):
{
"mcpServers": {
"github": {
"url": "http://localhost:3000/mcp",
"headers": {
"access-token": "ghp_your_token_here"
}
}
}
}(Exact client config shape depends on the client.)
Health check
curl http://localhost:3000/healthProject layout
src/
index.ts # Express + stateless Streamable HTTP (POST only), access-token middleware
server.ts # McpServer factory
tools.ts # 5 tool registrations
github.ts # GitHub REST client
context.ts # AsyncLocalStorage for per-request tokenLicense
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
Host your MCP tool over streamable HTTP in one command.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceA context-efficient GitHub MCP server designed for AI agents to manage repositories, issues, pull requests, and actions directly via cloud workflows. It focuses on a compact tool surface to minimize context waste while providing comprehensive read and write coverage without requiring a local Git CLI.-
- AlicenseBqualityDmaintenanceMCP (Model Context Protocol) server for GitHub API integration. This server provides comprehensive tools for interacting with GitHub repositories, issues, pull requests, branches, and code search through a unified interface.155 npmMIT
- FlicenseNot gradedqualityBmaintenanceA lightweight MCP server that exposes GitHub operations as tools over HTTP, enabling any MCP-compatible client to interact with GitHub repositories without a built-in connector.1-
- AlicenseAqualityCmaintenanceA lightweight MCP server that enables fetching public GitHub user profiles, repository stats, recent events, and pull request insights through simple tool calls.248 npm1MIT