Your widgets, your catalog
Sign in to design widgets, themes, schemas and actions, keep the secrets your actions use, create MCP API keys, and see everything appear in your own catalog on the next tool call.
A prompt action proposes a message the user reviews and sends. An http action runs server-side against a fixed URL and must pass a test call before it can be saved.
Secrets are encrypted with a vault-held key, injected into http actions by name, and never shown again after you enter them.
Sign-in identities
API keys
Keys always read your catalog. Tick execute to let widgets rendered with that key run http actions (using your secrets). Scopes are fixed at creation.
| Name | Created | Digest | Scopes | Status |
|---|
Point an MCP host at https://mcp.widgentic.dev/mcp?key=…
(or send the key as x-api-key). Keys never write to your catalog;
only execute keys can run widget actions.