Cloud Tools vs Apisix MCP
A side-by-side look at the Cloud Tools and Apisix MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cloud Tools 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?
Choose Cloud Tools when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_PROFILE, GOOGLE_APPLICATION_CREDENTIALS, CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID, OVH_APPLICATION_KEY, OVH_CONSUMER_KEY. - You want tools like
compare_costs, get_commitments, get_costs.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 61/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | API key required |
| Pricing | Free | Free |
| Required env vars | AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_PROFILEGOOGLE_APPLICATION_CREDENTIALSCLOUDFLARE_API_TOKENCLOUDFLARE_ACCOUNT_IDOVH_APPLICATION_KEYOVH_CONSUMER_KEY | APISIX_SERVER_HOSTAPISIX_SERVER_PORTAPISIX_ADMIN_API_PORTAPISIX_ADMIN_API_PREFIXAPISIX_ADMIN_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 38 |
| Directory activity | 3 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 7 | 32 |
| Full listing | View Cloud Tools | View Apisix MCP |
Tools & capabilities
Cloud Tools tools 7
compare_costsThis period against the same day window of the previous month, so a partial month does not read as a fall. AWS and GCP only. GCP needs credentials.gcp.billing_table.get_commitmentsCommitments you are paying for, and whether you are consuming them, over the last 30 days. AWS: Savings Plans utilisation, coverage of eligible spend, and the saving a further commitment would give. GCP: committed use discounts with their expiry. Not implemented for Cloudflare or OVH, which sell no commitments.get_costsCloud spend. AWS: by service over a date range, from Cost Explorer; pass group_by="data_transfer" for transfer cost by usage type. GCP: by service from the BigQuery billing export, which credentials.gcp.billing_table must name — without it you get budget amounts, not spend. Cloudflare: subscriptions and zone plan costs. OVH: the 6 most recent invoices.get_cross_cloud_summaryOne cost and waste report over every cloud you pass credentials for, with a grand total. Omit a cloud's credentials to skip it.get_inventoryWhat exists. GCP: GCE instances, disks, addresses, snapshots, forwarding rules, GKE clusters with node pools, Cloud SQL, Cloud Functions, Cloud Run, GCS buckets, Cloud NAT, Cloud IDS, Artifact Registry, VPN gateways, subnets, PSC endpoints and Cloud Logging ingestion, with a per-project summary. Cloudflare: zones with plan and price, DNS records split proxied against dns-only, certificates with hosts and expiry, and Workers with invocation counts. OVH: instances and active services with renewal dates and monthly cost. Not implemented for AWS.get_recommendationsThe cloud provider's own optimisation suggestions. GCP: the Recommender API across every zone and region — idle VMs, machine type rightsizing, idle disks and addresses, idle and oversized Cloud SQL. Not implemented for the others; AWS Compute Optimizer is read as part of get_waste instead.get_wasteWhat is wasted, with the monthly cost of each finding and the utilisation evidence behind it. AWS: idle and oversized EC2 and RDS measured from CloudWatch CPU series, stopped instances, orphaned volumes and snapshots, unused AMIs and Elastic IPs, idle load balancers and NAT gateways, DynamoDB and ElastiCache, and log groups with no retention. GCP: idle and oversized instances, orphaned disks, unattached addresses, snapshots over 90 days, idle Cloud SQL, GKE clusters with no nodes, Cloud Functions and Cloud Run with no invocations, buckets with no lifecycle rule. Not implemented for Cloudflare or OVH.
Apisix MCP tools 32
get_resourceGet resource details by ID or list all resourcesdelete_resourceDelete a resource by IDsend_request_to_gatewaySend a request or multiple requests to the APISIX gatewaycreate_routeCreate a routeupdate_routeUpdate specific attributes of an existing routecreate_serviceCreate a serviceupdate_serviceUpdate specific attributes of an existing servicecreate_upstreamCreate an upstream service with load balancing settingsupdate_upstreamUpdate specific attributes of an existing upstreamcreate_or_update_consumerCreate a consumer, if the consumer already exists, it will be updatedget_credentialGet all credentials or a specific credential for a consumercreate_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.
Cloud Tools
{
"mcpServers": {
"cloud-tools": {
"command": "npx",
"args": [
"-y",
"@munhq/cloud-tools"
],
"env": {
"AWS_ACCESS_KEY_ID": "YOUR_AWS_ACCESS_KEY_ID_HERE",
"AWS_SECRET_ACCESS_KEY": "YOUR_AWS_SECRET_ACCESS_KEY_HERE",
"AWS_PROFILE": "YOUR_AWS_PROFILE_HERE",
"GOOGLE_APPLICATION_CREDENTIALS": "YOUR_GOOGLE_APPLICATION_CREDENTIALS_HERE",
"CLOUDFLARE_API_TOKEN": "YOUR_CLOUDFLARE_API_TOKEN_HERE",
"CLOUDFLARE_ACCOUNT_ID": "YOUR_CLOUDFLARE_ACCOUNT_ID_HERE",
"OVH_APPLICATION_KEY": "YOUR_OVH_APPLICATION_KEY_HERE",
"OVH_CONSUMER_KEY": "YOUR_OVH_CONSUMER_KEY_HERE"
}
}
}
}
Apisix MCP
{
"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
Cloud Tools is categorized under Cloud Platforms and uses a local stdio subprocess. Apisix MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Cloud Tools 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.
Cloud Tools is listed as free. Auth: other. 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 cloud-tools and api7-apisix-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cloud Tools has a quality signal of 61/100 (Good) with 3 views, 0 installs and 0 GitHub stars. Apisix MCP has 63/100 (Good) with 6 views, 0 installs and 38 GitHub stars.