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 VS Code Copilot?
GitHub Copilot Agent mode brings CrowdSec data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 3 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
CrowdSec in VS Code Copilot
CrowdSec and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect CrowdSec to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Buffer
10 toolsAutomate social media management via Buffer — schedule posts, track sent updates, shuffle queues, and manage multi-platform profiles with any AI agent.

Convex
4 toolsInteract with your Convex backend directly—execute queries, mutations, and actions from any AI agent.

Open-Meteo
5 toolsGet weather forecasts, historical data and air quality — no API key required, open-source weather data.

TaxJar
10 toolsConnect your AI to TaxJar. Calculate sales tax dynamically, validate active nexus regions, and assess order tax liability natively from the terminal.
