GitGuardian MCP Server

Official

Bring GitGuardian secret detection and incident management into your AI agent

★ 37 Stars Category · Dev Tools Popular

52FMRS · D

An official GitGuardian-maintained MCP server that brings secret scanning, incident management, and honeytokens into AI agents. It supports hosted HTTP, self-hosted Docker, and local stdio (PAT) deployments, with the tool set gated by token OAuth scopes and a read-only-leaning default. Before use, confirm the region URL and auth mode, and be aware of the hosted request path plus the operational risk of automated code-fix pull requests.

Reliability

8/20

Security and permissions

12/20

Maintenance

11/20

Documentation

13/20

Setup experience

8/20

Read the FMRS scoring method →

GitGuardian MCP Server is maintained by GitGuardian and brings its secret detection and incident management into AI agents. Backed by GitGuardian's API and 500+ detectors, it scans files for leaked credentials before they are public, lists and manages security incidents (including internal and Public Monitoring incidents), generates and lists honeytokens, and opens pull requests that remediate secrets. The server defaults to read-only-leaning permissions, and the exact set of exposed tools depends on the OAuth scopes held by your access token. It can run as a hosted HTTP server (US: https://mcp.gitguardian.com/mcp, EU: https://mcp.eu1.gitguardian.com/mcp), a self-hosted Docker image, or locally over stdio with a PAT.

Tools

secret_scanning

Proactively scan files for leaked credentials

incident_management

List, filter, assign, resolve, and tag incidents, including both internal and Public Monitoring incidents

honeytokens

Generate honeytokens and list existing ones

code_fix_automation

Open pull requests that remediate secrets in repositories your workspace monitors

Setup

The recommended way is the hosted server: point your MCP client at the URL matching your GitGuardian region; the client handles OAuth automatically. For Cursor, edit ~/.cursor/mcp.json: {"mcpServers":{"GitGuardian":{"type":"http","url":"https://mcp.gitguardian.com/mcp"}}}. Windsurf uses {"mcp":{"servers":{"GitGuardian":{"type":"http","url":"https://mcp.gitguardian.com/mcp"}}}}. For Claude.ai (web), add the server in Settings → Connectors → Add custom connector. Claude Desktop and Zed use the same type: http snippet. For local stdio (PAT) mode, use the command uvx --from git+https://github.com/GitGuardian/ggmcp.git gg-mcp-server with ENABLE_LOCAL_OAUTH=false, GITGUARDIAN_PERSONAL_ACCESS_TOKEN, and GITGUARDIAN_URL; on macOS, Claude Desktop needs the absolute path to uvx. To self-host, run the ghcr.io/gitguardian/mcp-server image behind a TLS-terminating reverse proxy; it exposes the StreamableHTTP transport on port 8000 by default.

claude_desktop_config.json

{"mcpServers":{"GitGuardian":{"type":"http","url":"https://mcp.gitguardian.com/mcp"}}}

Generate and validate client config

Fit and risk

Best for

Teams already using GitGuardian SaaS (US/EU) or a self-hosted instance
Developers who want secret scanning, incident triage, and remediation inside their IDE or chat client
Teams that want to automate secret remediation via pull requests
Users of MCP clients that support type: http and can complete an OAuth flow
CI/CD, scripts, or airgapped environments that need local stdio with a PAT

Not for

Users who do not use GitGuardian and do not want to connect to its API
Users limited to older MCP clients without type: http support who cannot use the local stdio fallback
Users expecting the server to work with no authentication or scope configuration
Hosted-service users who do not want requests to transit mcp.gitguardian.com (they should self-host instead)

Required permissions

Requires a GitGuardian access token (OAuth or PAT); the exposed tool set is determined by the token's OAuth scopes
Local stdio mode uses the GITGUARDIAN_PERSONAL_ACCESS_TOKEN environment variable
Self-hosted OAuth proxy mode proxies /authorize, /token, and /register to your GitGuardian dashboard
PAT lifetime defaults to 30 days and is configurable via GITGUARDIAN_TOKEN_LIFETIME
The server defaults to read-only-leaning permissions

Risks and side effects

MCP servers are an emerging technology; agents act on your behalf and under your responsibility
In hosted mode, requests transit mcp.gitguardian.com in addition to api.gitguardian.com
Token scopes determine which tools the agent can use; overly broad scopes increase blast radius
Code-fix automation opens pull requests, so agent actions should be reviewed
Browser-driven OAuth in stdio mode is deprecated and stores the PAT on disk; that code path will be removed in a future release

Troubleshooting

Verify the URL matches your GitGuardian region: US uses https://mcp.gitguardian.com/mcp, EU uses https://mcp.eu1.gitguardian.com/mcp
For self-hosted deployments on a gitguardian.com/gitguardian.tech domain, set IS_ON_PREM=true explicitly, since hostname guessing fails
For local stdio, set ENABLE_LOCAL_OAUTH=false and provide GITGUARDIAN_PERSONAL_ACCESS_TOKEN
Claude Desktop on macOS needs the absolute path to uvx; it does not resolve $PATH
If tools are missing, check the access token's OAuth scopes
Older clients without type: http support can use the local stdio fallback
The developer-mcp-server and secops-mcp-server console scripts are deprecated; invoke gg-mcp-server directly

Use cases

Scan a codebase for leaked secrets or credentials

Remediate all incidents related to a project

Check if there are any new security incidents assigned to you

Understand a security incident and get remediation steps

List all active honeytokens

Generate a honeytoken for monitoring AWS credential access

Create a honeytoken named 'dev-database' and hide it in config files

Supported clients

CursorFull support

Claude DesktopPartial support

Claude.aiFull support

WindsurfFull support

ZedFull support

Related MCP servers

Compare with other MCP servers