GitHub MCP Server
OFFICIAL SERVERLets an assistant read code and manage repositories, issues, pull requests and Actions on GitHub.
Secret scanning, incident triage, honeytokens and fixes from a GitGuardian workspace
Official · GitGuardian Python Remote (hosted) · Streamable HTTPLocal · stdio SecurityDevOps and monitoring
40 popularity score ★ 41
Opens the app, which asks before it adds the server.
claude mcp add --transport http gitguardian https://mcp.gitguardian.com/mcphttps://mcp.gitguardian.com/mcphttps://mcp.gitguardian.com/mcp{
"mcpServers": {
"gitguardian": {
"url": "https://mcp.gitguardian.com/mcp"
}
}
}{
"servers": {
"gitguardian": {
"type": "http",
"url": "https://mcp.gitguardian.com/mcp"
}
}
}[mcp_servers.gitguardian]
url = "https://mcp.gitguardian.com/mcp"gemini mcp add --scope user --transport http gitguardian https://mcp.gitguardian.com/mcpOpens the app, which asks before it adds the server.
claude mcp add gitguardian -- uvx --from git+https://github.com/GitGuardian/ggmcp.git gg-mcp-server{
"mcpServers": {
"gitguardian": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/GitGuardian/ggmcp.git",
"gg-mcp-server"
]
}
}
}{
"mcpServers": {
"gitguardian": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/GitGuardian/ggmcp.git",
"gg-mcp-server"
]
}
}
}{
"servers": {
"gitguardian": {
"type": "stdio",
"command": "uvx",
"args": [
"--from",
"git+https://github.com/GitGuardian/ggmcp.git",
"gg-mcp-server"
]
}
}
}[mcp_servers.gitguardian]
command = "uvx"
args = ["--from", "git+https://github.com/GitGuardian/ggmcp.git", "gg-mcp-server"]gemini mcp add --scope user gitguardian uvx -- --from git+https://github.com/GitGuardian/ggmcp.git gg-mcp-serverGITGUARDIAN_PERSONAL_ACCESS_TOKEN |
Optional: Personal access token for local stdio use; its scopes decide which tools appear. |
|---|---|
ENABLE_LOCAL_OAUTH |
Optional: Set to false to use a token instead of the deprecated browser sign-in in stdio mode. |
GITGUARDIAN_URL |
Optional: GitGuardian dashboard URL; defaults to https://dashboard.gitguardian.com (US SaaS). |
IS_ON_PREM |
Optional: true for a self-hosted GitGuardian instance. |
GITGUARDIAN_SCOPES |
Optional: Comma-separated OAuth scopes to request. |
GITGUARDIAN_TOKEN_LIFETIME |
Optional: Lifetime in days of OAuth-issued tokens, or never; default 30. |
MCP_PORT |
Optional: Port for HTTP transport; unset means stdio. |
MCP_BASE_URL |
Optional: Public URL of a self-hosted server in OAuth proxy mode. |
MCP_OAUTH_PROXY_ENABLED |
Optional: Makes a self-hosted server proxy OAuth to the GitGuardian dashboard. |
GitGuardian's MCP server connects an assistant to a GitGuardian workspace. Through it the assistant can send file contents to GitGuardian's detection API to check for leaked credentials, read and filter the secret incidents GitGuardian has already raised, and act on them: assign, resolve, ignore or reopen an incident, change its severity, add tags and comments, or revoke a secret.
It covers two kinds of incidents kept apart by separate tools: internal ones found in the repositories and other sources a workspace has connected, and Public Monitoring ones found on public GitHub, gists and Docker Hub. It can also create AWS honeytokens and list existing ones, and ask GitGuardian to open pull requests that remove secrets from monitored repositories.
The makers recommend the hosted endpoint, where the MCP client signs in with OAuth and nothing is installed (US and EU regions have separate URLs). It can also run locally over stdio with a personal access token, or be self-hosted from a Docker image for self-hosted GitGuardian. Which tools appear depends on the scopes held by the token in use.
| To run it yourself | Python |
|---|
A GitGuardian account (US or EU SaaS, or a self-hosted GitGuardian instance). The hosted endpoint needs an MCP client that supports HTTP transport and OAuth. Local stdio use needs uv (uvx) and a GitGuardian personal access token; self-hosting needs Docker and a reverse proxy terminating TLS.
Tools shown depend on the scopes of the access token. Many tools work only on internal incidents or only on Public Monitoring incidents, and the IDs are not interchangeable. Honeytokens it generates are AWS type only. Browser-based OAuth in stdio mode is deprecated and will be removed; the old developer-mcp-server and secops-mcp-server commands are deprecated too. With the hosted server, requests pass through mcp.gitguardian.com as well as the GitGuardian API.
Suits teams already on GitGuardian who want an assistant to check code for secrets before committing and to work through their incident queue; it is official and the hosted endpoint needs no install. It is of no use without a GitGuardian account. Because it can resolve incidents and revoke secrets, those wanting read-only use should grant a token with read scopes only. Self-hosted or airgapped setups should use the Docker image or local stdio with a token.
scan_secretslist_detectorslist_incidentscount_incidentsget_incidentlist_repo_occurrenceslist_remediation_targetsget_remediation_workflowfind_current_source_idlist_sourceslist_public_incidentsget_public_incidentlist_public_occurrenceslist_incident_memberslist_incident_teamslist_incident_commentslist_public_incident_commentslist_incident_activity_logslist_public_incident_activity_logsmanage_private_incidentassign_incidentupdate_incident_severityupdate_or_create_incident_custom_tagsmanage_incident_commentassign_public_incidentupdate_public_incident_statusmanage_public_incident_commentcreate_code_fix_requestrevoke_secretgenerate_honeytokenlist_honeytokensread_custom_tagswrite_custom_tagslist_usersget_memberget_current_token_info