Same category · Developer tools
by github · github/github-mcp-server
GitHub provides hosted and local MCP servers. The remote endpoint supports PAT authentication; OAuth requires support from the host application. Local Docker remains an option.
GitHub provides hosted and local MCP servers. The remote endpoint supports PAT authentication; OAuth requires support from the host application. Local Docker remains an option.
Illustrative saved transcript; historical tool calls and timings are not current API documentation or a live execution.
{
"servers": {
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/"
}
}
}Use .vscode/mcp.json and complete sign-in when prompted. Other hosts must register a GitHub/OAuth app for OAuth support; remote PAT authentication is available to compatible HTTP clients. Check the host documentation.
{
"mcpServers": {
"github": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_PERSONAL_ACCESS_TOKEN",
"-e",
"GITHUB_READ_ONLY",
"ghcr.io/github/github-mcp-server"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_PAT>",
"GITHUB_READ_ONLY": "1"
}
}
}
}Requires Docker and a PAT with access to the selected repositories and tool permissions. Replace YOUR_PAT locally. GITHUB_READ_ONLY=1 suppresses write tools. The hosted endpoint can also use /mcp/readonly.
Client/version scope: Claude Desktop local Docker; VS Code 1.101+ remote HTTP. Other clients: pending verification.
Suggested prompts, not measured outcomes. Installation and listed tools were reviewed; these workflows were not executed.
Find open issues in modelcontextprotocol/servers labeled 'good first issue' with no assignee and zero comments. Pick the one that looks easiest to fix and explain why.
Pull the full issue body for #<num> and read the file it mentions. Tell me the actual change that needs to happen.
Apply the change, write a PR description that thanks the maintainer and explains the fix in 3 sentences.
List all PRs merged into our `org/repo` between last Monday and today. Include author, +/- lines, and one-line summary.
Group these by area (auth, payments, frontend, infra...) and flag any that look like reverts or hotfixes.
Now write a Slack post summarizing the week — celebrate the big wins, call out the risky changes, name the people who shipped them.
Search across our entire `acme-corp` org for any usage of the `LegacyAuth` class. Return file paths grouped by repo.
For each match, fetch 5 lines around the usage and tell me whether it's a real call or just a comment/import.
Create a tracking issue in `acme-corp/platform` titled 'Migrate off LegacyAuth' with a checklist of every real callsite and the team that owns each repo.
Fetch PR #<num> in `org/repo` — give me the diff and the description. What's the author claiming this does?
Now look at the existing files this PR touches. Does the change fit the existing patterns, or does it introduce a new one? If new, is the new pattern justified?
Where in this diff is something most likely to break in production 6 months from now? Be specific — point to the line.
Find open PRs in `org/repo` last updated more than 5 days ago. For each, tell me the author, the assigned reviewer, and the stated reason for delay (look at the last comment).
Group these into: 'waiting on reviewer', 'waiting on author', 'waiting on CI', 'waiting on decision'. Be specific about which.
For the 'waiting on reviewer' bucket, draft a polite nudge comment for each. Different tone if the reviewer is a peer vs senior to the author.
Integration compatibility: pending verification. Treat these as suggested workflows.
There's a new error in Sentry — issue WEB-3a91. Find which commit on main introduced it (cross-reference the release tag), then draft the smallest possible revert PR.
For every issue opened in our `octocat/api` repo this week with label 'bug', create a matching Linear issue in the BACKEND team with priority Medium.
Clone `acme/widgets` locally, fix the typo in src/utils/format.ts:42, push to a new branch, open a PR.
Selected parameters checked against upstream definitions. Consult the connected server tools/list for your installed version.
query: string, owner?: string, repo?: string, page?: integer, perPage?: integer (1–100), sort?: string, order?: string, fields?: string[]Find matching issues
method: string, owner: string, repo: string, issue_number: number; method-specific optional parametersRead issue context
method: string, owner: string, repo: string, pullNumber: number; method-specific optional parametersRead PR metadata or diff
api_quota: pending verification
per_call_tokens: pending verification
monetary: pending verification: see current upstream pricing and hosting requirements.
budget_tip: Limit requested data and inspect actual output before expanding queries.
Local Docker: GITHUB_PERSONAL_ACCESS_TOKEN. Remote OAuth: client sign-in.
Remote MCP connects to api.githubcopilot.com; local tools use GitHub APIs. Complete network audit pending review.
Repository access and permissions depend on selected tools; use host consent or PAT settings.
Local Docker: GITHUB_READ_ONLY=1; remote: /mcp/readonly.
CVE status and a full security audit: pending verification.
Check that the host has OAuth/GitHub app support; otherwise use documented PAT authentication or local Docker.
Pending verification: alternative projects and tradeoffs have not been rechecked.
Documentation checked 2026-10-08. No authenticated service was executed. Unchecked claims are marked pending verification.