Skip to content
GitGuardianPublic

About

GitGuardian MCP server for AI-assisted secrets remediation: SecOps run it at scale across the organization, developers fix incidents in their repo.

Topics

Resources

Stars

44 stars

Watchers

6 watching

Forks

Repository files navigation

GitGuardian MCP Server

Remediate leaked secrets from your AI agent, from a single repository to your whole organization.

The GitGuardian MCP server connects any MCP client to GitGuardian's secrets detection and incident management. Your agent gets the same view of your incidents as the GitGuardian dashboard, and can act on them for you.

Built for two jobs

SecOps and AppSec: orchestrate remediation at scale

  • Triage the backlog. List, count and prioritize internal and Public Monitoring incidents by severity, validity, source, tag or assignee.
  • Route the work. Assign incidents to the right developer or team, set severity, add tags and comments, across the whole workspace.
  • Close the loop. Resolve, ignore or reopen incidents, revoke exposed secrets, and deploy honeytokens.

Developers: fix incidents in the repository you work on

  • See what's yours. Get the incidents assigned to you and the leaks in the current repository, with their exact locations and history.
  • Fix them in place. Follow GitGuardian’s remediation workflow, or your organization’s own, to remove the secret from the code and get it rotated.

Caution

Agents act with your permissions. Review actions that modify incidents, create credentials, or revoke secrets, and grant only the scopes you need.

Quick start: hosted server

Add the URL for your GitGuardian region through your client's remote MCP setup and complete the OAuth sign-in:

Region URL
US https://mcp.gitguardian.com/mcp
EU https://mcp.eu1.gitguardian.com/mcp

Example for clients using an mcpServers configuration:

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

Hosted requests pass through the GitGuardian MCP service. To run the server on your own machine or infrastructure, use local stdio or self-hosting.

Try asking your agent:

  • "Scan this codebase for leaked credentials."
  • "Explain the security incidents assigned to me and suggest remediation steps."
  • "Generate an AWS honeytoken named dev-database."

Local stdio

Install uv and add this local-server configuration to your MCP client. Requests go from your machine to the configured GitGuardian API.

{
  "mcpServers": {
    "GitGuardian": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/GitGuardian/ggmcp.git",
        "gg-mcp-server"
      ],
      "env": {
        "GITGUARDIAN_URL": "https://dashboard.gitguardian.com"
      }
    }
  }
}

Set GITGUARDIAN_URL to your dashboard URL. Browser login is enabled by default; the first tool call opens a login flow and stores the resulting PAT locally for reuse. Each login creates a new PAT in your GitGuardian account.

For headless use, add GITGUARDIAN_PERSONAL_ACCESS_TOKEN and ENABLE_LOCAL_OAUTH=false to env. Create a PAT under API → Personal Access Tokens in your GitGuardian dashboard. Keep real tokens out of committed configuration.

Clients that cannot find uvx through PATH need its absolute path in command. For optional Sentry support, use ggmcp[sentry] @ git+https://github.com/GitGuardian/ggmcp.git as the --from value and configure SENTRY_DSN.

Self-hosting

Run the published Docker image behind a reverse proxy that terminates TLS, then connect your MCP clients to its /mcp endpoint:

docker run -p 8000:8000 \
  -e GITGUARDIAN_URL=https://dashboard.gitguardian.mycorp.local \
  -e IS_ON_PREM=true \
  -e MCP_BASE_URL=https://mcp.mycorp.local \
  -e MCP_OAUTH_PROXY_ENABLED=true \
  -e MULTI_TENANCY_ENABLED=true \
  -e MCP_PORT=8000 \
  -e ENABLE_LOCAL_OAUTH=false \
  ghcr.io/gitguardian/mcp-server:latest \
  gunicorn --workers=4 --worker-class=uvicorn.workers.UvicornWorker \
           -b 0.0.0.0:8000 gg_mcp_server.http_app:app
  • IS_ON_PREM=true selects the self-hosted GitGuardian API path and supported scopes, overriding hostname detection. Set it explicitly for self-hosted GitGuardian instances.
  • MCP_BASE_URL is the public URL of your MCP server.
  • MCP_OAUTH_PROXY_ENABLED=true enables OAuth discovery and proxies authorization to your GitGuardian dashboard.
  • HTTP requires MULTI_TENANCY_ENABLED=true and MCP_PORT. Every request uses its own bearer token; the server refuses HTTP startup without multi-tenancy.

For HTTP clients that send a PAT directly, leave MCP_OAUTH_PROXY_ENABLED unset, keep ENABLE_LOCAL_OAUTH=false, and send Authorization: Bearer <PAT> with each request.

Configuration

Environment variables
Variable Purpose Default
GITGUARDIAN_URL GitGuardian dashboard URL https://dashboard.gitguardian.com
IS_ON_PREM true: self-hosted; false: SaaS; unset: detect from hostname Unset
GITGUARDIAN_PERSONAL_ACCESS_TOKEN PAT for local stdio Unset
GITGUARDIAN_SCOPES Comma-separated OAuth scopes to request Scopes used by the tools
GITGUARDIAN_CLIENT_ID OAuth client ID ggshield_oauth
GITGUARDIAN_TOKEN_NAME Name for a local OAuth-issued PAT MCP Token
GITGUARDIAN_TOKEN_LIFETIME Local OAuth PAT lifetime in days, or never 30
MCP_PORT Enable HTTP on this port; unset selects stdio Unset
MULTI_TENANCY_ENABLED Use each request's bearer token; required for HTTP false
MCP_HOST HTTP bind address 127.0.0.1
MCP_BASE_URL Public MCP server URL for OAuth discovery http://localhost:8000
MCP_OAUTH_PROXY_ENABLED Enable OAuth proxy mode false
ENABLE_LOCAL_OAUTH Enable local browser login true
LOG_LEVEL Log level INFO
LOG_FORMAT json or console Console on a TTY; JSON otherwise

Development

Install Python 3.13, uv, and Make, then run:

git clone https://github.com/GitGuardian/ggmcp.git
cd ggmcp
uv sync --frozen --all-groups
make test
make lint
make typecheck
make format

Install the linting, commit-message, and secret-scanning hooks with uvx pre-commit install and uvx pre-commit install --hook-type pre-push.

Tools live in src/gg_api_core/tools/ and are registered with their required scopes in src/gg_mcp_server/register_tools.py. Cover new tools in tests/e2e/. See PUBLISHING.md for the release process.

About

GitGuardian MCP server for AI-assisted secrets remediation: SecOps run it at scale across the organization, developers fix incidents in their repo.

Topics

Resources

Stars

44 stars

Watchers

6 watching

Forks

Releases

Packages

Contributors

Languages