How do I create a Cloudflare API Token?

Log in to the [**Cloudflare dashboard**](https://dash.cloudflare.com/profile/api-tokens), go to **My Profile** > **API Tokens** > **Create Token**. Use the 'Edit zone DNS' template or create a custom token with permissions for Zones, DNS, Workers, KV, Pages and Firewall as needed. Copy the token immediately — it won't be shown again.

Can I modify DNS records for multiple domains?

Yes! First use `list_zones` to find the zone ID for each domain. Then use `create_dns_record`, `update_dns_record` or `delete_dns_record` with the appropriate zone_id. You can manage DNS records across all zones your API token has access to.

Where do I find my Cloudflare Account ID?

Your Account ID appears in the Cloudflare dashboard URL after logging in (e.g. `dash.cloudflare.com//...`). You can also find it in Organization Settings. The Account ID is needed for Workers, KV namespaces and Pages project queries.

Cloudflare Alternative MCP Server for CrewAI 15 tools — connect in under 2 minutes

Name: Cloudflare Alternative
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 15 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Cloudflare Alternative Specialist",
    goal="Help users interact with Cloudflare Alternative effectively",
    backstory=(
        "You are an expert at leveraging Cloudflare Alternative 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 Cloudflare Alternative "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 15 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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 Cloudflare Alternative MCP Server

Connect your Cloudflare account to any AI agent and take full control of your DNS, edge computing, CDN and security infrastructure through natural conversation.

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

What you can do

DNS Management — List, create, update and delete DNS records (A, AAAA, CNAME, MX, TXT) with full control over TTL, priority and Cloudflare proxy status
Zone Discovery — View all domains managed by Cloudflare with their plan type, SSL status, name server assignment and activation state
Workers Inventory — List all deployed serverless Worker scripts with their last deployment timestamps and binding configurations
KV Storage — Browse KV namespaces, read and write key-value pairs for Worker configuration, feature flags and edge-cached data
Pages Projects — View all Cloudflare Pages deployments with their Git source, production branch and build status
Firewall Audit — Review all WAF (Web Application Firewall) rules including filter expressions, actions (block, challenge, allow) and enabled status
Load Balancer Health — Inspect load balancer configurations, origin pools, health check status and traffic steering policies
CDN Analytics — View traffic analytics including request counts, bandwidth, threat mitigation, cache ratio and visitor statistics
IP Range Lookup — Retrieve Cloudflare's complete IP address ranges for origin firewall allow-listing

The Cloudflare Alternative MCP Server exposes 15 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 Cloudflare Alternative to CrewAI via MCP

Follow these steps to integrate the Cloudflare Alternative MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py — CrewAI auto-discovers 15 tools from Cloudflare Alternative

Why Use CrewAI with the Cloudflare Alternative MCP Server

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

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 the 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

Cloudflare Alternative + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Cloudflare Alternative MCP Server delivers measurable value.

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

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

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

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

Cloudflare Alternative MCP Tools for CrewAI (15)

These 15 tools become available when you connect Cloudflare Alternative to CrewAI via MCP:

create_dns_record

Requires the record type (A, AAAA, CNAME, MX, TXT, etc.), name (hostname) and content (IP address, target hostname, etc.). Optionally set TTL and whether to proxy through Cloudflare CDN (proxied=true enables the orange cloud). Create a new DNS record in a Cloudflare zone

delete_dns_record

Provide the zone ID and DNS record ID. This action cannot be undone — the record will be immediately removed from Cloudflare nameservers. Delete a DNS record from a Cloudflare zone

get_kv_value

Useful for reading Worker configuration, feature flags, cached API responses or session data. Provide the namespace ID and the key name. Get a value from a Cloudflare KV namespace

get_zone

Provide the zone ID. Get details for a specific Cloudflare zone

get_zone_analytics

Use to audit CDN performance, identify traffic spikes and review threat mitigation. Get analytics data for a Cloudflare zone

list_cloudflare_ips

Useful for configuring allow-lists, firewall rules and origin server access control to only permit traffic from Cloudflare proxies. List Cloudflare IP address ranges

list_dns_records

) configured for a specific zone. Each record has a type, name, content, TTL and proxied status (whether traffic goes through Cloudflare CDN). Optionally filter by record type (e.g. "A" for IPv4 addresses only). List DNS records for a Cloudflare zone

list_firewall_rules

Each rule defines a filter expression (e.g. "ip.src in {1.2.3.4}") and an action (block, challenge, allow, log, js_challenge). Use to audit your web application firewall configuration. List firewall rules for a Cloudflare zone

list_kv_namespaces

KV namespaces are used by Workers for edge-cached data, configuration and session storage. Each namespace has an ID and title. Use the namespace ID to read/write key-value pairs. List Cloudflare KV namespaces

list_load_balancers

Cloudflare Load Balancing distributes traffic across multiple origin servers or regions based on health checks, geolocation and steering policies. Each load balancer has a name, target pools, fallback pool and health status. List load balancers for a Cloudflare zone

list_pages_projects

Cloudflare Pages is a full-stack hosting platform that connects to Git repositories and deploys static/SSG sites. Each project has a name, Git source, production branch and deployment count. List Cloudflare Pages projects

list_workers

Workers are serverless JavaScript/Wasm functions that run at Cloudflare edge locations. Each worker has a name, last deployment timestamp, resource usage and optional bindings (KV, R2, D1). Provide the account ID (found in Cloudflare dashboard URL). List Cloudflare Workers scripts

list_zones

Each zone represents a domain that uses Cloudflare DNS and CDN services, with status (active, pending), plan type and verification status. Use the zone ID for subsequent DNS, firewall and analytics queries. List all Cloudflare zones (domains)

put_kv_value

Workers use this for edge-cached data, feature flags and configuration. Provide the namespace ID, key name and the value to store. The value can be any text (JSON, plain text, etc.). Write a value to a Cloudflare KV namespace

update_dns_record

Provide the zone ID and record ID, then any fields to change: name, content, TTL or proxied status. Only the fields you provide will be updated. Update an existing DNS record

Example Prompts for Cloudflare Alternative in CrewAI

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

"Show me all A records for my example.com zone."

"What Workers are currently deployed on my account?"

"What firewall rules are active on my production zone?"

Troubleshooting Cloudflare Alternative MCP Server with CrewAI

Common issues when connecting Cloudflare Alternative to CrewAI through the Vinkius, and how to resolve them.

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

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Cloudflare Alternative + CrewAI FAQ

Common questions about integrating Cloudflare Alternative MCP Server with CrewAI.

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.