access — mcp connector
connect claude.ai.
the remote mcp connector gives claude (web, desktop, code) access to the oto catalog: french company data, crm, gmail, linkedin, enrichment, datastore…
mcp endpoint
https://mcp.oto.cx/mcp
authentication
oauth via auth.oto.cx — the sign-in page creates your oto account on first sign-in. keys and access are then managed on manage.oto.cx.
how to connect
- i
add the connector in claude.ai
customize › connectors › + add › add custom connector. name: oto, then:
- url:
https://mcp.oto.cx/mcp
claude takes care of the rest: you sign in to oto, and your account is created along the way. on claude team or enterprise, the organization owner adds the connector, then everyone clicks connect.
not a developer? getting started with oto, in plain questions → - url:
- ii
add your keys (optional)
on manage.oto.cx, you connect your google accounts and your api keys (attio, hunter, serper…). each key stays in the vault, resolved server-side at execution.
- iii
run prompts
“find me 20 mid-size metal companies in normandy hiring a sales rep this year, with executives and emails” — claude orchestrates the connectors.
working in claude code?
the oto plugin does all of this in two commands — mcp connector + universal skill + cli setup.
$ claude plugin marketplace add otomata-tech/oto-plugin
which connectors are exposed?
french companies · linkedin · crm · gmail · tasks · web search · enrichment · datastore · … per-group details (params, examples) in the catalog.
security & privacy
- auth by oto account (self-hosted logto, oauth pkce — no shared password).
- your credentials live in the server-side vault — never in the agent's context, never logged.
- every call uses your keys: your linkedin session, your gmail, your attio. another user has no access to them.
- open data sources (recherche entreprises, sirene, dvf, bodacc) go through platform keys under per-user quota.
- linkedin is rate-limited per account — the agent waits when the limit is hit.