GitGuardian MCP server

What the model can do

GitGuardian secrets detection: secret incidents with detector, severity, validity, status, assignee and where they were found, the notes on an incident, monitored sources (repositories) with their health and open incidents, and workspace members. Can resolve, ignore, reopen, assign or unassign an incident, change its severity, re-check whether its secret is still present, add, edit or delete its notes, and scan named sources.

Reads

• gitguardian_list_incidentsGitGuardian secret incidents, newest detection first: detector (AWS key, Slack token…), severity, whether the secret is still valid, status…
• gitguardian_get_incidentOne GitGuardian secret incident with where it was found: each occurrence's source repository, file path, kind and whether still present.
• gitguardian_list_incident_notesNotes left on one GitGuardian secret incident, newest first, with the member id of who wrote each and when.
• gitguardian_list_sourcesSources GitGuardian monitors (repositories and other places code lives): name, type, visibility, criticality, health (safe, at_risk, unknown)…
• gitguardian_list_membersMembers of the GitGuardian workspace: name, email, access level (owner, manager, member, restricted) and whether active.

Acts, when you ask

These change something in GitGuardian. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• gitguardian_add_incident_noteAdds a note to a GitGuardian secret incident, written as the token's member.
• gitguardian_resolve_incidentResolve a GitGuardian secret incident, recording whether the leaked secret was revoked (secret_revoked must be stated, never assumed).
• gitguardian_ignore_incidentIgnore a GitGuardian secret incident with a reason (test_credential, false_positive, low_risk or invalid).
• gitguardian_reopen_incidentReopen a resolved or ignored GitGuardian secret incident, so it is open again for the workspace.
• gitguardian_assign_incidentAssign a GitGuardian secret incident to one workspace member, by email or member id (exactly one; find them with gitguardian_list_members).
• gitguardian_unassign_incidentRemove the assignee from a GitGuardian secret incident.
• gitguardian_set_incident_severityChange a GitGuardian secret incident's severity (critical, high, medium, low, info or unknown).
• gitguardian_check_incident_presenceAsk GitGuardian to re-check whether a secret incident's occurrences are still present in their sources.
• gitguardian_update_incident_noteReplace the text of a note on a GitGuardian secret incident.
• gitguardian_delete_incident_noteDelete a note from a GitGuardian secret incident permanently.
• gitguardian_scan_sourcesStart historical secret scans of named GitGuardian sources (ids from gitguardian_list_sources, at most 20).

Connect it

First connect GitGuardian on Dashboard → Connections, then add Memtro to your client once. The GitGuardian tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared GitGuardian connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which leaked secrets are still valid?
• › Which repositories are at risk?
• › Where was the latest AWS key incident found?
• › Which open incidents are assigned to Sarah?
• › Resolve the Slack token incident, the token was revoked this morning.

Questions

Is this an official GitGuardian MCP server?

No. It is Memtro's MCP server with Memtro's GitGuardian connector behind it: the connector reads GitGuardian through its API with the credentials you connect on Dashboard → Connections, and GitGuardian publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in GitGuardian?

Only when you ask, and only what it has been granted: add a note to a secret incident; resolve a secret incident (saying whether the secret was revoked), ignore it with a reason, or reopen it; assign a secret incident to a workspace member, or unassign it; change a secret incident's severity; re-check whether an incident's secret is still present in its sources; edit or delete a note this connection wrote on an incident; start historical scans of named sources. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server