GitGuardian MCP Server

The GitGuardian MCP Server is the official Model Context Protocol implementation from GitGuardian, exposing the platform's secrets detection, incident management, and honeytoken capabilities to AI coding agents like Cursor, Claude Desktop, Windsurf, and Zed. It lets agents scan code for leaked credentials, investigate active incidents, and embed decoy tokens without leaving the IDE.

The server bundles a developer-mcp-server package that wraps the GitGuardian REST API. It leverages 500+ secret detectors to find API keys, tokens, certificates, and other credentials in source code, then surfaces remediation steps and file/line locations for matched occurrences. Honeytoken tools let teams generate AWS decoy credentials with placement recommendations to catch unauthorized access.

By default the server runs locally over stdio and uses OAuth to authenticate to the GitGuardian dashboard, caching tokens in ~/.gitguardian/. It also supports Personal Access Tokens for CI/CD and an HTTP/SSE transport with per-request Authorization headers for shared deployments. Both GitGuardian SaaS (US and EU) and self-hosted instances are supported via the GITGUARDIAN_URL env var.

Tools

Prerequisites

• Install uv (Astral's Python package manager): https://docs.astral.sh/uv/getting-started/installation/
• A GitGuardian account (free tier works). OAuth flow opens automatically on first run.

Claude Desktop

Edit ~/Library/Application Support/Claude Desktop/mcp.json (macOS) or %APPDATA%\Claude Desktop\mcp.json (Windows). Use the absolute path to uvx:

{
  "mcpServers": {
    "GitGuardianDeveloper": {
      "command": "/path/to/uvx",
      "args": [
        "--from",
        "git+https://github.com/GitGuardian/ggmcp.git",
        "developer-mcp-server"
      ]
    }
  }
}

Cursor

Edit ~/.cursor/mcp.json (or use the one-click install button in the README):

{
  "mcpServers": {
    "GitGuardianDeveloper": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/GitGuardian/ggmcp.git",
        "developer-mcp-server"
      ]
    }
  }
}

Personal Access Token (CI/CD)

Disable interactive OAuth and pass a PAT for non-interactive environments:

{
  "mcpServers": {
    "GitGuardianDeveloper": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/GitGuardian/ggmcp.git", "developer-mcp-server"],
      "env": {
        "ENABLE_LOCAL_OAUTH": "false",
        "GITGUARDIAN_PERSONAL_ACCESS_TOKEN": "your_pat_here"
      }
    }
  }
}

Useful env vars

• GITGUARDIAN_URL: defaults to https://dashboard.gitguardian.com. Use https://dashboard.eu1.gitguardian.com for EU or your self-hosted URL.
• GITGUARDIAN_SCOPES: override OAuth scopes (e.g. add honeytokens:read,honeytokens:write).
• GITGUARDIAN_TOKEN_LIFETIME: default 30 days.
• MCP_PORT / MCP_HOST: enable HTTP/SSE transport for shared deployments.

• Block leaked secrets in AI-generated code by running scan before the agent commits or opens a PR.
• Triage open incidents from the IDE: list filtered by severity, fetch full incident details, and follow remediate_incidents instructions inline.
• Pinpoint exposed credentials with list_repo_occurrences to get exact file paths and line numbers for rotation.
• Plant AWS honeytokens in legacy code or sample configs with generate_honeytoken to detect unauthorized access.
• Audit your GitGuardian workspace from the agent: list monitored sources, available detectors, and workspace members.

• "Scan this repository for leaked secrets and show me the file paths and line numbers."
• "List all open incidents with critical severity assigned to my workspace."
• "Walk me through remediating incident 12345 and rotate the affected credential."
• "Generate an AWS honeytoken called legacy-deploy-key and suggest where to embed it in this codebase."
• "Show me every active honeytoken in the workspace and who created them."

• Official, vendor-maintained server from GitGuardian, distributed straight from the GitGuardian/ggmcp repo.
• Read-only by default with OAuth, plus PAT support for CI and HTTP transport for shared deployments.
• Covers the full developer workflow: detection, incident triage with file/line context, remediation guidance, and honeytokens.
• Works against GitGuardian SaaS (US/EU) and self-hosted instances via a single env var.

• Requires uv/uvx and a GitGuardian account; some features (honeytokens, full incident management) need a paid plan.
• SecOps profile (incident assignment, status changes, custom tags, automated fix PRs) is still on the roadmap, so this server is focused on developer use.
• Honeytoken generation is limited to AWS placement recommendations today.

• Semgrep MCP Server: SAST scanning for code vulnerabilities, broader than secrets.
• Snyk MCP Server: vulnerability scanning across SCA, SAST, and IaC.
• TruffleHog: open-source secret scanner; no official MCP server but commonly wrapped by community implementations.