Hetzner vs Apisix MCP

A side-by-side look at the Hetzner and Apisix MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Hetzner logoHetznerCloud Platforms · Local subprocess (stdio)MCP server for the Hetzner Cloud API — servers, networks, volumes, firewalls, and more.59GoodAuth: not declaredApisix MCP logoApisix MCPCloud Platforms · Local subprocess (stdio)MCP Server that support for querying and managing all resource in Apache APISIX.63GoodAuth: api key required

Verdict: choose Hetzner for cloud platforms work as a local process; choose Apisix MCP for cloud platforms as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Hetzner logoChoose Hetzner when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: HETZNER_API_TOKEN, HETZNER_STORAGE_API_TOKEN.
  • You want tools like hetzner_list_servers, hetzner_get_server, hetzner_create_server.
Explore Hetzner

Apisix MCP logoChoose Apisix MCP when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: APISIX_SERVER_HOST, APISIX_SERVER_PORT, APISIX_ADMIN_API_PORT, APISIX_ADMIN_API_PREFIX, APISIX_ADMIN_KEY.
  • You want tools like get_resource, delete_resource, send_request_to_gateway.
Explore Apisix MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecHetzner logoHetznerApisix MCP logoApisix MCP
CategoryCloud PlatformsCloud Platforms
Quality signal59/100 · Good63/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsHETZNER_API_TOKENHETZNER_STORAGE_API_TOKENAPISIX_SERVER_HOSTAPISIX_SERVER_PORTAPISIX_ADMIN_API_PORTAPISIX_ADMIN_API_PREFIXAPISIX_ADMIN_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars538
Directory activity 0 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
Tools8032

Tools & capabilities

Hetzner tools 80

  • hetzner_list_servers
  • hetzner_get_server
  • hetzner_create_server
  • hetzner_update_server
  • hetzner_delete_server
  • hetzner_power_on
  • hetzner_power_off
  • hetzner_reboot
  • hetzner_reset
  • hetzner_shutdown
  • hetzner_rebuild_server
  • hetzner_resize_server
  • +68 more on the listing page

Apisix MCP tools 32

  • get_resourceGet resource details by ID or list all resources
  • delete_resourceDelete a resource by ID
  • send_request_to_gatewaySend a request or multiple requests to the APISIX gateway
  • create_routeCreate a route
  • update_routeUpdate specific attributes of an existing route
  • create_serviceCreate a service
  • update_serviceUpdate specific attributes of an existing service
  • create_upstreamCreate an upstream service with load balancing settings
  • update_upstreamUpdate specific attributes of an existing upstream
  • create_or_update_consumerCreate a consumer, if the consumer already exists, it will be updated
  • get_credentialGet all credentials or a specific credential for a consumer
  • create_or_update_credentialCreate or update a credential for a consumer
  • +20 more on 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.

Hetzner

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "hetzner": {
      "command": "npx",
      "args": [
        "-y",
        "@lazyants/hetzner-mcp-server"
      ],
      "env": {
        "HETZNER_API_TOKEN": "YOUR_HETZNER_API_TOKEN_HERE",
        "HETZNER_STORAGE_API_TOKEN": "YOUR_HETZNER_STORAGE_API_TOKEN_HERE"
      }
    }
  }
}

Apisix MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "api7-apisix-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "apisix-mcp"
      ],
      "env": {
        "APISIX_SERVER_HOST": "YOUR_APISIX_SERVER_HOST_HERE",
        "APISIX_SERVER_PORT": "YOUR_APISIX_SERVER_PORT_HERE",
        "APISIX_ADMIN_API_PORT": "YOUR_APISIX_ADMIN_API_PORT_HERE",
        "APISIX_ADMIN_API_PREFIX": "YOUR_APISIX_ADMIN_API_PREFIX_HERE",
        "APISIX_ADMIN_KEY": "YOUR_APISIX_ADMIN_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Hetzner is categorized under Cloud Platforms and uses a local stdio subprocess. Apisix MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Hetzner for cloud platforms work and Apisix MCP 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.

Hetzner has no declared pricing — check the project's own site. Apisix MCP is listed as free. Auth: api key required. 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 hetzner and api7-apisix-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Hetzner has a quality signal of 59/100 (Good) with 0 views, 0 installs and 5 GitHub stars. Apisix MCP has 63/100 (Good) with 6 views, 0 installs and 38 GitHub stars.