A side-by-side look at the Porkbun (official) and Vozora MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Porkbun (official) 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 Porkbun (official) when
You need dedicated capabilities in the Cloud Platforms domain.
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.
Porkbun (official) is categorized under Cloud Platforms and uses a local stdio subprocess. Vozora belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Porkbun (official) 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.
Porkbun (official) 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 porkbun-official and vozora as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Porkbun (official) has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 32 GitHub stars. Vozora has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.