Kong Admin API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KONG_ADMIN_URL | No | Base URL of the Admin API | http://localhost:8001 |
| KONG_WORKSPACE | No | Default EE workspace to scope requests to | |
| KONG_ADMIN_TOKEN | No | Sent as the Kong-Admin-Token header (RBAC) | |
| KONG_TLS_INSECURE | No | true to skip TLS verification (self-signed certs) | false |
| KONG_ADMIN_HEADERS | No | Extra headers, e.g. X-Foo: bar or a JSON object |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kong_listA | List entities of a given type from the Kong Admin API (GET on a collection). Supports filtering by tags and offset pagination. Use fetch_all to automatically follow pagination and return every item. |
| kong_getA | Fetch a single entity by id or name (GET //). Many Kong entities accept either their UUID or their unique name/slug as the id. |
| kong_createA | Create a new entity (POST /). Pass the entity body as |
| kong_updateA | Partially update an entity (PATCH //). Only the fields supplied in |
| kong_upsertA | Create or replace an entity at a known id/name (PUT //). Creates it if absent, fully replaces it if present. |
| kong_deleteB | Delete an entity (DELETE //). Returns HTTP 204 on success. |
| kong_requestA | Make an arbitrary request to any Kong Admin API endpoint. Use this for anything the CRUD tools don't cover: nested relations, RBAC, keyring, schemas, /status, /config (DB-less), bulk operations, etc. Examples: GET /status, GET /schemas/plugins/rate-limiting, POST /config (declarative), GET /services//routes. |
| kong_node_infoA | Get general node information (GET /): version, configuration, hostname, plugins available on the server, and database mode. |
| kong_node_statusA | Get node health and metrics (GET /status): database reachability, connection counts, and memory usage. |
| kong_list_workspacesB | List all workspaces (Enterprise). Equivalent to GET /workspaces. |
| kong_plugin_schemaA | Fetch the configuration schema for a plugin (GET /schemas/plugins/). Use this before creating/updating a plugin to learn the valid |
| kong_get_configA | Show the current Kong Admin API connection settings (admin URL, default workspace, whether a token is set). The token value is masked. |
| kong_configureA | Override the Kong Admin API connection at runtime for this session: the admin URL, admin token (Kong-Admin-Token), default workspace, and TLS verification. Only the fields you pass are changed. Persist settings across restarts via the KONG_ADMIN_URL / KONG_ADMIN_TOKEN / KONG_WORKSPACE environment variables in your MCP client config. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct action (configure, create, delete, get, list, update, upsert) or specific resource (workspaces, node info, node status, plugin schema). The generic kong_request tool fills gaps without overlapping with the CRUD tools. No two tools have ambiguous purposes.
All tools follow the 'kong_<verb>' or 'kong_<verb>_<noun>' pattern consistently, using lowercase with underscores. Examples: kong_create, kong_list_workspaces, kong_node_info. This pattern makes prediction and selection straightforward for an agent.
With 13 tools, the set is well-scoped for a Kong Admin API client. It covers connection management, CRUD operations, node diagnostics, plugin schema inspection, and a fallback generic request. No tool feels superfluous or missing.
The tools provide full lifecycle coverage for Kong entities (create, read, update, delete, upsert, list with pagination). The node info/status tools cover administrative monitoring, and the generic kong_request handles any API endpoint not explicitly exposed (e.g., RBAC, declarative config). No obvious gaps.