Before you connect.
You need a Sairo account with access to a workspace and at least one website. Check that you can open the website’s knowledge or conversations in Sairo first. The connection keeps your existing role and project permissions.
Your Claude account or organisation must allow custom remote connectors. Availability and settings can change, so check Claude’s current help page if the option is missing. Use the server address on Sairo’s connection page. Cloud applications need the deployed HTTPS address; a local preview address only works for a client that can reach that computer.
Source references
Add a custom connector in Claude.
In Claude, open Customize, then Connectors. Choose the option to add a custom connector, name it Sairo and enter the server URL. For an organisation-managed account, an owner may need to add the connector first.
Choose Connect when prompted. The browser opens Sairo’s sign-in and permission screen. Sign in there with your Sairo account, rather than entering that password into a chat message.
Choose the workspace, website and access.
Check the application name, choose the intended workspace and select one website or the currently permitted websites. Leave “Also allow changes” off for your first connection if you only want to search and review information.
When you want help applying corrections or other supported updates, allow changes if the option is offered and your role permits it. Approve the connection and return to Claude. If you selected the wrong workspace or website, disconnect and repeat the flow with the correct scope.
Test a read before asking for a change.
Ask Claude to use Sairo to show your workspace overview, then find a conversation or saved answer you recognise. Check that the results belong to the website you approved. Empty results can mean that the selected site has no matching conversations yet.
For a correction, give the actual question and approved answer. Ask Claude to prepare the change and show the website and replacement wording before applying it. The client controls its own confirmation experience; read-only access is the option when you do not want it to write.
Example first request
Use Sairo to show my selected website and its recent visitor questions. Read the saved answer about opening hours. Do not make any changes.
Connect from Claude Code.
Add the server using Claude Code’s HTTP transport. The command below uses Sairo’s public origin; substitute the HTTPS server address shown on your connection page when using another deployment.
Inside Claude Code, run /mcp and follow the browser authentication prompt for Sairo. The same workspace and website selection applies. You do not need a static bearer token for the OAuth flow.
claude mcp add --transport http sairo https://sairo.app/mcpSource references
If connection or access fails.
A cloud client cannot reach localhost. Copy the deployed HTTPS address from the connection page and confirm that the service is reachable. Opening the MCP endpoint in a normal browser can show an authentication or method response; use the client’s connection status to test it.
If sign-in succeeds but the expected records are missing, check the selected website and your Sairo role. Reconnect after a role, project or website-access change. If reads work but changes fail, check both the connection’s write access and your team editing permission.
An expired connection or changed password requires sign-in again. For an unsupported client, confirm support for remote Streamable HTTP and OAuth with PKCE. Legacy SSE-only clients and configurations that only launch a local process are not the same connection method.
Manage and disconnect the application.
Open Connected apps in your Sairo account to review your connections and disconnect one. Disconnecting revokes further access through that connection. Signing out of the Sairo website alone does not revoke it.
Information already returned to Claude remains subject to Claude’s own conversation and data settings. Removing a connection does not erase that previously shared information. Review both services when you need to manage a stored conversation.