2,500+ MCP servers ready to use
Vinkius

Aikido Security MCP Server for CrewAI 16 tools — connect in under 2 minutes

Built by Vinkius GDPR 16 Tools Framework

Connect your CrewAI agents to Aikido Security through Vinkius, pass the Edge URL in the `mcps` parameter and every Aikido Security tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Aikido Security Specialist",
    goal="Help users interact with Aikido Security effectively",
    backstory=(
        "You are an expert at leveraging Aikido Security tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Aikido Security "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 16 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Aikido Security
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Aikido Security MCP Server

Connect your Aikido Security account to any AI agent and take full control of your security posture monitoring through natural conversation.

When paired with CrewAI, Aikido Security becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Aikido Security tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

  • Open Issues — List all open security vulnerabilities (CVEs, leaked secrets, cloud misconfigs, SAST findings) ordered by priority
  • Repository Scanning — View all connected code repositories and their scanning status across GitHub, GitLab, Bitbucket
  • Cloud Asset Monitoring — List cloud infrastructure assets from AWS, GCP, and Azure being monitored for misconfigurations
  • Container Security — Monitor container images and registries for known vulnerabilities
  • Compliance Tracking — Get ISO 27001 and SOC2 compliance overviews for audit preparation
  • Export Issues — Bulk export all security findings for reporting and analysis
  • Webhook Management — List configured webhooks for Slack, Jira, and other integrations

The Aikido Security MCP Server exposes 16 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Aikido Security to CrewAI via MCP

Follow these steps to integrate the Aikido Security MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

03

Customize the agent

Adjust the role, goal, and backstory to fit your use case

04

Run the crew

Run python crew.py. CrewAI auto-discovers 16 tools from Aikido Security

Why Use CrewAI with the Aikido Security MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Aikido Security through the Model Context Protocol.

01

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

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

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

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Aikido Security + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Aikido Security MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Aikido Security for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Aikido Security, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Aikido Security tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Aikido Security against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Aikido Security MCP Tools for CrewAI (16)

These 16 tools become available when you connect Aikido Security to CrewAI via MCP:

01

export_all_issues

This provides a comprehensive snapshot of your organization's security posture. Use this for compliance reporting, audit preparation, or bulk analysis of vulnerabilities. Export all security issues from Aikido

02

get_iso_compliance

Shows which controls are passing, failing, or need attention. Use this for compliance monitoring, audit preparation, and security posture reporting. This endpoint is available on all paid Aikido plans. Get ISO 27001 compliance overview for your organization

03

get_issue_group

The issue group ID can be obtained from list_open_issues. Each issue group represents a category of related vulnerabilities (e.g., the same CVE across multiple repositories). Use this to deep-dive into a specific security finding before deciding on remediation steps. Get detailed information about a specific security issue group

04

get_soc2_compliance

Shows which trust service criteria are met and which need remediation. Use this for SOC2 audit preparation and compliance monitoring. This endpoint is available on all paid Aikido plans. Get SOC2 compliance overview for your organization

05

get_workspace

Use this to verify your workspace setup and check for any configuration errors. Get workspace information and configuration

06

list_apps

Shows which apps have active protection and their configuration status. Use this to verify your web applications are properly secured against common attacks (SQL injection, XSS, etc.). List all web applications protected by Aikido firewall

07

list_cloud_assets

You can paginate through results and optionally search by text or sort by name, asset type, region, etc. Use this to understand your cloud attack surface and identify misconfigurations or vulnerabilities. List cloud infrastructure assets monitored by Aikido

08

list_code_repositories

This includes repositories connected from GitHub, GitLab, Bitbucket, etc. Use this to discover which repositories are being monitored for vulnerabilities and security issues. List all active code repositories connected to Aikido

09

list_connected_clouds

Shows which cloud environments are being monitored for security misconfigurations and vulnerabilities. Use this to verify cloud integrations are properly configured. List all cloud accounts connected to Aikido

10

list_containers

This includes Docker images from registries like Docker Hub, ECR, GCR, etc. Use this to monitor container security and identify vulnerable base images or dependencies. List all container images and repositories scanned by Aikido

11

list_custom_rules

Custom rules allow you to define organization-specific security checks beyond the default scanner. Use this to audit your custom rule coverage and ensure your security policies are properly enforced. List all custom SAST scanning rules in Aikido

12

list_open_issues

Issues include vulnerabilities from code scanning, container scanning, cloud security, SAST, IaC, DAST, and more. You can optionally filter by issue type (open_source, leaked_secret, cloud, sast, iac, docker_container, etc.), by team ID, or by repository. Supports pagination with page and per_page parameters. Use this to get a comprehensive view of your organization's security posture and prioritize remediation efforts. List all open security issues (vulnerabilities) in your Aikido account

13

list_teams

Teams are used to organize repositories, assign issues, and manage security workflows. Use this to understand how your organization structures its security responsibilities. List all teams in your Aikido organization

14

list_users

Shows user roles, permissions, and access levels. Use this to audit user access and ensure proper security team membership. List all users in your Aikido organization

15

list_virtual_machines

Use this to understand your VM attack surface and identify security gaps. List all virtual machines monitored by Aikido

16

list_webhooks

Webhooks are used to send security event notifications to external systems (Slack, Jira, etc.). Use this to verify integrations are properly configured and troubleshoot notification delivery. List all configured webhooks in Aikido

Example Prompts for Aikido Security in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Aikido Security immediately.

01

"Show me all critical and high severity open security issues, grouped by type."

02

"What's our current ISO 27001 compliance status?"

03

"List all our connected cloud accounts and any misconfigurations found in the last 7 days."

Troubleshooting Aikido Security MCP Server with CrewAI

Common issues when connecting Aikido Security to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

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.

Aikido Security + CrewAI FAQ

Common questions about integrating Aikido Security MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect Aikido Security to CrewAI

Get your token, paste the configuration, and start using 16 tools in under 2 minutes. No API key management needed.