Connect
The place in Caura Prism for plugging agents and tools into Caura — the Get started checklist and client snippets, keys, and the MCP console — and what each person sees there.
Connect answers one question: how do I plug an agent or a tool into Caura? Its line under the title reads "Plug agents and tools into Caura."
Connect works on the tenant chosen in the switcher at the top of the sidebar: the keys you make and the snippets you copy are for that tenant. With no tenant chosen, a tab says so and offers Choose a tenant. See Tenants.
Who sees what
All three tabs are shown to everyone in the tenant. What Keys shows depends on your role; see below.
Get started
The Get started checklist, step by step:
- See your team tenant, in organizations that have it switched on: done once a shared tenant has been shared with you.
- Create a key.
- Write your first memory.
- Connect your agent.
Each step ticks itself off when it is done. Without the Manage API credentials permission there are no key and agent steps, since keys are made by people with it: ask an organization admin for one. Your checklist is then done once your first memory is in. You can dismiss the checklist; it then stays hidden for that tenant in this browser. A new tenant with no memories also shows it on Memory › Memories.
Once the checklist is done or dismissed, the tab shows Connect a client instead: pick your agent, paste the snippet, restart it. Each agent writes under its own name. Manage keys opens Connect › Keys, and a link at the bottom opens the MCP console.
See Quickstart and the guides for each client under Integrations, such as Claude Code and MCP.
Keys
Every key lives here. Keys start with mc_, and the full key is shown once,
when it is made: copy it then.
If your role can manage the organization's credentials (org admins can), Keys lists every credential in the organization and lets you create and revoke them. Create a key has no kind picker: its Read scope makes either an API key (Home tenant only) or a Cross-tenant key (Read all tenants in this org). The Kind column also shows keys made elsewhere:
| Kind | What it is for |
|---|---|
| API key | one tenant; the program using it says which agent is calling |
| Cross-tenant key | reads memories across several tenants; writes stay in its home tenant |
| Agent key | one agent in one tenant; made by the OpenClaw plugin, caura-bus join or the provisioning API |
| Org admin key | the whole organization, every tenant; made through the API; use sparingly |
Right after you create one, the page offers a client config with the new key already filled in. To onboard a broker, use Agents › Machines › Onboard instead.
Everyone else sees this tenant's connection details (tenant ID, MCP server URL and API base URL). Creating, listing and revoking keys needs the Manage API credentials permission, so ask an organization admin for a key.
See Per-agent keys and Cross-tenant credentials.
MCP console
Try Caura's MCP tools against this tenant without connecting an agent. The page
shows the MCP endpoint and lists the tools (such as caura_write,
caura_recall, caura_list, caura_manage and caura_doc), each with a
description and example parameters. Pick one, edit the parameters, Execute
it and read the response. To get a memory by its ID, run caura_manage with
op: read.
The console calls tools as the agent console- followed by the part of your
email address before the @. Memories you write on the Write tab of
Ask your memory use the same agent.
Calls you run here act on this tenant's real memory: a write here is a real write. See MCP.
Insights
The place in Caura Prism that says what happened and how safe it is — the activity report, per-agent summaries, the security scan and what memory was worth — and who sees each tab.
Settings
The place in Caura Prism for this tenant's settings, your organization's plan, members, tenants and roles, and your own profile — what each page in the side list does and who sees it.