Setup
Connect the hosted MCP server with OAuth, or run the npm package locally.
There are two ways to connect: the hosted server (no install, OAuth
sign-in) or the @xreplyai/mcp npm package (runs locally, authenticates
with an API key).
Hosted server (no install)
XreplyAI hosts the MCP server over streamable HTTP with OAuth, so there is no local process and no long-lived token to paste. Point any MCP client that supports remote servers at:
https://mcp.xreplyai.com/mcpAuthentication is OAuth 2.1; your client walks you through sign-in on first connect. In Claude, add it as a custom connector using that URL (the endpoint itself is for MCP clients, not browsers). The same paid-plan requirement applies.
npm package
Requires Node.js 20+ and an API key: sign in to XreplyAI, go to Settings → API Keys, and create one.
claude mcp add xreply -e XREPLY_TOKEN=your-api-key-here -- npx @xreplyai/mcp@0.16.0Then run claude mcp list to confirm it's registered. Or add manually to
~/.claude/mcp.json:
{
"mcpServers": {
"xreply": {
"command": "npx",
"args": ["@xreplyai/mcp@0.16.0"],
"env": { "XREPLY_TOKEN": "your-api-key-here" }
}
}
}Environment variables
| Variable | Required | Default | Description |
|---|---|---|---|
XREPLY_TOKEN | Yes | (none) | Your XreplyAI API key |
XREPLY_POSTHOG_KEY | No | public project key | Usage-analytics key. Set to an empty string (XREPLY_POSTHOG_KEY="") to disable analytics entirely |
Each tool call emits a fire-and-forget usage event (tool name, server version, duration, and error flag; never argument values). It never blocks or fails the tool response.