AAI Gateway
Unified MCP & Skill management gateway, shared across AI agents, 99% context token savings
Install AAI Gateway
Pick your client, then add it in one click or paste the config.
~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": {
"aai-gateway": {
"command": "npx",
"args": [
"-y",
"aai-gateway"
]
}
}
}
Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.
We couldn’t confirm it starts correctly
The install command started, but didn't respond the way we expected when we tried to talk to it.
npx -y aai-gatewayinitialize succeeded but no response to tools/list.
This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 7d ago.
Overview
Security & health
What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.
Recent health check succeeded.
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Scanned 14d ago via OSV.dev · aai-gateway (npm)
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
From the project README
English | 简体ä¸æ–‡ | 日本語 | í•œêµì–´
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.
Reviews
No reviews yet — be the first to share how it worked for you.
Frequently Asked Questions about AAI Gateway
Related MCP servers
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/aai-gateway)<a href="https://allmcps.com/mcp/aai-gateway"><img src="https://allmcps.com/api/badge/aai-gateway?style=directory" alt="AAI Gateway on AllMCPs" /></a>