aai-gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aai:execA | Execute any AAI tool action. Read the guide first (call app:*, mcp:import, skill:import, or search:discover) — it contains the required schema and parameters. |
| mcp:importA | Import an MCP server as a GLOBAL app (visible to all projects). For project-level MCP, use your agent's native config instead (e.g. .mcp.json, .cursor/mcp.json). Call this first to get the import guide. Never ask the user for API keys or secrets in chat. |
| skill:importA | Import a local skill as a GLOBAL app (visible to all projects). For project-level skills, use your agent's native skill directory instead (e.g. .claude/skills/). Call this first to get the import guide. |
| listAllAaiAppsA | List imported apps (MCP servers and skills) for the current agent. This does not include built-in tools like search:discover, mcp:import, or skill:import — those are always available. |
| disableAppA | Disable one app for the current agent only. If you do not know the app id, call listAllAaiApps first to find it. |
| enableAppA | Enable or re-enable an app for the current agent. When the user asks to enable, start, turn on, or use a specific app by name, call listAllAaiApps first to check if it is already imported before searching for new tools. |
| removeAppA | Remove one AAI Gateway managed import from all agents. If you do not know the app id, call listAllAaiApps first to find it. |
| search:discoverA | Find and install new tools. Call this when: 1. The user explicitly asks to search for or install tools. 2. The user's request cannot be fulfilled by any currently available tool — proactively suggest and search for a suitable tool. Before searching, check listAllAaiApps first — the user may already have the app imported (possibly disabled). |
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 8 tools
Most tools have distinct purposes (e.g., disableApp vs enableApp, specific imports), but 'aai:exec' is a catch-all that could overlap with other actions, causing mild ambiguity.
Names mix colon-separated (aai:exec, mcp:import) and camelCase (disableApp, listAllAaiApps), creating an inconsistent pattern. Though readable, the lack of a uniform convention is noticeable.
Eight tools cover the core functions (list, enable, disable, remove, import, search, execute) without being excessive. The scope is well-contained for a gateway server.
The tool set covers key lifecycle operations for apps and imports. Missing explicit update or detail tools, but 'aai:exec' may fill those gaps; minor gap in app detail retrieval.