Ionoscloud MCP vs Vozora
A side-by-side look at the Ionoscloud MCP 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 Ionoscloud MCP for cloud platforms work over a hosted endpoint; 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 Ionoscloud MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
IONOS_TOKEN, IONOS_S3_ACCESS_KEY, IONOS_S3_SECRET_KEY, IONOS_MCP_TOOL_SCOPE. - You want tools like
eager, lazy, ionos_load_compute_tools.
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 | 55/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | IONOS_TOKENIONOS_S3_ACCESS_KEYIONOS_S3_SECRET_KEYIONOS_MCP_TOOL_SCOPE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 9 | — |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 11 | Not listed |
| Full listing | View Ionoscloud MCP | View Vozora |
Tools & capabilities
Ionoscloud MCP tools 11
eagerlazyionos_load_compute_toolsionos_load_objectstorage_toolsdynamicsearchionos_search_toolsionos_describe_toolsionos_call_tooldescribecall
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.
Ionoscloud MCP
{
"mcpServers": {
"ionos-cloud-ionoscloud-mcp": {
"url": "https://mcp.so/server/ionos-cloud-mcp-server/ionos-cloud"
}
}
}
Vozora
{
"mcpServers": {
"vozora": {
"url": "https://vozora.io/mcp"
}
}
}
Frequently asked questions
Ionoscloud MCP is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. Vozora belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Ionoscloud MCP 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.
Ionoscloud MCP is listed as free. Auth: api key required. 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 ionos-cloud-ionoscloud-mcp and vozora as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ionoscloud MCP has a quality signal of 55/100 (Good) with 3 views, 0 installs and 9 GitHub stars. Vozora has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.