Model Context Protocol

MCP server

One remote MCP endpoint gives any MCP client — Claude Desktop, Claude Code, Cursor, Codex, OpenClaw, Hermes — the same provider data tools as the REST API. No SDK, no generated client. Add one config block.

Endpoint

https://api.replynodes.com/mcp   (Streamable HTTP)

The server is remote — nothing to install for clients with native remote-MCP support. For stdio-only clients, use the thin bridge package:

npm install @replynodes/mcp     # forwards stdio → remote, authenticates with your key

Authentication

Pass your ReplyNodes API key as a connection header. The same rn_live_... key works for both REST and MCP — usage meters into the same workspace.

Tools

Tool	Cost	What it does
search_endpoints	free	Find provider operations by keyword across every live route.
describe_endpoint	free	Full parameter and response schema for one operation.
check_balance / usage	free	Current quota and usage for your key.
x_user_posts	metered	Public posts by an X handle (normalized post page).
x_post	metered	A single public X post by ID.
appstore_search / appstore_app / appstore_similar	metered	Google Play search, app lookup, related apps.
youtube_* / tiktok_* / reddit_*	metered	Enabled per provider as adapters ship.

Free discovery tools let an agent explore the API before spending anything — the pattern proven by fetcher.sh's MCP surface: agents that can describe endpoints themselves integrate faster and make fewer malformed calls.

Setup examples

Claude Code / CLI clients

claude mcp add replynodes --transport http \
  https://api.replynodes.com/mcp \
  --header "Authorization: Bearer $REPLYNODES_API_KEY"

Claude Desktop / Cursor (JSON config)

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

stdio-only clients (bridge)

npx @replynodes/mcp   # set REPLYNODES_API_KEY in the environment

MCP vs REST

	REST API	MCP
Best for	Production agent runtimes, high volume, typed clients	Interactive assistants, exploration, quick integration
Auth	Bearer key per request	Key in connection header, once
Discovery	/capabilities endpoints + OpenAPI	Built-in free search/describe tools
Pricing	Same metering — one workspace, one usage ledger