Bring Secret Detection
to CrewAI
Learn how to connect GitGuardian to CrewAI and start using 49 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the GitGuardian MCP Server?
Connect your GitGuardian workspace to any AI agent to strengthen your security posture and manage secret leaks through natural conversation.
What you can do
- Incident Management — List, retrieve, and resolve secret incidents. Assign team members to leaks and track remediation progress.
- Honeytokens — Create and manage decoy credentials (honeytokens) to detect unauthorized access to your private infrastructure.
- Security Scanning — Scan code snippets or content for secrets and sensitive data in real-time to prevent leaks before they happen.
- Audit & Compliance — Access detailed audit logs to monitor workspace activity and ensure compliance with security policies.
- Team Collaboration — Manage teams, members, and API tokens to orchestrate security operations across your organization.
How it works
- Subscribe to this server
- Enter your GitGuardian API Key
- Start monitoring and securing your code from Claude, Cursor, or any MCP-compatible client
Your AI acts as a 24/7 Security Operations Center (SOC) assistant, helping you triage alerts and deploy defenses without leaving your workflow.
Who is this for?
- Security Engineers — quickly triage secret incidents and manage honeytoken deployments across multiple environments.
- DevOps & SREs — automate security audits and monitor workspace health checks directly from the terminal or IDE.
- Developers — scan code for secrets before committing and check incident statuses without switching to the GitGuardian dashboard.
Built-in capabilities (49)
Assign a secret incident
Bulk lookup for honeytoken HMSL hashes
Create a custom tag
Create a honeytoken
Create a honeytoken note
Create a honeytoken within a context
Create a team
Delete a custom tag
Delete a custom tags key
Retrieve a custom tag
Check API health status
Retrieve a honeytoken
Retrieve quota overview
Retrieve secret incident details
Retrieve current API token details
Ignore a secret incident
List API tokens
List all existing event names for audit logs
List audit logs for your workspace
List custom tags
List health check history for an instance
List health checks
List all honeytokens events
List honeytoken notes
List sources where a honeytoken appears
List honeytokens
List IP allowlist rules
List GitGuardian's own IP addresses
List workspace members
List groups via SCIM
List members via SCIM
List secret incidents
List all sources
List team members
List teams
Scan multiple contents for secrets
Reset a honeytoken
Resolve a secret incident
Revoke a honeytoken
Revoke current API token
Scan content and create incidents automatically
Scan content for secrets
Trigger a health check
Trigger scans on sources
Full update of a custom tag
Partial update of a custom tag
Update a custom tags key
Update a honeytoken
Update a secret incident
Why CrewAI?
When paired with CrewAI, GitGuardian becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call GitGuardian tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
GitGuardian in CrewAI
GitGuardian and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect GitGuardian to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for GitGuardian in CrewAI
The GitGuardian MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 49 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
GitGuardian for CrewAI
Every tool call from CrewAI to the GitGuardian MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I resolve a secret incident directly through the AI?
Yes. You can use the resolve_secret_incident tool by providing the incident ID. You can also use assign_secret_incident to delegate the fix to a specific team member.
How do I create a decoy credential to catch attackers?
Use the create_honeytoken tool. You can specify the type and name of the honeytoken, and GitGuardian will generate a decoy that alerts you if it's ever used.
Is it possible to scan a text block for secrets before I commit it?
Absolutely. Use the scan_content tool. Provide the document content and a filename, and the AI will return any detected secrets or policy violations found by GitGuardian's engine.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Modal (Serverless AI Infrastructure)
7 toolsManage serverless compute via Modal — audit active apps, track GPU deployments, and monitor network volumes.
api.video
9 toolsHost, encode, and stream video content with a developer-first API that handles everything from upload to playback.
Google Calendar
12 toolsSync and orchestrate your agenda securely — scan, schedule, and manipulate Google Calendar events natively in chat.
Odoo Manufacturing
7 toolsCreate manufacturing orders, manage BOMs, work orders, and work centers — Odoo MRP through natural conversation.