Reos runs a remote MCP server, so an AI assistant can work inside your research workspace: read observations and transcripts, search across projects, start an analysis flow, and write results back. Claude, ChatGPT, and any other MCP-capable client connect the same way.
The connection is scoped to your own account. An assistant sees exactly what you see, with the same role and the same project access - never more.
Connect
The server URL is:
https://www.reos.ai/api/mcp
In Claude: open Settings → Connectors → Add custom connector, paste the URL, and click Connect. Claude opens a Reos sign-in page, you pick the organisation to connect, and you approve the connection. Claude registers itself automatically - there is no client ID or secret to copy.
In ChatGPT: open Settings → Connectors → Advanced → Developer mode, then add a connector with the same URL. Sign in to Reos and approve, exactly as above. Developer mode is available on ChatGPT Pro, Team, Enterprise and Edu plans.
In another client: point it at the same URL. The server speaks Streamable HTTP and authenticates with OAuth 2.1, including dynamic client registration, so any spec-compliant client can complete the handshake on its own.
Once connected, ask the assistant something like "what are the top insights from my onboarding research?" and it will pick the tools it needs.
Deep research and cited answers
ChatGPT can also treat Reos as a research source, so a deep research run searches your workspace alongside everything else it consults and cites what it used.
Two tools make that work. search takes a plain question and returns matching items, each with a link. fetch takes one of those items and returns it in full. Because every result carries a link back to the item in Reos, an answer that leans on your research can point at the exact observation or insight behind each claim - and anyone reading the answer can open it, provided they have access to that project.
Both tools are read-only and act on the organisation you connected. To search a different organisation, connect it separately.
What the assistant can do
The tools follow the DECODE funnel - raw data, then observations, then insights, then solutions - and split cleanly into reading and writing.
Reading - search your research and read any result in full; list projects, flows, entities, documents and tags; read observations (including everything a single participant said); pull a transcript or a still frame from a recording; read the timecoded comments and markers on a resource; check the status and results of a flow run; and list the organisations your account can reach.
Writing - create a project, add raw data by pasting text or importing a public URL, start a flow run, create a document, and edit or delete entities.
Every write tool is annotated so your assistant asks before it runs. Read-only tools can run without a prompt each time, which is what makes a research conversation feel fluid rather than click-heavy.
Permissions
Your organisation role decides which tools exist at all:
| Role | What the assistant gets |
|---|---|
| Owner, admin, member | Every tool, reading and writing |
| Viewer | Read-only tools |
| Stakeholder | No tools |
On top of that, every call re-checks project access, so an assistant can only reach projects you can already open. Writing to a project needs write access to that project specifically.
Working across organisations
If your account belongs to more than one organisation, you do not need a second connection. Ask the assistant to list your organisations, then name the one you want - each tool accepts an organisation id per call, and your role is evaluated separately in each one.
The two deep-research tools, search and fetch, are the exception: their shape is fixed by ChatGPT and takes no organisation argument, so they always act on the organisation you connected.
Managing and revoking access
Connected assistants are listed under AI assistants in your profile menu, where you can revoke any of them. Revoking takes effect immediately: the assistant's access token stops working and it cannot obtain a new one.
Access tokens last one hour and are refreshed silently in the background. A connection you never use expires on its own after 90 days.
Privacy and data handling
The server reads and writes only your Reos workspace data, through Reos's own API, under your identity and role. It does not read your assistant's memory, chat history, or files, and it does not collect your conversations. Data handling is covered by the Reos privacy policy.
Getting help
Something not working, or a tool behaving oddly? Email support@reos.ai and we will take a look.
