Bring Api Security
to CrewAI
Create your Vinkius account to connect Salt Security to CrewAI and start using all 10 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Salt Security MCP Server?
Connect your AI directly with Salt Security to proactively defend your Application Programming Interface (API) environment. Improve API discovery, manage security posture, and remediate threats in real-time through simple conversational prompts.
What you can do
- API Inventory & Discovery — View all auto-discovered APIs in your environment, including unknown or shadow APIs (
get_inventory). Retrieve schema details, identify exposed sensitive data (PII), and analyze structural drifts (get_endpoint). - Threat Intelligence & Monitoring — Monitor active API attacks and business logic abuses as they happen (
get_attacks). Profile known threat actors to uncover behavioral patterns (get_attackers). - Active Remediation — Respond to incidents immediately by triggering blockade commands against attackers, seamlessly passing instructions to your integrated WAFs (
block_attacker). - Posture & Governance Assessment — Identify design flaws and vulnerabilities before they reach production (
get_posture_vulnerabilities). Manage OpenAPI (OAS) specifications (list_oas_specs,upload_oas_spec) and verify active governance rules (get_governance_policies).
How it works
- Enable the Salt Security integration in your workspace.
- Navigate to your Salt Security console.
- Go to the Settings or Administration section and generate a new API Token.
- Paste this token securely into the configuration fields provided below.
- Ask the AI: "Are there any known threat actors exploiting our APIs right now?"
Built-in capabilities (10)
Issues a command to block a specific attacker
Lists known threat actors profiled by Salt
Lists detected malicious API attacks
Retrieves details for a specific API endpoint
Lists active API governance rules
Retrieves the auto-discovered API inventory
Retrieves identified pre-production design flaws
Checks the health of traffic mirror ingestion
Lists all uploaded OpenAPI specifications
Uploads a new OAS/Swagger specification
Why CrewAI?
When paired with CrewAI, Salt Security becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Salt Security 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
Salt Security in CrewAI
Why run Salt Security with Vinkius?
The Salt Security connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 10 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.
* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.
Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Salt Security using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Salt Security and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Salt Security to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Salt Security for CrewAI
Every request between CrewAI and Salt Security is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
Can the AI forcefully block attackers or does it just view them?
You can explicitly instruct the AI to use the block_attacker tool, which triggers a remediation event across your security infrastructure (e.g., WAF integrations). It provides both visibility and direct active response.
Does Salt Security allow me to upload spec definitions (OAS) directly from my files via chat?
Yes, you can upload raw specification content using the upload_oas_spec tool for vulnerability testing and validation. Provide the exact OpenAPI content, and Salt will interpret it securely naturally properly successfully cleanly nicely properly natively completely optimally brightly cleanly beautifully actively quickly seamlessly efficiently correctly elegantly faithfully efficiently natively perfectly.
How frequently is the API inventory auto-discovered?
Salt maintains a continuous discovery architecture via passive traffic monitoring. This prevents any drift and immediately identifies 'Ghost APIs' when queried using the get_inventory capability.
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 →
ANVISA (Portal de APIs)
7 toolsAccess official Brazilian health regulatory data — query medicines, prices, food registrations, cosmetics, and sanitizers directly from ANVISA.
Webflow
10 toolsEquip your AI agent with direct access to Webflow — manage CMS collections, publish sites, and query site analytics without opening the Webflow designer.
Officevibe
10 toolsManage employee engagement via Officevibe — track pulse survey scores, feedback, and NPS directly from your AI agent.
Konfío
14 toolsAutomate your Konfío SMB banking and lending. Manage loans, pay invoices, track credit cards, and emit SAT-compliant CFDIs directly from any AI agent.