Cloudpulse vs Apisix MCP
A side-by-side look at the Cloudpulse 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 Cloudpulse 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 Cloudpulse when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_PROFILE, AWS_REGION, VERCEL_TOKEN, VERCEL_TEAM_ID, GOOGLE_APPLICATION_CREDENTIALS, CLOUDFLARE_API_TOKEN. - You want tools like
list_cloud_topology, get_correlated_logs, diagnose_service_link.
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 | 49/100 · Fair | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_PROFILEAWS_REGIONVERCEL_TOKENVERCEL_TEAM_IDGOOGLE_APPLICATION_CREDENTIALSCLOUDFLARE_API_TOKEN | APISIX_SERVER_HOSTAPISIX_SERVER_PORTAPISIX_ADMIN_API_PORTAPISIX_ADMIN_API_PREFIXAPISIX_ADMIN_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 38 |
| Directory activity | 0 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 4 | 32 |
| Full listing | View Cloudpulse | View Apisix MCP |
Tools & capabilities
Cloudpulse tools 4
list_cloud_topologyScan all configured platforms and return a unified service map.get_correlated_logsFetch and merge logs from Vercel + AWS CloudWatch into one timeline.diagnose_service_linkCheck why service A can't reach resource B.check_resource_limitsQuery quotas and flag resources nearing their limits.
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.
Cloudpulse
{
"mcpServers": {
"cloudpulse": {
"command": "npx",
"args": [
"-y",
"cloudpulse-mcp"
],
"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",
"AWS_REGION": "YOUR_AWS_REGION_HERE",
"VERCEL_TOKEN": "YOUR_VERCEL_TOKEN_HERE",
"VERCEL_TEAM_ID": "YOUR_VERCEL_TEAM_ID_HERE",
"GOOGLE_APPLICATION_CREDENTIALS": "YOUR_GOOGLE_APPLICATION_CREDENTIALS_HERE",
"CLOUDFLARE_API_TOKEN": "YOUR_CLOUDFLARE_API_TOKEN_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
Cloudpulse is categorized under Cloud Platforms and uses a local stdio subprocess. Apisix MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Cloudpulse 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.
Cloudpulse 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 cloudpulse and api7-apisix-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cloudpulse has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Apisix MCP has 63/100 (Good) with 6 views, 0 installs and 38 GitHub stars.