Compatible with every major AI agent and IDE
What is the CrowdSec MCP Server?
Connect your CrowdSec security engine to any AI agent to take full control of your threat intelligence and network defense through natural conversation.
What you can do
- Local Decisions — Query your Local API (LAPI) for active blocks or decisions on specific IPs, ranges, or scopes to understand current local threats.
- Decision Streaming — Poll for real-time updates on new and deleted decisions from your local database to keep your security context synchronized.
- Global CTI Reputation — Fetch global IP reputation data, behaviors, and classifications from the CrowdSec Community Threat Intelligence (CTI) network.
- Security Auditing — Inspect metadata and classifications for suspicious actors directly from your command interface or code editor.
How it works
- Subscribe to this server
- Enter your CrowdSec LAPI URL, LAPI Key, and CTI Key
- Start managing your security posture from Claude, Cursor, or any MCP-compatible client
No more manual log diving or complex CLI commands to check if an IP is malicious. Your AI acts as a dedicated security analyst.
Who is this for?
- Security Engineers — instantly retrieve local decision statuses and global reputation metrics without leaving the terminal
- DevOps Teams — monitor security streams and verify IP behaviors during incident response directly from the IDE
- System Administrators — automate the auditing of blocked ranges and suspicious network activity through natural language
Built-in capabilities (3)
Get CTI reputation for an IP
Query CrowdSec LAPI for decisions
Poll for new and deleted decisions from LAPI
Why Cursor?
Cursor's Agent mode turns CrowdSec into an in-editor superpower. Ask Cursor to generate code using live data from CrowdSec and it fetches, processes, and writes. all in a single agentic loop. 3 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
CrowdSec in Cursor
CrowdSec and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect CrowdSec to Cursor 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 CrowdSec in Cursor
The CrowdSec 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 3 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor 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
CrowdSec for Cursor
Every tool call from Cursor to the CrowdSec MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check if a specific IP address is currently blocked in my local CrowdSec instance?
Yes! Use the get_decisions tool providing the IP address. Your agent will query your Local API and return any active decisions, including the reason and duration of the block.
How do I see the latest security threats detected by my server in real-time?
You can use the get_decisions_stream tool. This allows your agent to poll for new and deleted decisions, giving you a clear view of recent security activity on your infrastructure.
Can I verify an IP's global reputation even if it hasn't attacked my server yet?
Absolutely. The get_cti_smoke tool queries the global CrowdSec CTI network. It provides background information, attack behaviors, and risk scores for any IP based on community data.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Lightcast Labor Market
10 toolsEquip your AI agent to access labor market data, track skill taxonomies, and monitor job titles via the Lightcast API.

Testim
10 toolsTrigger automated AI tests, inspect execution logs, and manage branches natively via your AI agent.

John Deere
7 toolsMonitor farm operations via John Deere APIs — track machines, map fields, review planting and harvest data from any AI agent.

Gamma (AI Presentations)
5 toolsGenerate AI-powered presentations, documents, and webpages. List, update, and manage your Gamma workspace directly from any AI agent.
