How to Use the GitGuardian MCP in Claude

Q: How do I install the GitGuardian MCP Server on Claude Desktop?

Open your claudedesktopconfig.json file and add the server configuration under the mcpServers key. Provide your GitGuardian API key as an environment variable, save the file, and restart Claude Desktop to load the 49 security tools.

Q: How does GitGuardian help Claude Desktop identify false positives?

Your agent uses getcustomtag and listcustomtags to filter out known safe patterns. You can also run updatecustomtagfull to flag specific mock keys used in testing so they don't trigger alerts during local code reviews.

Q: What happens if my Claude Desktop session runs out of GitGuardian API quota?

Ask your agent to run getquotas to check your remaining monthly scanning limits. If you hit your limit, the server will block new scanning requests until your billing cycle resets or you upgrade your plan.

Scan raw code and manage active security leaks directly from your Claude Desktop chat window.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect GitGuardian MCP to Claude Desktop

Create your Vinkius account to connect GitGuardian to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup GitGuardian with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Real-time credential scanning in Claude Desktop

Look, here's the thing: developers leak keys. It's a fact of life. Paste your code blocks directly into your Claude Desktop chat to check for exposed API keys before you commit. The MCP Server runs `scan_content` on your machine to flag high-entropy strings, stopping credentials from ever reaching your remote origin. If your workspace requires automated tracking, you can trigger `scan_and_create_incidents` to log findings instantly. This keeps your local development loop tight and keeps accidental leaks out of your git history.

Instant incident triage and resolution

When an alert triggers, your local Claude Desktop agent pulls the exact leak details using `get_secret_incident`. You don't need to open the GitGuardian dashboard to see which file exposed the token or who committed it. Fix the issue, rotate the leaked key, and tell your agent to run `resolve_secret_incident` to close the ticket. If it's a false positive in a test file, use `ignore_secret_incident` to clear the noise without leaving your chat window.

Deploying active deception traps

Stop playing catch-up with attackers and start seeding your environments with decoy credentials. Ask your Claude Desktop agent to connect to the MCP Server and run `create_honeytoken` to generate highly realistic, non-functional keys that alert you the second they are touched. You can organize these traps by running `create_honeytoken_note` to document where they live. If a decoy is compromised, your agent checks `list_honeytoken_events` to show you the attacker's IP and user agent immediately.

Setup guide

Set up GitGuardian MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The GitGuardian MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the GitGuardian MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under gitguardian-mcp.

json

{
  "mcpServers": {
    "gitguardian-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by GitGuardian. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect GitGuardian now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about GitGuardian MCP in Claude Desktop

Open your `claude_desktop_config.json` file and add the server configuration under the `mcpServers` key. Provide your GitGuardian API key as an environment variable, save the file, and restart Claude Desktop to load the 49 security tools.

Yes. Go to your Claude.ai settings, select Integrations, and add the remote URL for your hosted GitGuardian MCP instance. This lets you run tools like `list_secret_incidents` directly in your browser chat.

Your agent uses `get_custom_tag` and `list_custom_tags` to filter out known safe patterns. You can also run `update_custom_tag_full` to flag specific mock keys used in testing so they don't trigger alerts during local code reviews.

Ask your agent to run `get_quotas` to check your remaining monthly scanning limits. If you hit your limit, the server will block new scanning requests until your billing cycle resets or you upgrade your plan.

No. The GitGuardian MCP Server processes your code locally via `scan_content` and only sends metadata or incident IDs back to the GitGuardian API. Your raw credentials and source files never leave your local machine or your private Claude Desktop environment.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript