AAI Gateway MCP
An MCP gateway imports servers and skills once and gives Claude Code, Codex and OpenCode short summaries instead of full schemas.
- 91 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- On an agent request the gateway finds and installs third-party MCP servers and skills that run code with user rights.
- One gateway exposes a set of apps to several agents at once.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/aai-gatewayDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- On an agent request the gateway finds and installs third-party MCP servers and skills that run code with user rights.
- One gateway exposes a set of apps to several agents at once.
This is third-party code. Review the repository files before installing.
What it does
AAI Gateway gathers MCP servers and skill packages under one name, Agent App. The agent sees each app as a short summary and loads tools only when needed. One import is available to every connected agent. Built-in tools: `search:discover` finds and installs new tools from a plain-language request, `mcp:import` and `skill:import` add a server or skill, `listAllAaiApps` lists them, `enableApp` and `disableApp` switch an app per agent, `aai:exec` calls a tool inside an app. Each imported app gets an `app_<app-id>` tool with the full guide.
Who it is for. Developers running a dozen MCP servers across several agents who are tired of repeating setup and spending context on schemas.
Good fit when
- The same server set is needed in Claude Code, Codex and OpenCode.
- Schemas of a dozen MCP servers eat the context of every chat.
- An agent is asked to find a tool for a task and install it without hand-editing JSON.
- A server author wants the gateway to discover the app by itself through an `aai.json` file.
Not a fit when
- One MCP server in one agent is enough.
- Installing new tools on an agent request without your review is unacceptable.
- You need an agent outside Claude Code, Codex, OpenCode and OpenClaw.
Example request
Use AAI to find a browser automation tool, install it and enable it for Codex.MCP
- Transport
- stdio
- Authentication
- not required
Limitations
Only locally installed Claude Code, Codex and OpenCode are discovered automatically. Connected servers run with your user rights, so check the source of a new tool yourself. The 99% token saving is the authors figure for 10 servers with 5 tools each; yours will differ. The last commit is dated August 2026. The project is young: three agents get auto-discovery and the rest are wired by hand.
How to disable. Remove the gateway entry with `claude mcp remove aai-gateway` or by editing the agent config. Imported apps are stored separately; clear them through `removeApp`.
FAQ
How do I connect AAI Gateway to Claude Code?
Run `claude mcp add --scope user --transport stdio aai-gateway -- npx -y aai-gateway`. For Codex use `codex mcp add aai-gateway -- npx -y aai-gateway`.
What is an Agent App?
A set of capabilities for an agent: an MCP server with tools or a skill package. The gateway stores both in one form and shows the agent a short summary.
How do I make my own server discoverable?
Describe it in an `aai.json` file with `command`, `file` or `path` checks and send a PR to `src/discovery/descriptors/`. Supported protocols are `mcp`, `skill` and `acp-agent`.
How does it avoid bloating context?
Each app gets a summary of under 50 tokens. The agent receives the full guide by calling `app_<app-id>` when needed.
Does the gateway work with OpenClaw?
Yes, through a separate plugin: `openclaw plugins install openclaw-aai-gateway-plugin`.
Discussion
No questions or reviews yet.
Related
MCP serversA local dashboard for running many agents across machines: memory, code graph and agent-to-agent messaging
A single Rust gateway between an agent and all its MCP servers: the client sees 9 to 17 meta-tools and finds the rest on demand.
A CLI that keeps coding agents' shared context in one place: instructions, skills, MCPs, subagents and durable memory across projects and machines
One command turns a local Claude Code, Codex or Pi agent into an A2A protocol server, and a Python SDK does the same for code.
A plugin for Claude Code and Codex: a shared task wall, project memory, reports and a dashboard that shows agents' work across sessions
A local MCP gateway: set servers up once and use them in Claude Code, Codex, Cursor and other agents, with keys in the OS keychain
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| AAI Gateway (this card) | no | not required | 91 | |
| MetaMCP | no | API key | 2,762 | a self-hosted gateway with an endpoint and auth; AAI Gateway runs locally over stdio and loads tools on demand |
| MCPM | no | 1,023 | an MCP server manager; AAI Gateway adds skills and tool discovery from the agent chat |
README in short
Each app costs under 50 tokens of context and details load on demand. The user states a need, and the gateway finds, installs and enables a tool without a restart.