User guide¶
The console has four workspaces: Chat, Connections, Team & keys and Activity. Sign in with the credentials created during local setup.
Roles and permissions¶
The bundled connections start with these permissions:
| Action | Administrator | Member |
|---|---|---|
| Read products, orders, policies and shipping estimates | Yes | Yes, for tools marked as read |
| Create products and update orders | Yes | No |
| View connection summaries | Yes | Yes |
| Register, edit or disable upstream servers | Yes | No |
| Change tool permissions or manage the team | Yes | No |
| Create and revoke API keys | Own keys or another member's keys | Own keys |
| View activity | All users | Own activity |
These rules are enforced by the backend. Newly discovered tools default to administrator-only until an administrator reviews them and marks them as read tools. A read permission means the tool is made available to members; only assign it to a tool whose behavior you trust to be read-only.
Use chat and review writes¶
Chat uses the tools available to the signed-in user. Start with a read, such as:
What products are in the store?
Tool calls and their results remain visible in the conversation. An administrator can propose a change:
Create a product called Field notebook priced at INR 249, SKU FIELD-NOTEBOOK-01.
Review the proposed tool and arguments before approving. Use a unique SKU for each demonstration. Confirmations are tied to the user session, expire after five minutes and can be used only once. The gateway checks the target and current permissions again before dispatch.
If a write times out, check the store before trying again. A lost response does not prove that the store rejected the change, and the gateway does not automatically retry writes. Conversation content stays in the browser tab; tool activity is recorded in PostgreSQL.
Complete a store order¶
- After an approved product creation succeeds, inspect the returned product and open the storefront.
- Add the product to the cart and check out with a fictional Indian address, such as Bengaluru, Karnataka, 560038.
- Choose Cash on delivery. This is a demo store; no money or shipment is processed.
- Open WordPress administration and find the order under WooCommerce > Orders.
- Return to chat and ask:
What orders came in today?
The store uses INR and the Asia/Kolkata timezone. Use synthetic data for checkout. The sample store has no outbound email provider.
Invite a member¶
In Team & keys, create a member invitation and copy its link. Invitations are delivered by copying the link; the application does not send email. They expire after two days and can be accepted once.
Accepting an invitation signs in as that invited account, replacing any existing session in the same browser profile. Other tabs refresh their identity and clear the previous account's workspace state. Use a separate browser profile if you need administrator and member sessions open simultaneously.
An invalid, expired or used link leaves the current session unchanged. An existing member can sign in through /login. Keep invitation links private because their tokens allow account creation.
Connect an external client¶
As the member, create an API key in Team & keys. Copy it when it is displayed; the complete key is shown once. An external client needs only the gateway's /mcp URL and that key as a bearer credential. It does not receive store or upstream credentials.
Follow the external client guide for MCP Inspector and the standalone reference agent. As a multi-server example, ask:
Read the shipping policy and quote delivery for an INR 1700 order to Karnataka, India. Use both tools.
This combines the policy and shipping upstreams. The sample table charges INR 59 for standard regions or INR 99 for the documented remote states, plus INR 20 per additional 0.5 kg. Orders of INR 1500 or more ship free. The storefront uses the same sample rules. Shipping quotes are estimates from that table, not a carrier integration.
Manage connections and access¶
Administrators manage upstreams and their tool permissions in Connections. Connection status refreshes while the page is visible. A disabled upstream disappears from tool discovery. Refresh an external client's catalog or reconnect after changing the registry; stale direct calls are rejected even if a client retains a cached tool name.
Revoke a key in Team & keys when it is no longer needed. Its next request fails, including requests on an initialized MCP transport. An operation that has already been dispatched may still finish. The system also prevents removing or deactivating the last active administrator.
Use Activity to inspect attributable tool calls, their outcome and duration. Members see only their own activity; administrators can inspect all users. The audit trail is distinct from the browser's conversation history.
For a complete presentation, use the demo walkthrough. For permission boundaries and remaining risks, read the threat model.