ReplyNodes

@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 REPLYNODES_API_KEY 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 REPLYNODES_API_KEY 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 REPLYNODES_MCP_URL override below, but the canonical public endpoint remains https://mcp.replynodes.com/mcp.

Environment variables

Variable	Required	Description
REPLYNODES_API_KEY	yes	Credential from the ReplyNodes auth claim flow. Read from the environment only.
REPLYNODES_MCP_URL	no	Trusted HTTPS endpoint override. Defaults to https://mcp.replynodes.com/mcp.

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.

Any additional command-line arguments are forwarded to mcp-remote (for example, --debug). Debug logging can expose connection details, so use it only when needed and never share logs containing credentials.

Native remote MCP (no install)

A client with native remote MCP support can connect directly to:

URL: https://mcp.replynodes.com/mcp

Use the client's supported authentication flow and keep credentials out of URLs and command-line arguments.

Live tool surface

After connecting, discover the current read-only tools with a tools/list call. As of the last verification, the live endpoint exposes read-only tools across these capability families:

• web_search — public web search results
• webcontext — scrape, crawl, map, and brand extraction for one URL
• brand — brand search, retrieve, styleguide, and fonts by domain
• reddit — post lookup by id/permalink, site-wide search, subreddit listings, user activity
• youtube — video, channel, playlist, comments, transcript, search, related videos
• appstore — App Store search, list, app/developer details, ratings, reviews, similar, suggest, privacy
• googleplay — Google Play search, category browsing, app/developer details, reviews, permissions, data-safety, availability, similar, suggest
• hackernews — item lookup, search, and top/ask/show/new/job/best story listings and user profiles

The exact tool set and schemas are authoritative at runtime. Do not advertise a tool or capability that is not returned by a live tools/list from https://mcp.replynodes.com/mcp.

Cursor and other IDE ecosystems

ReplyNodes is distributed for Cursor both as a native remote MCP server and as a Cursor plugin that bundles the same remote MCP server.

Native remote MCP (no plugin)

Cursor supports remote MCP servers in mcp.json using a url plus optional headers. Add ReplyNodes to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "replynodes": {
      "url": "https://mcp.replynodes.com/mcp",
      "headers": {
        "Authorization": "Bearer ${REPLYNODES_API_KEY}"
      }
    }
  }
}

Set REPLYNODES_API_KEY in your environment. Claim a credential at https://replynodes.com/auth.md. See Cursor's MCP docs at https://cursor.com/docs/mcp and the manual install help at https://cursor.com/help/customization/mcp.

Cursor plugin (one-click + deeplink + marketplace-ready)

A Cursor plugin that wraps the same remote MCP server lives in .cursor-plugin/ in this repository:

• plugin manifest: https://github.com/replynodes/replynodes-mcp/blob/master/.cursor-plugin/plugin.json
• logo: https://github.com/replynodes/replynodes-mcp/blob/master/assets/logo.svg

The plugin uses the canonical production endpoint https://mcp.replynodes.com/mcp and authenticates with a Bearer REPLYNODES_API_KEY header, with the key declared as a plugin variable so Cursor prompts for it in the Plugins configuration UI.

Install with a Cursor deeplink

Cursor supports MCP install deeplinks of the form:

cursor://anysphere.cursor-deeplink/mcp/install?name=$NAME&config=$BASE64_ENCODED_CONFIG

The ReplyNodes deeplink (remote HTTP MCP, Bearer API key) is:

cursor://anysphere.cursor-deeplink/mcp/install?name=replynodes&config=eyJtY3BTZXJ2ZXJzIjp7InJlcGx5bm9kZXMiOnsiaGVhZGVycyI6eyJBdXRob3JpemF0aW9uIjoiQmVhcmVyICR7UkVQTFlOT0RFU19BUElfS0VZfSJ9LCJ1cmwiOiJodHRwczovL21jcC5yZXBseW5vZGVzLmNvbS9tY3AifX19

Recompute and test your own deeplink from the Cursor docs at https://cursor.com/docs/mcp/install-links.

Submit to the Cursor Marketplace

The plugin is submit-ready. To list it on the public Cursor Marketplace:

1. Confirm the plugin is on a public Git branch of https://github.com/replynodes/replynodes-mcp.
2. Sign in at https://cursor.com/marketplace/publish.
3. Submit the repository URL.

Submission checklist (from https://cursor.com/docs/reference/plugins): valid .cursor-plugin/plugin.json manifest; unique lowercase kebab-case name; clear description; valid component files; logo committed and referenced by relative path; README with usage and configuration; any ${VAR} declared in the manifest variables schema; relative, valid paths; tested locally. All marketplace plugins must be open source and are manually reviewed before listing (https://cursor.com/help/security-and-privacy/marketplace-security).

Distribution state

Channel	State	URL
Official MCP Registry	Live listing	https://registry.modelcontextprotocol.io/v0.1/servers/com.replynodes%2Fmcp/versions/latest
Smithery	Live listing	https://smithery.ai/server/@replynodes/mcp
Cursor plugin (in this repo)	Submit-ready	https://github.com/replynodes/replynodes-mcp/tree/master/.cursor-plugin
Cursor deeplink	Verified install path	cursor://anysphere.cursor-deeplink/mcp/install?name=replynodes&config=eyJtY3BTZXJ2ZXJzIjp7InJlcGx5bm9kZXMiOnsiaGVhZGVycyI6eyJBdXRob3JpemF0aW9uIjoiQmVhcmVyICR7UkVQTFlOT0RFU19BUElfS0VZfSJ9LCJ1cmwiOiJodHRwczovL21jcC5yZXBseW5vZGVzLmNvbS9tY3AifX19
Cursor Marketplace listing	Not listed yet	submit at https://cursor.com/marketplace/publish (owner action)
Claude Code plugin (in this repo)	Existing, uses stdio bridge	https://github.com/replynodes/replynodes-mcp/tree/master/.claude-plugin
Claude Code community marketplace	Submit path is owner-gated	https://code.claude.com/docs/en/plugins.md

License

MIT