One local gateway for every design tool.
Instead of loading dozens of MCP tool schemas into every prompt, ExonUI Grid exposes four compact meta-tools that search 36 catalog entries, read verified Grid Notes, and enforce write approvals before anything changes.
16 MCP packs16 Grid Notes4 profiles~97% fewer up-front tokens
Keep 97% of your schema budget out of the prompt
Direct MCP connections dump every downstream tool definition before your agent reads a single file. Grid loads four meta-tools up front and warms packs lazily on first search.
Up-front context cost (ADR 0002 spike)
4 meta-tools loaded up front; downstream schemas stay lazy
- grid_status~95 tokens
- grid_search~145 tokens
- grid_describe~135 tokens
- grid_call~155 tokens
Includes ~530 tokens for tool schemas plus ~100 tokens of gateway instructions.
- Cold warm-up (parallel)
- ~1.8 s
- Warm search & describe
- ~5 ms
- Downstream call overhead
- ~25 ms
Meta-tools surface
Meta exposure · ≤ 16 tools total- grid_statusIn spike
Show enabled packs, connection state, tool counts, and client capabilities.
- grid_searchIn spike
Search enabled tools, libraries, and Grid Notes with compact result cards.
- grid_describeIn spike
Return a tool's schema and resolved policy, or a pack's install + Grid Notes.
- grid_callIn spike
Execute a downstream tool through the policy engine and untrusted banner.
- grid_enable / disable / profilePhase 2
Toggle packs or switch explore/build/motion/review in exonui.json.
- library_docs & component_getPhase 2
Fetch Grid Notes, framework docs, and registry source + install commands.
- asset_search & design_utilsPhase 2
Query icons, Lottie, fonts, contrast checks, OKLCH palettes, and DTCG tokens.
- relay_checkpoint / resume / listPhase 2
Save and resume design sessions across Claude Code, Codex, Cursor, and OpenCode.
Search, describe, then call
Pick a real workflow below and step through what your agent sends to Grid and what Grid returns—including Grid Notes for libraries and interactive approval prompts for writes.
Canvas to component, step 1 of 3: grid_search — Search tools and packs.
Developer prompt
“Find the command to add a button from our shadcn registry without guessing flags.”
Step 1 · Agent calls grid_search
~110 tokens{
"query": "shadcn add command",
"kind": "tool",
"limit": 4
}Only the matching ids come back—no 73-tool schema dump.
Compact search cards
OK{
"results": [
{
"id": "shadcn:get_add_command_for_items",
"kind": "tool",
"pack": "shadcn",
"summary": "Generate the exact CLI add command for selected registry items."
},
{
"id": "shadcn:search_items_in_registries",
"kind": "tool",
"pack": "shadcn",
"summary": "Search configured shadcn registries by component name."
}
],
"next": "Call grid_describe with an id, then grid_call for tools."
}Reads run; writes ask or stop
Because aggregation hides downstream tool names from an agent's own permission prompt, Grid enforces per-pack policy itself and displays the complete JSON payload before running writes.
1. Downstream tool access level
2. Pack policy in exonui.json
Pack policy is "ask", so Grid pauses and shows an elicitation prompt with the exact JSON arguments.
Grid response
Allow paper:write_html (write)? Arguments (JSON data): {"target":"hero-frame"}Unannotated tools default to destructive unless listed in a pack’s curated readOnlyTools.
Named presets in exonui.json
Switch the active pool for exploring a canvas, building UI, authoring motion, or running reviews. Secrets stay in environment variables or your OS keychain—never in exonui.json.
Explore
profile: exploreInspect design canvases, Storybook components, and assets with read-safe defaults.
Enabled MCP packs (4)
- Paperread
- Figma (desktop MCP)read
- Penpotread
- Storybookread
Paired libraries & assets
{
"profile": "explore",
"exposure": "meta",
"packs": [
"paper",
"figma-desktop",
"penpot",
"storybook"
],
"policy": {
"paper": "read",
"figma-desktop": "read",
"penpot": "read",
"storybook": "read"
}
}exonui grid profile explore (coming in Phase 2).What works today and what ships in Phase 2
The Grid gateway lives in packages/grid inside the repository while we finish hardening, OS keychain auth, and the CLI. Everything in the catalog and setup wizard works today without Grid.
Working in the Grid spike
- • Four meta-tools (`grid_status`, `grid_search`, `grid_describe`, `grid_call`) over MCP SDK v2
- • MiniSearch index across catalog entries, downstream tools, and all 16 Grid Notes
- • Policy engine (`read` / `ask` / `write`), curated `readOnlyTools` fallback, and MCP form elicitation
- • Profile loading (`explore`, `build`, `motion`, `review`) from `exonui.json`
Coming in Phase 2 (M1)
- • Tool-list disk cache (`~/.exonui/cache`) so search answers instantly before packs warm
- • Downstream reconnect recovery, stderr diagnostics, and remote OAuth with OS keychain storage
- • `npx exonui init` CLI, local cross-agent Relay checkpoints, and native agent plugins
- • `library_docs`, `component_get`, `asset_search`, and `design_utils` meta-tools
- Setup wizardGenerate direct MCP configs for 11 agents today while Grid finishes Phase 2.
- Browse catalogExplore all 36 design tools, MCP servers, UI libraries, and assets.
- Grid NotesInspect verified library setup, gotchas, and accessibility checks like Lenis.
- Architecture docsRead how packs, Grid Notes, the catalog feed, and Grid fit together.