claude knows the world.oto hands it your tools.
crm, inboxes, linkedin, french company data — your agents (claude.ai, claude code) use them with your keys, held in a server-side vault. never pasted into a prompt.
№ 01 — access
three doors. one platform.
same account, same vault, same catalog — from claude code, claude.ai or your terminal.
two commands: the mcp connector configures itself and claude learns to drive the toolkit (universal skill).
then /oto:setup inside claude code installs the local cli (linkedin outreach included).
settings → connectors → add custom connector. oauth creates your account on first sign-in, and the connector also syncs into claude code.
json on stdout, composable with jq and xargs. for scripts, crons and bash agents.
№ 02 — catalog
your business tools, already wired.
22 connectors · 184 tools — derived from the platform's live catalog — a connector added server-side shows up here on its own.
№ 03 — the vault
your keys, never in the prompt.
every call resolves its credentials server-side, at execution time. the agent never sees a key — it sees the result.
cascading resolution
your key first. else your org's key. else the platform key — explicitly granted, under quota.
deny-by-default
sensitive connectors (inboxes, outreach) are closed by default: an explicit grant is required, per user.
encryption at rest
vault designed for aes-256-gcm envelope encryption. credentials never logged, never in a repo.
№ 04 — teams
one org, shared keys.
an organization owns its credentials — the company attio key, the growth team's serper — and its members inherit them. switch orgs, the vault follows.
the model runs in production on the platform; org management is handled with the oto team today, on request.
request an orgoto is built by otomata, alexis laporte's studio. handmade, in marseille.