4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Cloudflare Tunnel MCP Server

Bring Cloudflare Tunnel
to CrewAI

Learn how to connect Cloudflare Tunnel to CrewAI and start using 17 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Cleanup ConnectionsCreate RouteCreate TunnelDelete RouteDelete TunnelGet ConfigurationGet ConnectorGet Management TokenGet Route By IpGet TunnelGet Tunnel TokenList ConnectionsList RoutesList TunnelsPut ConfigurationUpdate RouteUpdate Tunnel

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Cloudflare Tunnel

What is the Cloudflare Tunnel MCP Server?

Connect your Cloudflare account to any AI agent to take full control of your Zero Trust connectivity and private network routing through natural conversation.

What you can do

  • Tunnel Management — List all tunnels in your account, filter by status (healthy, degraded, down), and fetch detailed metadata for specific tunnels.
  • Remote Configuration — Retrieve and update ingress rules and origin settings for remotely-managed tunnels without touching the CLI.
  • Network Routing — Manage private network routes (CIDR) and IP-based routing to connect your internal resources securely.
  • Connection Monitoring — Inspect active connectors, list tunnel connections, and clean up stale sessions to ensure high availability.
  • Lifecycle Actions — Create new tunnels, update secrets, or delete decommissioned tunnels directly from your workspace.

How it works

  1. Subscribe to this server
  2. Enter your Cloudflare API Token (with Cloudflare Tunnel permissions)
  3. Start managing your secure tunnels from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • DevOps Engineers — quickly check tunnel health and update ingress rules during deployments without leaving the terminal or IDE.
  • Security Teams — audit active tunnels and network routes to ensure compliance with Zero Trust policies.
  • System Administrators — automate the cleanup of stale connections and monitor the status of remote connectors across multiple accounts.

Built-in capabilities (17)

cleanup_connections

If no client_id is provided, all connectors are removed. Clean up Cloudflare Tunnel connections

create_route

Create a tunnel route

create_tunnel

Create a new Cloudflare Tunnel

delete_route

Delete a tunnel route

delete_tunnel

Delete a Cloudflare Tunnel

get_configuration

Get configuration for a remotely-managed tunnel

get_connector

Get Cloudflare Tunnel connector details

get_management_token

Get a Cloudflare Tunnel management token

get_route_by_ip

Get tunnel route by IP

get_tunnel

Get details for a single Cloudflare Tunnel

get_tunnel_token

Get a Cloudflare Tunnel token

list_connections

List Cloudflare Tunnel connections

list_routes

List tunnel routes

list_tunnels

List and filter Cloudflare Tunnels in an account

put_configuration

Add or update configuration for a remotely-managed tunnel

update_route

Update a tunnel route

update_tunnel

Update an existing Cloudflare Tunnel

Why CrewAI?

When paired with CrewAI, Cloudflare Tunnel becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Cloudflare Tunnel 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 mcps parameter 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

See it in action

Cloudflare Tunnel in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Cloudflare Tunnel and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Cloudflare Tunnel 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Cloudflare Tunnel in CrewAI

The Cloudflare Tunnel 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 17 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.

Cloudflare Tunnel
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

The Vinkius Advantage

How Vinkius secures Cloudflare Tunnel for CrewAI

Every tool call from CrewAI to the Cloudflare Tunnel MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I update the ingress rules for a remotely managed tunnel?

Yes. Use the put_configuration tool to update the ingress rules and origin request settings for any tunnel that is configured for remote management.

02

How do I check if my tunnels are currently online?

You can use list_tunnels with the status parameter set to 'healthy' to see active tunnels, or use get_tunnel with a specific ID to see its current operational state.

03

Can I manage private network routes through this integration?

Yes. The server includes tools like list_routes, create_route, and delete_route to manage your Cloudflare Tunnel network routing (WARP-to-Tunnel).

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

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 →