getting started with oto.

Your Claude's memory and tools. You work in Claude, as usual. oto keeps what needs to last, your instructions, your working rules, the history of a topic, and gives it back to Claude from one conversation to the next and from one device to another. When you share a project, your colleagues benefit too.

oto also plugs into ChatGPT and Mistral.

Day to day, no: you ask Claude. "Create a project for the Martin file", "note in oto that we invoice at 30 days".

The dashboard, manage.oto.cx, is for three things: connecting the tools that need a key or an account, seeing what exists, and sharing.

Once, in two minutes.

• Individual plan (Free, Pro, Max): in Claude, Customize › Connectors, then + Add › Add custom connector. Name: oto. URL: https://mcp.oto.cx/mcp. Claude takes care of the rest: sign in to your oto account (email or Google). On Free, only one custom connector is allowed.
• Team or Enterprise plan: the owner of the Claude organization adds oto once for everyone, in Organization settings › Connectors › Add › Custom › Web, with the same name and URL. Then each member goes to Customize › Connectors, finds oto and clicks Connect.
• Then, in a conversation: turn oto on with the + button › Connectors. The rest is explained in Academy's Claude guide (in French).

Once connected, oto is available wherever you use Claude: web, desktop app, mobile.

On a Claude Team or Enterprise account, only the owner of the Claude organization can add oto, once for everyone. It's not an oto setting: ask them, then click Connect.

They also decide what Claude may do with each tool: see "In a team, who can connect what?" on Academy (in French).

• Project: the folder for a piece of work. It brings together the brief, the note pages and everything that work needs. It's what you open and what you share.
• Procedure: a way of doing something, written once to be repeated. It says what to do, in what order and with which tools.
• Table: rows and columns to keep the data of a piece of work. Claude fills them in, you look at them.

Everything you create is private by default. You share project by project, with a person, a team or the whole organization, read-only or with editing rights.

The administrator of your oto organization can view, read-only and with every view logged, what a member sees in the organization.

oto brings what Claude doesn't have: your business software, an internal back office, French public data (companies, law…). It also offers Gmail, Drive and Calendar, if your team prefers to keep everything in one place, and keeps your keys in the vault, on the server side.

For Claude's official connectors, see the Academy page (in French).

Only what the connected tool returns, when Claude asks for it. Nothing is copied in the background: Claude fetches on demand, and only imports in bulk if you ask it to.

Your organization's administrator can mask or pseudonymize fields (a social security number, an IBAN…) for the whole organization. Your keys and passwords stay in oto's vault, never with Claude.

Yes: an oto procedure can be run on its own by a Claude scheduled task, every day or every week, even with your computer off. To create the task, see "Faire tourner une tâche toute seule ?" on Academy (in French).

• Ask Claude: "explain how oto works". For a problem: "report to oto that…", and the message reaches us.
• Write to us: alexis@otomata.tech.
• Security and privacy: trust.oto.cx.
• For developers: docs.oto.cx.