ChatRail

dev.chatrailPublished by chatrail.devOfficial publisherv0.1.0Updated Nov 2, 2026

Inspect WhatsApp connections, groups, message delivery, schedules and webhooks in ChatRail.

VerifiedStreamable HTTPWeb executableDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

ChatRail's hosted MCP server lets an assistant inspect WhatsApp connections, groups, message delivery, schedules and webhooks in a ChatRail workspace.

What you can do
  • List and inspect WhatsApp connections with their state, health and recent state history
  • Look up groups visible to a connected number, including name, description, settings and member counts
  • Review recent messages, delivery timelines and structured explanations of why a message failed
  • List scheduled messages and recent webhook deliveries with their outcomes
  • Reschedule or cancel scheduled messages, set or remove emoji reactions, and replay dead or skipped webhook deliveries, each with a preview before applying
When to use it
Useful when you already run a ChatRail workspace and want to debug WhatsApp delivery problems, check connection health, review groups and schedules, or requeue webhook deliveries from your editor instead of the dashboard.
Requirements
A remote MCP endpoint with OAuth sign-in approved by a workspace owner, admin or developer, or the local npm package chatrail-mcp run with npx or Docker using a workspace API key in CHATRAIL_API_KEY (mcp:read, optionally mcp:write). MCP access is included on the Core + AI and Team plans.
Before you install
The server operates a workspace and cannot send messages. Write tools (reschedule, cancel, react, replay) change state; they preview first and apply only when called again with confirm: true, and need an API key with mcp:write. The API key is a workspace credential, so keep it out of shared configs. Calls are scoped to one workspace and recorded in its audit log.

Installation

In SourceWeft

  1. Open ChatRail 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/dev.chatrail%2Fchatrail/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": {
    "chatrail": {
      "type": "http",
      "url": "https://www.chatrail.dev/v1/mcp"
    }
  }
}

README

ChatRail MCP server

[npm version] [npm downloads]

Operate a ChatRail workspace from Claude, Cursor, VS Code and any other Model Context Protocol client. Check the health of your WhatsApp connections, look up groups, trace why a message failed, manage scheduled messages and replay webhook deliveries without leaving your editor.

ChatRail is a WhatsApp API for developers: send and receive WhatsApp messages over HTTP from a number you already have. See the MCP documentation for the full reference.

Privacy by design

  • Message bodies, recipient phone numbers and credentials are never returned by any tool.
  • Tools that change state return a preview first and apply only when called again with confirm: true.
  • Every call is scoped to one workspace and recorded in its audit log.

Two ways to connect

1. Hosted server with OAuth (recommended)

Point any client that supports remote MCP servers at:

https://www.chatrail.dev/v1/mcp

Your client opens a browser window where a workspace owner, admin or developer approves access. Nothing to install and no key to copy.

Claude Code

bash
claude mcp add --transport http chatrail https://www.chatrail.dev/v1/mcp

Cursor (~/.cursor/mcp.json)

json
{  "mcpServers": {    "chatrail": { "url": "https://www.chatrail.dev/v1/mcp" }  }}

VS Code (.vscode/mcp.json)

json
{  "servers": {    "chatrail": { "type": "http", "url": "https://www.chatrail.dev/v1/mcp" }  }}

2. Local stdio server with an API key

For clients that only run local servers, or when you would rather use an API key. This package runs on your machine and forwards requests to the hosted server.

  1. In the ChatRail dashboard, create a workspace API key with the mcp:read scope. Add mcp:write if the assistant may reschedule, cancel, react or replay.
  2. Add the server to your client.

Claude Desktop (claude_desktop_config.json)

json
{  "mcpServers": {    "chatrail": {      "command": "npx",      "args": ["-y", "chatrail-mcp"],      "env": { "CHATRAIL_API_KEY": "cr_live_..." }    }  }}

The package is published on npm as chatrail-mcp, so npx fetches it from the registry. If you need a version that is not published yet, run it straight from the repository instead:

json
"args": ["-y", "github:chatrail/chatrail_mcp"]

Docker

bash
docker build -t chatrail-mcp .docker run -i --rm -e CHATRAIL_API_KEY=cr_live_... chatrail-mcp
VariableRequiredDescription
CHATRAIL_API_KEYYes, to call toolsWorkspace API key with mcp:read (and optionally mcp:write).
CHATRAIL_MCP_URLNoOverride the endpoint. Defaults to https://www.chatrail.dev/v1/mcp.

Without a key the server still starts and lists its tools, so you can inspect it before signing up.

Tools

ToolScopeWhat it does
list_connectionsreadEvery WhatsApp connection in the workspace with its state and health.
get_connectionreadOne connection with its state, health and recent state history.
list_whatsapp_groupsreadGroups visible to a connected number, with ids and participant counts.
get_whatsapp_groupreadName, description, settings and member counts for one group.
list_messagesreadRecent messages with their delivery state.
get_messagereadOne message and its delivery timeline.
explain_message_failurereadA structured explanation of why a message failed.
list_scheduled_messagesreadMessages waiting to be sent, soonest first.
list_webhook_deliveriesreadRecent webhook deliveries and their outcomes.
reschedule_messagewriteChange when a scheduled message is sent. Previews first.
cancel_scheduled_messagewriteCancel a message that has not been sent. Previews first.
react_to_messagewriteSet or remove an emoji reaction on a message. Previews first.
replay_webhookwriteRequeue a dead or skipped webhook delivery. Previews first.

Plans

MCP access is included on the ChatRail Core + AI and Team plans. See pricing.

Development

bash
npm installnpm run buildCHATRAIL_API_KEY=cr_test_... node dist/index.js

tools.json is the tool catalog served when no API key is configured. It is exported from the hosted server and should be refreshed when the hosted tools change.

Agent skill

ChatRail publishes a skill file that tells an agent when to use ChatRail, what a person has to set up, how to send and receive, and the rules for sending. This MCP server operates a workspace and cannot send messages, so the skill points to the REST API for sending.

Give your agent this line:

Read https://www.chatrail.dev/SKILL.md and follow it to set up ChatRail.

Or install it with the skills CLI, which installs agent skills from a GitHub repository:

bash
npx skills add chatrail/chatrail_mcp

Or copy it into Claude Code by hand:

bash
mkdir -p ~/.claude/skills/chatrailcurl -fsSL https://www.chatrail.dev/SKILL.md -o ~/.claude/skills/chatrail/SKILL.md

The canonical file is https://www.chatrail.dev/SKILL.md. A copy lives in this repository at skills/chatrail/SKILL.md so tools that install skills from GitHub can find it.

Links

License

MIT

Source: README.md at commit 73210cd

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

1
  1. v0.1.0LatestSep 25, 2026

Score

85% 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
  • License10 pts