Give your AI application useful workspace context.
MCP, the Model Context Protocol, is a way for an AI application to call tools provided by another service. Sairo’s remote MCP server exposes a defined set of workspace operations, such as finding a visitor conversation or reading an approved answer.
You sign in to Sairo during connection, choose a workspace and select the website access. The application can then request the permitted information when you ask it to help. You do not need to copy transcripts into every new conversation or give the application your Sairo password.
A useful first request
Show the unanswered questions for my selected website. Find the relevant conversations and help me decide which answers need correcting.
Read the context. Prepare a useful next step.
Read access lets the application inspect your permitted workspace overview, conversations, knowledge, website details, leads and activity. It can check an answer against the selected website’s current knowledge.
If you also allow changes, supported tools can prepare and apply updates to saved answers, business facts, internal notes, conversation status, leads, source controls and assistant copy. Each change records what is being updated and supports dismissal or undo, subject to the current record and your permissions.
| Access | Examples | What to expect |
|---|---|---|
| Read | Find visitor questions, read saved answers, inspect lead follow-ups | Available within the workspace and website scope you approve. |
| Also allow changes | Correct an answer, update opening hours, prepare a follow-up date | Requires your existing editing permissions as well as write access for the connection. |
| Outside the tool set | Billing, team administration, outbound customer messages | These operations remain in their existing Sairo workflows. |
Choose the connection’s reach.
Start with read access. During sign-in, select one website or the currently permitted websites in a workspace. Enable “Also allow changes” only when you want the application to update supported records. A connection cannot grant more access than your existing team role.
Change tools prepare a recorded proposal before applying it. Ask the application to show you the proposed change and wait for approval; the application controls its own confirmation interface. If you allow write access, it can call the permitted apply tools, so choose that access deliberately.
Connections expire and can be disconnected from Connected apps in your Sairo account. Password changes and resets revoke them too. Signing out of the website alone leaves a separately authorised connection active. Changes to your role or website access require a fresh connection.
Use a client that supports remote MCP and OAuth.
Sairo uses Streamable HTTP with OAuth authorisation and PKCE. Compatible clients discover the sign-in flow from the server address. Claude’s custom-connector flow and Claude Code’s HTTP MCP configuration provide two ways to start.
Client capabilities, account access and organisation policies vary. This is a custom MCP connection, not a claim of listing in an application’s connector directory. A cloud client needs a publicly reachable HTTPS Sairo address; it cannot connect to a localhost preview on your computer.
Source references
Common questions
Do I need to share an API key?
For the supported OAuth connection, sign in on Sairo and approve access. You do not paste an AI provider key or Sairo password into the connector configuration.
Can I connect with read-only access?
Yes. Leave “Also allow changes” off. The application can then use permitted read tools, while write tools require additional connection access and the right team role.
Does disconnecting delete information already shared?
Disconnecting prevents further access through that connection. It does not delete information the external application has already received. Its own data and conversation settings govern that copy.