Skip to main content
Glama
aai-gateway
by gybob

English | 简体中文 | 日本語 | 한국어


AAI Gateway: Unified MCP & Skill Management, Shared Across AI Agents, 99% Context Token Savings

npm version license


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.


Related MCP server: Skillsmith

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:

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

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.

Available Tools

8 tools
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.

Inputs: tool (required), app, args.

disableAppA

Disable one app for the current agent only. If you do not know the app id, call listAllAaiApps first to find it.

Inputs: app (required).

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.

Inputs: app (required).

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.

Inputs: no named 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.

Inputs: no named parameters.

removeAppA

Remove one AAI Gateway managed import from all agents. If you do not know the app id, call listAllAaiApps first to find it.

Inputs: app (required), confirm (required).

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).

Inputs: no named parameters.

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.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers