Replai

tw.replaiPublished by replai.twOfficial publisherv1.13.0Updated Oct 30, 2026

Set up, test and publish an AI customer support Agent for your SaaS product.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Replai is a remote MCP server that lets an assistant set up, test and publish an AI customer support agent for a SaaS product.

What you can do
  • Set up an AI customer support agent for a SaaS product
  • Test the agent before it goes live
  • Publish the agent so it can handle customer support
  • No individual tools are listed in the registry entry, so the exact operations are not documented here.
When to use it
Consider it when you want an assistant to help build, try out and launch an AI support agent for your SaaS product rather than doing that setup by hand.
Requirements
A remote MCP endpoint at api.replai.tw over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
OAuth access is required, so the server acts on your Replai account. It can publish an agent, which changes what customers see, so review the agent before publishing. The registry lists no tools, so what it can read or modify is not documented.

Installation

In SourceWeft

  1. Open Replai in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/tw.replai%2Freplai/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "replai": {
      "type": "http",
      "url": "https://api.replai.tw/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

6
  1. v1.13.0LatestOct 30, 2026
  2. v1.12.0Oct 30, 2026
  3. v1.8.0Oct 26, 2026
  4. v1.1.1Oct 25, 2026
  5. v1.0.1Oct 24, 2026
  6. v1.0.0Oct 20, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.