
AAI Gateway
- 104 repo stars
- Updated April 22, 2026
- gybob/aai-gateway
AAI Gateway is a MCP server that provides a unified gateway for MCP and skill management shared across AI agents with large context savings.
About
AAI Gateway is a developer-oriented MCP server that acts as a management and routing layer for other MCP servers and skills, advertised as cutting context token use by up to 99% when many tools would otherwise sit in every prompt. developers who accumulate dozens of MCP installs across Claude Code, Cursor, and Codex can point clients at one gateway instead of pasting huge tool schemas into each session. Complexity is intermediate because you still must understand which downstream servers the gateway exposes and how sharing works in your environment. Treat published token-savings figures as product positioning until you measure tool list.
- Unified MCP and Skill management gateway across AI agents
- Marketing claim of 99% context token savings vs loading all tool defs raw
- Shared gateway instance for Claude Code, Cursor, and other MCP clients
- npm stdio package aai-gateway v1.1.10
- Reduces duplicate MCP entries in per-editor config files
AAI Gateway by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add aai-gateway -- npx -y aai-gatewayAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 104 |
|---|---|
| Package | aai-gateway |
| Transport | STDIO |
| Auth | None |
| Last updated | April 22, 2026 |
| Repository | gybob/aai-gateway ↗ |
What it does
Centralize MCP and skill registration behind one gateway so every agent shares the same tool surface with far less context bloat.
Who is it for?
Power users running many MCP servers who want one shared management layer and lighter prompts.
Skip if: Skip if you only need one simple MCP, or teams that cannot add another hop in your agent toolchain.
What you get
One gateway registration can federate MCP and skill access for multiple agents with leaner tool metadata in context.
- Single AAI Gateway MCP endpoint in agent config
- Shared MCP and skill catalog across configured agents
- Leaner tool metadata surface for long MCP stacks
By the numbers
- Product claims 99% context token savings
- npm package aai-gateway version 1.1.10
- stdio transport
README.md
AAI Gateway: Unified MCP & Skill Management, Shared Across AI Agents, 99% Context Token Savings
What Is It
AAI = Agent App Interface
AAI Gateway is the interaction gateway for Agent Apps.
What is an Agent App? An Agent App is a collection of capabilities that an Agent can use. For example:
- An MCP Server is an Agent App — it provides a set of tools
- A Skill package is an Agent App — it provides one or more skills
In AAI Gateway, they are abstracted as Agent Apps under unified management. Import once, and all AI Agents can use them immediately.
What Problems Does It Solve
Context Bloat
Traditional: 10 MCPs × 5 tools = 50 full schemas ≈ 7,500 tokens injected into every conversation.
AAI Gateway: each Agent App needs only fewer than 50 tokens for a summary, with details loaded on demand. 99% token savings.
Finding Tools Is Hard
Traditional: search GitHub → read READMEs → copy JSON configs → debug connections → restart Agent.
AAI Gateway: tell your Agent "use AAI to search for xxx" — auto-searches, installs, ready to use.
"Use AAI to search for a browser automation tool"
→ Search → finds Playwright MCP → Agent summarizes a one-line Agent App summary → install → ready to use, no restart needed
"Use AAI to search for a PPT creation skill"
→ Search → finds PPT Skill → uses skill description as Agent App summary → install → ready to use, no restart needed
Duplicate Config
Configure the same thing in Claude Code, Codex, and OpenCode separately? Import once through AAI Gateway, all Agents share instantly.
Quick Start (30 Seconds)
Claude Code:
claude mcp add --scope user --transport stdio aai-gateway -- npx -y aai-gateway
Codex:
codex mcp add aai-gateway -- npx -y aai-gateway
OpenCode — add to ~/.config/opencode/opencode.json:
{
"mcp": {
"aai-gateway": {
"type": "local",
"command": ["npx", "-y", "aai-gateway"],
"enabled": true
}
}
}
openclaw plugins install openclaw-aai-gateway-plugin
Once installed, just tell your Agent what you want to do.
Built-in Tools
| Tool | Description |
|---|---|
search:discover |
Search and install new tools with natural language |
mcp:import |
Import an MCP Server as an Agent App |
skill:import |
Import a Skill package as an Agent App |
listAllAaiApps |
List all registered Agent Apps |
enableApp / disableApp |
Enable or disable an Agent App per Agent |
removeApp |
Remove an Agent App |
aai:exec |
Execute a specific tool within an Agent App |
Each imported Agent App generates an app_<app-id> tool that returns the full operation guide and tool list when called.
Preset Agent Apps (auto-discovered when locally installed)
| App ID | Name | Description |
|---|---|---|
claude |
Claude Code | AI coding assistant for code editing, analysis, and development |
codex |
Codex | OpenAI-powered AI coding assistant |
opencode |
OpenCode | AI development assistant for editing files and running commands |
Architecture

Developers: Get Your Agent App Auto-Discovered
Create an aai.json descriptor and submit it to src/discovery/descriptors/. When a user's local environment meets the discovery.checks conditions, the Agent will auto-discover your Agent App.
{
"schemaVersion": "2.0",
"version": "1.0.0",
"app": {
"name": { "default": "My App" }
},
"discovery": {
"checks": [
{ "kind": "command", "command": "my-app" }
]
},
"access": {
"protocol": "mcp",
"config": {
"command": "my-app-mcp",
"args": ["--stdio"]
}
},
"exposure": {
"summary": "Use when the user wants to do X."
}
}
discovery.checks supports three check types: command (command exists), file (file exists), path (directory exists).
Supported protocols: mcp, skill, acp-agent
Welcome to submit a PR to contribute new Agent App descriptors, or open an issue for feedback.
Recommended MCP Servers
How it compares
Meta-gateway for MCP and skills—not a replacement for individual domain servers like Gmail or Grist.
FAQ
Who is AAI Gateway for?
Developers and integrators who run multiple MCP servers and skills across Claude Code, Cursor, Codex, or generic MCP hosts.
When should I use AAI Gateway?
Use it during Build when configuring agent-tooling and your tool list or token usage from raw MCP definitions becomes painful.
How do I add AAI Gateway to my agent?
Install the npm package aai-gateway, register it as a stdio MCP server in your agent config, then attach your other MCP servers and skills through the gateway per its repository docs.