Skip to main content
Connect Replo to another AI client by adding Replo’s public MCP server and authorizing access to your account.

MCP server URL

Replo’s public MCP server is available at:
Your client must support remote streamable HTTP servers and OAuth 2.1 with PKCE. Replo public API keys do not work on this endpoint. The client must complete the browser OAuth flow.

Connect another AI client

1

Add the Replo MCP server

Open your AI client’s MCP or integrations settings, then choose the option to add a remote MCP server. Paste https://api.replo.app/v1/mcp into the server URL field.
2

Complete OAuth when prompted

Your client discovers auth from Replo’s OAuth protected-resource metadata, registers through dynamic client registration, and opens a Replo sign-in window. Sign in to the account whose projects you want, confirm the requesting app, then select Allow access.
3

Ask Replo something

After authorization, ask your client a Replo question, for example:
Claude and ChatGPT have verified Replo connectors with one-click installation. For those clients, follow Use Replo with Claude and ChatGPT instead of configuring the URL manually.

Connect from OpenClaw

OpenClaw needs 2 extra steps. It defaults to a transport Replo does not accept, and it does not finish the browser sign-in on its own, so you capture the authorization code yourself. Before you start, confirm OpenClaw runs on Node 22.22.3 or later and that nothing else is using port 8989.
1

Add the Replo MCP server

Include --transport streamable-http. Without it, OpenClaw uses a transport Replo does not accept and the connection fails with a 405 error.
2

Start the sign-in

This prints an authorization URL and exits without opening your browser. Leave the URL for the next steps.
3

Start a listener for the redirect

In a second terminal, run this before you open the URL. It waits for Replo to redirect back and prints your authorization code.
4

Approve access in your browser

Open the URL from step 2, sign in to Replo, confirm that OpenClaw is the app requesting access, then select Allow access.Your browser shows Authorized. Return to your terminal. and the second terminal prints the authorization code.
5

Finish the sign-in

Pass the code back to OpenClaw, replacing CODE with the value from the previous step.
6

Confirm the connection

Check that OpenClaw is authorized and can see the Replo tools.
openclaw mcp status reports replo: streamable-http oauth authorized.
Your authorization code is a credential. Use it only in the openclaw mcp login command. Never paste it into a chat, a website, or a message to another person.
If you cannot run the listener in step 3, open the URL and select Allow access anyway. Your browser then fails to load a 127.0.0.1:8989 page, which is expected. Copy the code value out of the address bar, stopping before &state=, and pass it to openclaw mcp login replo --code CODE.

Fix an OpenClaw connection

  • The connection returns a 405 error. The transport is not set. Run openclaw mcp unset replo, then add the server again with --transport streamable-http.
  • The authorization code is rejected. The saved sign-in state is stale. Run openclaw mcp logout replo and start again.
  • The connection stops working after several months. Sign-ins expire after 90 days. Run openclaw mcp logout replo, then authorize again.