Bring your own assistant.

Every practice now has an assistant open in another window. The problem is that it knows nothing about your jobs — so you end up pasting in a fee schedule, describing where a project is up to, and getting confident answers built on whatever you happened to paste.

MCP closes that gap. It is the standard way an assistant connects to software it does not own, and Setout speaks it. Connect your practice once, and questions like “what is outstanding from clients across every job?” or “which projects have had nothing happen in a fortnight?” are answered from your live records — the same stages, deliverables, decisions and time entries your team is working in today.

It has your access, not its own

The connector does not get an account of its own. It signs in as you and carries your role, so an assistant asked about a project you cannot open simply cannot open it either. That is not a setting to remember: every request is checked against the same permissions the app enforces, on the way in.

Access starts read-only. The assistant can answer, gather and summarise, but it cannot alter anything — which is the right place to start, because an assistant that quietly edits live project records is worse than no assistant at all. Writing arrives as a suggestion queue: the assistant proposes the change, you see exactly what it would do, and you approve or discard it. Anything applied can be undone.

Nothing to maintain

There is no separate integration to configure and no list of actions to keep in step. Each tool the assistant sees is an endpoint of the Setout API, offered with your permissions already applied, so the connector cannot drift from the product or expose something it should not.

The connector is included with every plan. We are switching it on for early-access practices as we go — tell us you want it and we will set yours up.