MCP Cloudflare vs Vozora
A side-by-side look at the MCP Cloudflare and Vozora MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
V
VozoraCloud Platforms · Remote HTTP/SSEManage Vozora VPS servers, SSH keys, firewalls, DNS and usage from an AI agent.37FairAuth: not declaredVerdict: choose MCP Cloudflare for cloud platforms work as a local process; choose Vozora for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Cloudflare when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CLOUDFLARE_API_TOKEN.
VChoose Vozora when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | V Vozora | |
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 39/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CLOUDFLARE_API_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Cloudflare | View Vozora |
Tools & capabilities
MCP Cloudflare tools
No tool names declared yet. Check the project README from the listing page.
Vozora tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Cloudflare
{
"mcpServers": {
"mcp-cloudflare": {
"command": "uvx",
"args": [
"mcp-cloudflare-crunchtools"
],
"env": {
"CLOUDFLARE_API_TOKEN": "YOUR_CLOUDFLARE_API_TOKEN_HERE"
}
}
}
}
Vozora
{
"mcpServers": {
"vozora": {
"url": "https://vozora.io/mcp"
}
}
}
Frequently asked questions
MCP Cloudflare is categorized under Cloud Platforms and uses a local stdio subprocess. Vozora belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick MCP Cloudflare for cloud platforms work and Vozora for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Cloudflare has no declared pricing — check the project's own site. Vozora has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-cloudflare and vozora as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Cloudflare has a quality signal of 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Vozora has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.