Apisix MCP vs Shipstatic MCP

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

Apisix MCP logoApisix MCPCloud Platforms · Local subprocess (stdio)MCP Server that support for querying and managing all resource in Apache APISIX.63GoodAuth: api key requiredShipstatic MCP logoShipstatic MCPCloud Platforms · Local subprocess (stdio)Deploy and manage static sites from AI agents. A simpler alternative to Vercel and Netlify for static website hosting — upload files, get a URL, and connect custom domains.67GreatAuth: no auth required

Verdict: choose Apisix MCP for cloud platforms work as a local process; choose Shipstatic 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?

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

Shipstatic MCP logoChoose Shipstatic MCP when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: SHIP_TOKEN.
  • You want tools like deployments_upload, deployments_list, deployments_get.
Explore Shipstatic MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecApisix MCP logoApisix MCPShipstatic MCP logoShipstatic MCP
CategoryCloud PlatformsCloud Platforms
Quality signal63/100 · Good67/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNo auth required
PricingFreeFree
Required env varsAPISIX_SERVER_HOSTAPISIX_SERVER_PORTAPISIX_ADMIN_API_PORTAPISIX_ADMIN_API_PREFIXAPISIX_ADMIN_KEYSHIP_TOKEN
Verified ownerCommunity listingCommunity listing
GitHub stars386
Directory activity 6 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools3215

Tools & capabilities

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

Shipstatic MCP tools 15

  • deployments_uploadDeploy a static site instantly: free, no account or API key required. Returns the live URL, file count, and size. Without SHIP_TOKEN, the response also includes a one-time claim URL, and the site expires in 3 days unless claimed. Pass `password` to make the site private.
  • deployments_listList all deployments with their URLs, status, labels, and password protection state. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next.
  • deployments_getGet deployment details including URL, status, file count, size, labels, and password protection state.
  • deployments_setUpdate deployment labels. Replaces all existing labels.
  • deployments_deletePermanently deletes a deployment and its files.
  • domains_setCreate or update a custom domain. Can reserve a name (omit deployment), link it to a deployment, switch deployments, or update labels. domains_records then returns the DNS records to configure.
  • domains_listList all domains with their URLs, linked deployment, and `status`. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next.
  • domains_getGet domain details including URL, linked deployment, labels, and `status`: the one word saying what the domain needs from its owner (`unverified`, `unlinked`, `live`, `paused`).
  • domains_recordsReturns the DNS records to configure at the domain's DNS provider. Call after domains_set. Custom domains only: a ShipStatic domain has no records to configure.
  • domains_dnsReturns the DNS provider recorded for the domain, if known (e.g. Cloudflare, Namecheap): where its DNS records are configured. Custom domains only, and only while the domain is unverified; once its DNS is right there is nothing left to locate.
  • domains_shareReturns a shareable DNS setup URL that needs no API key, for whoever manages the domain's DNS. Custom domains only, and only while the domain is unverified; a verified domain has no setup left to share.
  • domains_validateCheck if a domain name is valid and available before creating it. Returns the normalized form and availability.
  • +3 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.

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"
      }
    }
  }
}

Shipstatic MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "shipstatic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@shipstatic/mcp"
      ],
      "env": {
        "SHIP_TOKEN": "YOUR_SHIP_TOKEN_HERE"
      }
    }
  }
}

Frequently asked questions

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

Apisix MCP is listed as free. Auth: api key required. Shipstatic MCP is listed as free. Auth: no auth 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 api7-apisix-mcp and shipstatic-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Apisix MCP has a quality signal of 63/100 (Good) with 6 views, 0 installs and 38 GitHub stars. Shipstatic MCP has 67/100 (Great) with 4 views, 0 installs and 6 GitHub stars.