AWS Billing vs Apisix MCP
A side-by-side look at the AWS Billing 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 AWS Billing for cloud platforms work over a hosted endpoint; 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 AWS Billing when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
aws_billing_list_accounts, aws_billing_cost, aws_billing_forecast.
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 | 55/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | 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 | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 10 | 32 |
| Full listing | View AWS Billing | View Apisix MCP |
Tools & capabilities
AWS Billing tools 10
aws_billing_list_accountsList AWS Billing credential records linked to this install.aws_billing_costGet normalized AWS Cost Explorer cost and usage with daily breakdown and top services. The adapter drains NextPageToken internally.aws_billing_forecastGet normalized AWS Cost Explorer forecast for the next 30 days or an explicit date range.aws_billing_anomaliesGet normalized AWS Cost Anomaly Detection anomalies for a date range. The adapter drains NextPageToken internally.show_versionShow the current MCP platform and adapter versions.report_bugReport a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.connectReturns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
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.
AWS Billing
{
"mcpServers": {
"aws-billing": {
"url": "https://api.mcp.ai/p_aws_billing"
}
}
}
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
AWS Billing is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. Apisix MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick AWS Billing 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.
AWS Billing 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 aws-billing and api7-apisix-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AWS Billing has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Apisix MCP has 63/100 (Good) with 6 views, 0 installs and 38 GitHub stars.