Model Context Protocol moderate risk

Apisix

APISIX MCP server bridges LLMs with APISIX Admin API, enabling natural language interaction for managing APISIX resources, but requires careful configuration.

Connections & Capabilities

Connects To

GitHub

Capabilities

readwriteadmin

Quickstart

Install

npx -y @smithery/cli install @api7/apisix-mcp --client claude

Config

{
  "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"
      }
    }
  }
}

Exposed MCP Tools (6)

safe

get_resource

Retrieves resources from APISIX based on the specified type.

Read-only operation; does not modify any resources.

critical

delete_resource

Removes a resource from APISIX based on its ID.

Destructive operation; can permanently remove resources.

moderate

create_route

Creates a new route in APISIX.

Adds a new route, potentially affecting traffic routing.

high

update_plugin_config

Modifies the configuration of a plugin.

Changes plugin behavior, which can have significant impact.

critical

get_secret_by_id

Retrieves a secret from APISIX by its ID.

Exposes sensitive information; can lead to credential compromise.

moderate

create_or_update_consumer

Creates or updates a consumer in APISIX.

Modifies consumer configurations, affecting access control.

Safety Assessment

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.

Access is controlled via API key.
Operations are categorized, allowing for granular control.
Supports management of secrets, consumers, and credentials.

Direct access to APISIX Admin API, which can be destructive.
No built-in sandboxing; relies on correct configuration.
Improper configuration of environment variables can lead to security breaches.
Potential for unauthorized resource manipulation if API key is compromised.