GitGuardian MCP Server Logo

GitGuardian MCP Server

Official

Enables AI agents to scan projects for leaked secrets and manage security incidents using GitGuardia...

28 views
0 installs
Updated Jan 19, 2026
Not audited
Enables AI agents to scan projects for leaked secrets and manage security incidents using GitGuardian's comprehensive API. It supports automated secret detection, honeytoken creation, and remediation workflows to secure codebases without context switching.
  1. Open the FastMCP connection interface

    • Click the "Install Now" button to open the FastMCP / MCP install dialog where you can enter environment variables. All ENV values described below should be added in that connection interface (the form fields provided by FastMCP).
  2. Default (recommended) — use the built‑in OAuth flow (no ENV required)

    • If you leave OAuth enabled (default), you do NOT need to pre-fill a token: after installation the MCP server will open a browser to authenticate you and will store the resulting token under ~/.gitguardian for future runs. (github.com)
  3. If you want a Personal Access Token (PAT) instead of OAuth — obtain a PAT and paste it

    • Log in to your GitGuardian Dashboard (your workspace).
    • Open the "API" area → "Personal access tokens" (or "Personal access tokens" under API) and click Create token. (docs.gitguardian.com)
    • Give the token a name, set an expiry (or never), select the scopes you need (e.g., scan, incidents:read, honeytokens:read/write depending on features you intend to use), then click Create.
    • Copy the token immediately (it is shown only once) and paste it into the FastMCP interface field named GITGUARDIAN_PERSONAL_ACCESS_TOKEN. (docs.gitguardian.com)
    • In the FastMCP env fields also set ENABLE_LOCAL_OAUTH to false (because you are supplying a PAT). (github.com)
  4. If you need HTTP/SSE (remote) transport — set MCP_PORT / MCP_HOST and disable local OAuth

    • In the FastMCP interface set ENABLE_LOCAL_OAUTH = false, MCP_PORT = <port you choose, e.g. 8000>, and MCP_HOST = <host, e.g. 127.0.0.1 or 0.0.0.0>. (github.com)
    • When using HTTP/SSE, the server requires per-request authentication (Authorization header). You can either:
      • Keep GITGUARDIAN_PERSONAL_ACCESS_TOKEN set in the FastMCP env (fallback), or
      • Supply Authorization: Bearer on each HTTP request to the MCP server. (github.com)
  5. If you use a self‑hosted GitGuardian instance — set the instance URL

  6. If you have a custom OAuth application — set GITGUARDIAN_CLIENT_ID

    • Only needed if your organization created a custom OAuth client for GitGuardian. Obtain the client ID from your GitGuardian admin or from the OAuth app registration area in your GitGuardian instance and paste it into GITGUARDIAN_CLIENT_ID in the FastMCP interface. If you don’t have a custom client, you can leave this unset (the MCP server defaults to the standard client). (github.com)
  7. Optional scope and token options (fill if required)

    • If you need extra OAuth scopes or want to control token lifetime, set GITGUARDIAN_SCOPES (comma-separated scopes) and/or GITGUARDIAN_TOKEN_LIFETIME (days) in the FastMCP env fields. Only set these if your deployment requires broader permissions or a non-default lifetime. (github.com)
  8. Secure handling and final steps

    • After pasting any token into the FastMCP interface, confirm the install. Store the token in a secrets manager if possible; PATs are shown once and cannot be recovered later — copy and keep them safely. (docs.gitguardian.com)
  9. Quick checklist to paste into the FastMCP form

    • For OAuth (default): no env required (install and authenticate via browser).
    • For PAT-based or non-interactive usage: ENABLE_LOCAL_OAUTH = false, GITGUARDIAN_PERSONAL_ACCESS_TOKEN = .
    • For HTTP/SSE transport: ENABLE_LOCAL_OAUTH = false, MCP_PORT = , MCP_HOST = , (optionally) GITGUARDIAN_PERSONAL_ACCESS_TOKEN.
    • For self-hosted: GITGUARDIAN_URL = .
    • For custom OAuth: GITGUARDIAN_CLIENT_ID = .
    • Paste each value into its matching FastMCP ENV field and complete the Install/Save action in the interface. (github.com)

Quick Start

View on GitHub

More for Security

View All →

More for Developer Tools

View All →

Similar MCP Servers

G

GitLab

GitLab MCP Server provides robust integration with the GitLab API, enabling developers to interact with repositories, issues, merge requests, and project events through natural language commands via stdio and Server-Sent Events (SSE) transports.

Developer Tools Project Management
312
0
GitHub

GitHub

Official Remote Remote

Extend your developer tools with the GitHub MCP Server—a powerful Model Context Protocol server enhancing automation and AI interactions with GitHub APIs. It supports diverse functionalities like managing workflows, issues, pull requests, repositories, and security alerts. Customize available toolsets to fit your needs, enable dynamic tool discovery to streamline tool usage, and run the server locally or remotely. With read-only mode and support for GitHub Enterprise, this server integrates deeply into your GitHub ecosystem, empowering data extraction and intelligent operations for developers and AI applications. Licensed under MIT, it fosters flexible and advanced GitHub automation.

Developer Tools Project Management

Report Issue

Thank you! Your issue report has been submitted successfully.