Loading...

APISIX MCP server bridges LLMs with APISIX Admin API, enabling natural language interaction for managing APISIX resources, but requires careful configuration.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
APISIX MCP server bridges LLMs with APISIX Admin API, enabling natural language interaction for managing APISIX resources, but requires careful configuration.
The APISIX MCP server provides a convenient way to manage APISIX resources through natural language. However, it requires careful configuration and monitoring to prevent unauthorized access and destructive operations. It is safe when used with strong API key management and limited user permissions; it is risky when exposed to untrusted users or when the API key is compromised.
Performance is limited by the APISIX Admin API's performance and the network latency between the AI client and the APISIX server. Consider optimizing API calls and caching frequently accessed data.
Cost depends on the number of API calls made to the APISIX Admin API and the resources consumed by the AI client. Monitor API usage to avoid unexpected costs.
npx -y @smithery/cli install @api7/apisix-mcp --client claude{
"mcpServers": {
"apisix-mcp": {
"command": "npx",
"args": [
"-y",
"apisix-mcp"
],
"env": {
"APISIX_SERVER_HOST": "your-apisix-server-host",
"APISIX_SERVER_PORT": "your-apisix-server-port",
"APISIX_ADMIN_API_PORT": "your-apisix-admin-api-port",
"APISIX_ADMIN_API_PREFIX": "your-apisix-admin-api-prefix",
"APISIX_ADMIN_KEY": "your-apisix-api-key"
}
}
}
}APISIX_SERVER_PORTAPISIX_ADMIN_API_PORTAPISIX_ADMIN_KEYget_resourceRetrieves resources from APISIX based on the specified type.
Read-only operation; does not modify any resources.
delete_resourceRemoves a resource from APISIX based on its ID.
Destructive operation; can permanently remove resources.
create_routeCreates a new route in APISIX.
Adds a new route, potentially affecting traffic routing.
update_plugin_configModifies the configuration of a plugin.
Changes plugin behavior, which can have significant impact.
get_secret_by_idRetrieves a secret from APISIX by its ID.
Exposes sensitive information; can lead to credential compromise.
create_or_update_consumerCreates or updates a consumer in APISIX.
Modifies consumer configurations, affecting access control.
API Key
cloud
The APISIX MCP server provides a convenient way to manage APISIX resources through natural language. However, it requires careful configuration and monitoring to prevent unauthorized access and destructive operations. It is safe when used with strong API key management and limited user permissions; it is risky when exposed to untrusted users or when the API key is compromised.
Autonomy depends entirely on the configuration of the AI client and the permissions granted to the API key. Exercise caution when enabling autonomous operations.
Production Tip
Implement robust monitoring and alerting to detect and respond to any unexpected changes made by the AI client.
It's a bridge between LLMs and the APISIX Admin API, enabling natural language management of APISIX resources.
You can install it via Smithery or manually using npm or source code, as described in the README.
You need to configure APISIX_SERVER_HOST, APISIX_SERVER_PORT, APISIX_ADMIN_API_PORT, APISIX_ADMIN_API_PREFIX, and APISIX_ADMIN_KEY.
It depends on your configuration. Secure your API key and limit user permissions to minimize risk.
Yes, but exercise caution and monitor changes closely to prevent unintended consequences.
It relies on the APISIX Admin API and the AI client's capabilities. It also lacks built-in sandboxing and rollback support.
Monitor the AI client's logs and the APISIX Admin API's activity to track changes made by the MCP server.