Apisix MCP vs MCP Redis Cloud
A side-by-side look at the Apisix MCP and MCP Redis Cloud MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Apisix MCP for cloud platforms work as a local process; choose MCP Redis Cloud for cloud platforms. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose MCP Redis Cloud when
- You need dedicated capabilities in the Cloud Platforms domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
API_KEY, SECRET_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 63/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | APISIX_SERVER_HOSTAPISIX_SERVER_PORTAPISIX_ADMIN_API_PORTAPISIX_ADMIN_API_PREFIXAPISIX_ADMIN_KEY | API_KEYSECRET_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 38 | 43 |
| Directory activity | 5 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 32 | Not listed |
| Full listing | View Apisix MCP | View MCP Redis Cloud |
Tools & capabilities
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
MCP Redis Cloud tools
No tool names declared yet. Check the project README from 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": {
"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"
}
}
}
}
MCP Redis Cloud
No confirmed install command for MCP Redis Cloud yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Apisix MCP is categorized under Cloud Platforms and uses a local stdio subprocess. MCP Redis Cloud belongs to Cloud Platforms and uses an install path we have not confirmed yet. Pick Apisix MCP for cloud platforms work and MCP Redis Cloud 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. MCP Redis Cloud has no confirmed install command yet — follow its own setup instructions.
Apisix MCP is listed as free. Auth: api key required. MCP Redis Cloud is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 api7-apisix-mcp and redis-mcp-redis-cloud 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 5 views, 0 installs and 38 GitHub stars. MCP Redis Cloud has 39/100 (Fair) with 6 views, 0 installs and 43 GitHub stars.