Sign-in does not open
Check that your client supports OAuth for remote MCP servers. Replier does not use a static API key.
Connect Replier with MCP
Use Replier's remote MCP server in an AI app that supports HTTP MCP connections and OAuth sign-in. No API key is needed.
Replier MCP server URL
Remote HTTP endpoint
https://api.usereplier.com/mcpEnter this URL in your client's remote MCP server or custom connector settings. Use OAuth to authorize Replier.
Connect your client
- 1
Add a remote server
In your AI client's MCP settings, create a remote HTTP server named Replier.
- 2
Enter the endpoint
Paste the URL above and choose OAuth or browser-based sign-in if asked.
- 3
Authorize and test
Sign in to Replier, review access, then ask your AI app to list your Replier workspaces.
Connect with an AI prompt
If your AI app can edit its own MCP settings, such as a coding agent, paste this prompt into a chat. It includes the server URL and the JSON config for clients that use one.
Connect the Replier MCP server to this app.
- Server name: replier
- Transport: remote HTTP (Streamable HTTP)
- URL: https://api.usereplier.com/mcp
- Authentication: OAuth sign-in in the browser. Replier does not use an API key.
If this app uses a JSON MCP config, add:
{
"mcpServers": {
"replier": {
"type": "http",
"url": "https://api.usereplier.com/mcp"
}
}
}
Once it is connected, list my Replier workspaces to confirm it works.Access and troubleshooting
A tool is unavailable
Your client's capabilities, plan, and Replier workspace permissions determine available actions.
Reconnect or revoke access
Reconnect from your client if needed. Pause or revoke access from Replier Account → Connections.
For app-specific steps, see the Claude connector guide / ChatGPT setup guide.