GitHub MCP server
GitHub's own MCP server — issues, pull requests, code search and Actions, hosted by GitHub or run from the official image.
- Version:
- 1.7.0
- Publisher:
- sargonpiraev
Why you would use it
Your agents already live in pull requests. This is the server GitHub maintains, so tool names track the product instead of a third-party wrapper that lags a release behind.
The GitHub MCP server is the one most agents meet first: it turns a repository into tools the agent can call — list and comment on issues, open and review pull requests, search code, read workflow runs — with GitHub's own permission model deciding what the token may touch.
connect0 supports GitHub as a connection, so an agent on your account can pick up the credential it already holds instead of pasting a token into a config file.
Install
Generated from the server’s transport data — never hand-written. Placeholders in angle brackets are yours to fill.
Run it with its own identity, a budget you set, and every call audited — no local config to keep in sync.
Add to a connect0 projectYou will sign in first, then land back on this page.
What it can do
No capability summary yet — the publisher has not declared one and it has not been verified.
Setup gotchas
- The hosted endpoint wants an OAuth token with the scopes of the work you plan to hand the agent — start with read-only scopes and widen when a task needs write.
- The stdio distribution is a container image; make sure the client can reach a Docker daemon before pasting the snippet.