Skip to main content
All GitGuardian integration capabilities

​
About

This is an MCP connector that gives the Sazabi agent tools from GitGuardian’s hosted MCP server. You connect it with a GitGuardian personal access token, which Sazabi stores securely and sends as the Authorization: Bearer header. The agent sees only what the token’s owner can see in the GitGuardian dashboard, and Sazabi connects it read-only: tools that resolve, assign, or comment on incidents, change severity or tags, revoke secrets, or create honeytokens stay blocked, and so does the tool that scans pasted content. What the agent can do:
  • Look up the incidents, detectors, and occurrences for a secret named in a log or alert
  • Check an incident’s severity, status, assignees, comments, and activity history
  • List the sources (repositories) GitGuardian monitors and where a secret was found
  • Read the workspace remediation workflow to say what the next step is

​
Prerequisites

  • A GitGuardian workspace with permission to create a personal access token
  • Your GitGuardian region: United States (dashboard.gitguardian.com) or Europe (dashboard.eu1.gitguardian.com); you select it when connecting. A token only works in its own region.

​
Set up in the dashboard

Configure connectors in the dashboard under Settings > MCP connectors.
1

​
Create a personal access token

In GitGuardian, open API > Personal access tokens, click Create token, tick only the read scopes incidents:read, sources:read and members:read, and copy the token. GitGuardian shows it once.
2

​
Open the connector

Find GitGuardian in Settings > MCP connectors.
3

​
Connect

Select your region, paste the token, and connect. Sazabi stores the token securely and sends it as the Authorization header.

​
Set up with the CLI

You can also connect GitGuardian with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference). GitGuardian authenticates with a personal access token sent as an Authorization header:
For Europe workspaces, add --server-url https://mcp.eu1.gitguardian.com/mcp. Sazabi uses this connector read-only, so write tools stay blocked even without --read-only; pass --project-id <project> to target a specific project. Confirm the result with sazabi mcp-connectors list.

​
Verify

Open the connector’s connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm you selected the region your GitGuardian workspace runs in.

​
Troubleshooting

Connection fails with an authorization error — GitGuardian rejected the token. Check that you copied the whole token, that it has not expired, and that it was created in the same region you selected (a US token does not work against the EU server). A tool is missing from the list — GitGuardian hides every tool the token’s scopes do not allow. Create a token with the read scopes listed above. A tool returns a permission error — The token’s owner cannot see that data in the GitGuardian dashboard.

​
Further reading

Agent tools

How the agent uses connector tools.

MCP connectors

Browse the connector catalog.