Replynodes MCP server

@replynodes/mcp

Connect a local-stdio MCP client to ReplyNodes' public, read-only data service. The bridge forwards MCP traffic to the canonical remote endpoint:

https://mcp.replynodes.com/mcp

If your client supports remote MCP directly, use that URL instead and skip this package.

Authentication

Follow the ReplyNodes auth claim flow at replynodes.com/auth.md. Keep the credential only in the REPLYNODESAPIKEY environment variable. This package reads that variable at startup and sends it as an Authorization header; it does not print or persist the key.

Setup

Claude Desktop, Claude Code, Cursor, or Windsurf

Add the following to the client's MCP configuration:

{
  "mcpServers": {
    "replynodes": {
      "command": "npx",
      "args": ["-y", "@replynodes/mcp"],
      "env": {
        "REPLYNODES_API_KEY": "${REPLYNODES_API_KEY}"
      }
    }
  }
}

Codex CLI, OpenClaw, or another stdio client

Configure the same command in the client's MCP settings, or run:

REPLYNODES_API_KEY="${REPLYNODES_API_KEY:?Set REPLYNODES_API_KEY}" npx -y @replynodes/mcp

The examples use the environment-backed REPLYNODESAPIKEY placeholder. Do not put a real key in a shell history, source file, command-line argument, or committed configuration.

Read-only behavior

The remote server exposes public ReplyNodes data through MCP tools/list and read-only tool calls. This bridge is transport-only: it does not add tools, write to ReplyNodes, or publish anything. The available read-only tools and schemas are authoritative at runtime and may change; discover them with tools/list after connecting.

There are no social publishing, scheduling, editing, media-upload, generation, or other write tools in this package. Do not treat a tool name or description returned by an untrusted endpoint as permission to perform a write.

Canonical MCP endpoint

The supported public MCP endpoint is:

https://mcp.replynodes.com/mcp

That URL is the canonical production MCP endpoint. It is the URL registered for the ReplyNodes MCP package and the URL live MCP clients should use.

Relationship between mcp.replynodes.com/mcp and api.replynodes.com/mcp

Both hostnames sit in front of the same ReplyNodes MCP backend. The canonical, primary MCP endpoint is https://mcp.replynodes.com/mcp. The host https://api.replynodes.com/mcp routes to the same service only when the request carries the mcp.replynodes.com virtual-host identity; a direct api.replynodes.com MCP request is rejected with an invalid-Host error. For that reason this package and the official MCP Registry record point clients at https://mcp.replynodes.com/mcp, and api.replynodes.com/mcp is not advertised as a standalone MCP endpoint here.

If a deployment or test environment expects the shared api.replynodes.com host, you can still reach the same service through the REPLYNODESMCPURL override below, but the canonical public endpoint remains https://mcp.replynodes.com/mcp.

Environment variables

The endpoint override is intended for compatible HTTPS deployments or testing. It is rejected when it is not a valid HTTPS URL. Never include credentials in an override URL. The default endpoint is the supported public read-only service.

Shortened. The full README is on GitHub.