Aeion WebMCP for Admin AI Assistant
Admin power users spend hours each day on routine multi-step operations — bulk archive stale products, merge duplicate contacts, publish drafts to staging, audit which API keys haven't been used in 90 days. WebMCP gives them a browser-native AI assistant that operates the admin UI directly via 180+ pre-built tools (and any custom tool a developer registers via `useAeionTool`). Natural-language commands replace clickstreams. Permissions inherit from the admin's session. Audit trail is automatic.
The Power-User Problem
Most admin UIs are designed for "click each row to do the thing." Power users — operations managers, customer-success leads, growth analysts, IT admins — work in batches. A typical day:
What "AI Operating the UI" Looks Like
`
Common Admin AI Workflows
`
What WebMCP Tools Look Like
```typescript
Permission Inheritance + Audit
`
Failure Modes — Where WebMCP Admin Assistant Can Go Wrong
`
FAQ
Chrome extensions install per-browser, need approval to update, lose state on browser restart, can't be governed centrally, and have full read access to the page (security risk). WebMCP lives in your application — installed centrally, governed by RBAC, scoped to your domain, no browser-level permissions needed.
Anthropic Claude (recommended), OpenAI GPT-4/5, Google Gemini, and any model that supports tool/function calling. AI provider gateway routes calls; per-tenant model selection.
Developers register tools via `useAeionTool` from React components. Admins consume them. For citizen-developer scenarios, a low-code custom tool builder UI in admin lets non-engineers register their own automations — included free with any module, no separate tier required.
~2-5 seconds for simple commands (single tool call). 10-30 seconds for complex multi-step orchestration. Streaming responses make this feel faster.
Yes, if the admin's role grants them PII access. The AI inherits the admin's permissions, including any data masking. For high-sensitivity data, use the AI provider gateway's per-field data-classification rules.
Yes, custom tools can manipulate React state via useAeionTool. Common use: scroll to row, highlight result, fill form, navigate to detail page.
Strict. Tool calls run in the admin's tenant context. Cross-tenant calls require explicit tenant_id parameter + super-admin role.
Per-call LLM cost (routed through AI provider gateway with per-tenant cost caps). WebMCP itself is free; AI inference is per-token billing on your chosen provider.
(1) Permission checks block out-of-scope ops. (2) Destructive tools have preview mode. (3) Per-tool rate limits. (4) Audit log enables rollback. (5) Aegis Bulk Undo can reverse runaway changes after the fact.
Yes — WebMCP implements the `navigator.modelContext` polyfill that mirrors the W3C draft spec. As browsers natively implement MCP, WebMCP transparently switches to native.