Operational tools
MCP exposes focused actions such as listing connections, checking a session, inspecting delivery state, explaining a failed message, replaying a safe payload and scheduling a send.
Connect with OAuth or an API key
The hosted server is https://www.chatrail.dev/v1/mcp. MCP clients can use the built-in OAuth 2.1 flow: dynamic client registration, S256 PKCE, workspace consent and short-lived audience-bound access tokens. A dedicated API key with mcp:read and mcp:write remains available for direct server-to-server configurations.
Discovery starts at /.well-known/oauth-protected-resource/v1/mcp and /.well-known/oauth-authorization-server. See the complete authentication profile.
Not a replacement for the API
Use the HTTPS API and webhooks in production applications. MCP is an operator and developer interface for inspecting and managing the same workspace.
Controlled access
Every credential is scoped to one workspace. OAuth grants are limited to mcp:read and mcp:write; mutating tools preview first and require a second explicit confirmation. Every tool call is audited, and results are bounded so an agent cannot fill its context with an unbounded response.
Set it up from your agent
Give your agent one line: Read https://www.chatrail.dev/SKILL.md and follow it to set up ChatRail. The ChatRail skill covers when to use ChatRail, how a person creates the key and pairs the number, how to send and receive, and the rules for sending. The MCP server operates a workspace; sending goes through the REST API.