Gg MCP Server

If you already use Gg MCP, the gg mcp mcp server is the piece that lets your assistant work with it directly. Bring GitGuardian's secret detection and incident management into your AI agent. Scan code for credentials before they leak, triage existing incidents, generate honeytokens, and remediate findings — all from inside your IDE or chat client.

What the server does

• Secret scanning — — proactively scan files for leaked credentials
• Incident management — — list, filter, assign, resolve, and tag incidents
• Honeytokens — — generate honeytokens and list existing ones
• Code-fix automation — — open pull requests that remediate secrets in

Available tools

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

• Honeytokens — generate honeytokens and list existing ones
• Code — fix automation** — open pull requests that remediate secrets in
• Region — URL
• Self-hosted — See Self-hosting the MCP server
• Deployment — When to use
• Mode — Configuration
• Variable — Description
• GITGUARDIAN_URL — GitGuardian dashboard URL
• IS_ON_PREM — true => self-hosted; false => SaaS; unset ⇒ guess from hostname
• GITGUARDIAN_PERSONAL_ACCESS_TOKEN — PAT (overrides OAuth)
• GITGUARDIAN_SCOPES — Comma-separated OAuth scopes to request
• GITGUARDIAN_CLIENT_ID — OAuth client ID

Credentials and setup notes

Configuration is passed through the environment: ENABLE_LOCAL_OAUTH, GITGUARDIAN_PERSONAL_ACCESS_TOKEN, GITGUARDIAN_URL, MCP_BASE_URL, GITGUARDIAN_CLIENT_ID. 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. Gg MCP's toolset — Honeytokens, Code, Region and 11 more — is a fair guide to whether it matches your workflow. It is maintained by GitGuardian; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Gg MCP'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 Gg MCP.
• 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.