mcp-apisix
Related Servers
Alternatives to mcp-apisix
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to safely read, audit, and manage Clash Verge Rev / Mihomo configuration with read-only and controlled runtime operations.666MIT
- FlicenseNot gradedqualityCmaintenanceEnables natural-language Chinese queries across MySQL, Dameng DM, and KingbaseES databases, with safe SQL generation, schema exploration, and read-only query execution.-
- AlicenseNot gradedqualityAmaintenanceEnables LLMs to manage Apifox API projects, including listing, creating, updating, and deleting API endpoints and schemas via natural language.30MIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible AI clients to query, search, create, and update YApi API definitions and categories using natural language, with write operations excluding deletion for safety.98ISC
- AlicenseBqualityDmaintenanceEnables large language models to query and operate on Apollo Configuration Center. Supports managing apps, clusters, namespaces, config items, and releases.173MIT
- AlicenseDqualityBmaintenanceEnables managing MikroTik RouterOS devices via natural language, with read-heavy network inspection and guarded write access across multiple routers.261Apache 2.0
TDQS
Scored across 15 tools
Each tool targets a distinct resource type (route, service, upstream, consumer, etc.) and a distinct action (get, list, validate). Even similar list tools like apisix_list_routes and apisix_list_stream_routes are clearly differentiated by resource type and descriptions.
All tools follow the consistent pattern apisix_<verb>_<resource>, with verbs limited to get, list, and validate. Naming is uniform snake_case with no mixed conventions, making the toolset highly predictable.
With 15 tools, the server sits at the top of the ideal 3-15 range. Each tool corresponds to a meaningful APISIX resource or capability, and none feel redundant or out of scope, so the count is well-calibrated.
The toolset offers comprehensive read coverage for all major APISIX resources plus schema validation, and intentional omissions are documented. However, there are no create, update, or delete operations, which is a notable gap if full lifecycle management is expected, though consistent with the apparent read-only intent.