Github MCP Server

If you already use Github, the github mcp server is the piece that lets your assistant work with it directly. GitHub security posture audit tools for AI agents — organization, repository, Actions, secrets, supply chain analysis via MCP.

What the server does

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• github_check_org_security — 2FA enforcement, default repo visibility, member creation privileges
• github_check_org_sso — SSO/SAML configuration via GraphQL
• github_check_org_members — Outside collaborators, stale member detection
• github_check_org_apps — OAuth credential authorizations, GitHub App installation permissions
• github_check_org_webhooks — Insecure webhook URLs (HTTP, no secret)
• github_check_org_audit_log — Suspicious audit log activity (Enterprise)
• github_list_org_repos — List all repos in an org with security metadata
• github_check_repo_branch_protection — Branch protection rules on default branch
• github_check_repo_secrets — Secret scanning and push protection enablement
• github_check_repo_code_scanning — CodeQL / code scanning enabled, open alerts
• github_check_repo_dependabot — Dependabot enabled, critical alert triage
• github_check_repo_settings — SECURITY.md, private vulnerability reporting, fork restrictions

Credentials and setup notes

Configuration is passed through the environment: GITHUB_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Github's toolset — github_check_org_security, github_check_org_sso, github_check_org_members and 11 more — is a fair guide to whether it matches your workflow. It is maintained by orhnyldrm; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Github's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Github.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.