AAI Gateway

io.github.gybobPublished by GitHub account gybobv1.1.10Updated Oct 24, 2026

Unified MCP & Skill management gateway, shared across AI agents, 99% context token savings

VerifiedSTDIODesktop onlyProductivity & Workflow Developer Tools AI & ML

Server details

Identifier: io.github.gybob/aai-gateway
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account gybob for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.gybob%2Faai-gateway.svg)](https://sourceweft.com/mcp/io.github.gybob%2Faai-gateway?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local gateway that registers MCP servers and skill packages as shared "Agent Apps", letting an assistant search, install, enable and run them on demand.

What you can do: Search for and install new tools or Agent Apps from a natural-language request
Import MCP servers and skill packages as managed Agent Apps
List registered Agent Apps and enable or disable them per agent
Remove Agent Apps and execute a specific tool inside one
Expose each imported app as an app_ tool that returns its operation guide and tool list
Auto-discover preset apps such as Claude Code, Codex and OpenCode when installed locally
When to use it: Useful when you connect many MCP servers or skills to several AI agents and want one shared registry instead of repeated per-agent configuration, and when you want tool schemas loaded on demand rather than injected into every conversation.
Requirements: Runs as a local stdio process on the user's machine, started with npx from the npm package aai-gateway, so Node.js and network access for package download are needed. No authentication, environment variables or headers are declared. Desktop only; not available as a web executable.

Before you install

The gateway can install and import third-party MCP servers and skill packages and execute their tools, so it runs code and tools from outside sources on your machine. It can also remove Agent Apps and change which apps are enabled per agent. Review what gets installed before relying on it.

Installation

In SourceWeft

Open AAI Gateway in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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.

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:

Codex:

OpenCode — add to ~/.config/opencode/opencode.json:

json

{  "mcp": {    "aai-gateway": {      "type": "local",      "command": ["npx", "-y", "aai-gateway"],      "enabled": true    }  }}

{  "mcp": {    "aai-gateway": {      "type": "local",      "command": ["npx", "-y", "aai-gateway"],      "enabled": true    }  }}

OpenClaw:

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.

json

{  "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."  }}

{  "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.

Source: README.md at commit 8ef730b

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.1.10LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts