aai-gateway 0.4.0 → 0.4.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -1
- package/dist/cli.js +346 -369
- package/dist/cli.js.map +1 -1
- package/dist/index.js +441 -438
- package/dist/index.js.map +1 -1
- package/dist/server-C2U35Fro.js +4126 -0
- package/dist/server-C2U35Fro.js.map +1 -0
- package/package.json +23 -11
- package/dist/server-C2Hyt-lR.js +0 -15444
- package/dist/server-C2Hyt-lR.js.map +0 -1
package/README.md
CHANGED
|
@@ -9,7 +9,17 @@ You connect your AI tool once. AAI Gateway handles discovery, import, routing, a
|
|
|
9
9
|
Why this matters:
|
|
10
10
|
|
|
11
11
|
- One MCP connection instead of one MCP per app
|
|
12
|
-
- Smaller context
|
|
12
|
+
- Smaller context through progressive disclosure — AAI Gateway never exposes raw tool definitions upfront
|
|
13
|
+
|
|
14
|
+
**App-level exposure, not tool-level.** Tools are grouped into apps and only the app interface is visible initially. Users interact through `app:<id>` guides instead of seeing dozens of individual tools.
|
|
15
|
+
|
|
16
|
+
**Two app interfaces, user chooses:**
|
|
17
|
+
|
|
18
|
+
- `summary` — a natural language description; good for automatic triggering
|
|
19
|
+
- `keywords` — a compact keyword set; further reduces context overhead when users reference tools explicitly
|
|
20
|
+
|
|
21
|
+
Both modes keep the full tool capability available downstream — it just stays hidden until actually needed.
|
|
22
|
+
|
|
13
23
|
- A cleaner path to mix MCP servers, skills, ACP agents, and CLI-backed apps
|
|
14
24
|
|
|
15
25
|
AAI Gateway is for one goal: make tool ecosystems feel smaller, sharper, and easier for agents to use.
|