ReplyNodes

MCP

ReplyNodes runs one remote MCP server over Streamable HTTP:

https://mcp.replynodes.com/mcp

Use it from any MCP-capable client. GET /mcp serves a landing page, and POST /mcp handles MCP initialize, tools/list and tools/call.

Choose how to sign in

ClientSign in withWhy
Interactive client that supports OAuthOAuth (scope mcp:read)No key to store. The client handles the browser sign-in
Headless agent, CI, or a client without OAuthAPI key as a Bearer headerWorks anywhere you can set a header

No organization id is needed in either case. ReplyNodes resolves the organization from the signed-in identity or the key, and enforces credits, entitlements and metering. Every MCP tool call needs a key or OAuth token, including tools whose names start with anonymous_: that prefix names the REST route and does not make MCP anonymous.

Need a key? Create one on the API keys page, or use the agent flow if you have no human at the keyboard.

Set up your client

Client config formats change, so check your client's MCP documentation if a snippet no longer works. Replace the placeholder with a key from your secret store, and never commit a real key.

Claude Code

OAuth:

claude mcp add --transport http replynodes https://mcp.replynodes.com/mcp

API key:

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

Cursor

Add this to .cursor/mcp.json. Cursor expands ${env:NAME} from your environment.

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

VS Code

Add this to .vscode/mcp.json. VS Code asks for the key once and stores it securely.

{
  "servers": {
    "replynodes": {
      "type": "http",
      "url": "https://mcp.replynodes.com/mcp",
      "headers": { "Authorization": "Bearer ${input:replynodes-key}" }
    }
  },
  "inputs": [
    { "type": "promptString", "id": "replynodes-key", "description": "ReplyNodes API key", "password": true }
  ]
}

Codex

Add this to ~/.codex/config.toml. Codex reads the key from the named environment variable.

[mcp_servers.replynodes]
url = "https://mcp.replynodes.com/mcp"
bearer_token_env_var = "REPLYNODES_API_KEY"

Other clients

Use your client's equivalent of a remote Streamable HTTP server with this URL, and add the header Authorization: Bearer ${REPLYNODES_API_KEY} when you use a key. The same URL works for Hermes and OpenCode.

Verify the connection

  1. Run initialize and tools/list through your client, or by hand:

    curl -sS https://mcp.replynodes.com/mcp \
      -H "Authorization: Bearer ${REPLYNODES_API_KEY}" \
      -H "Content-Type: application/json" \
      -H "Accept: application/json, text/event-stream" \
      -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
  2. Call one read-only tool. get_fetcher_readyz takes no arguments:

    curl -sS https://mcp.replynodes.com/mcp \
      -H "Authorization: Bearer ${REPLYNODES_API_KEY}" \
      -H "Content-Type: application/json" \
      -H "Accept: application/json, text/event-stream" \
      -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_fetcher_readyz","arguments":{}}}'

An unauthenticated request cannot run a tool.

Tools

The tool catalog is generated from the runtime capability contract, so tools/list is the live source of tool names and arguments. Provider tool arguments map to the read-only REST GET operations in the API reference, and the gateway stays the authority for authentication, entitlement, credits and rate limits.

GroupWhat it covers
WebScrape, map, crawl and brand extraction; web search
SourcesReddit, YouTube, Hacker News, Apple App Store, Google Play
BrandRetrieve, search, styleguide, fonts and logo
Researchanonymous_company_research, anonymous_competitor_research
Jobs and companiesJob search, hiring signals, company search
Company Changesget_company_events, get_company_history, get_recent_company_events, get_company_intelligence (read only)
Monitorsmonitor_list, monitor_get, monitor_changes, monitor_runs (read), monitor_create, monitor_update (write)
Discoveryget_fetcher_readyz

The capability groups can change with the gateway contract, so read tools/list before you rely on a particular tool.

Monitor tools and credentials

  • OAuth (mcp:read) covers the four Company Changes read tools and the monitor read tools.
  • The write tools monitor_create and monitor_update need monitors:write. OAuth never grants it, and API-key issuance of the monitor scopes is pending. Until it ships, a write tool returns 403 forbidden_scope. This is expected behavior and not a transient error.
  • Monitor HTTP calls are rate-limited per organization. An exhausted window returns 429 rate_limited with Retry-After.
  • If a deployment does not have monitor integration configured, only monitor calls fail with monitor_api_misconfigured. Provider tools keep working.

Credits

MCP calls use the same prepaid credits as the REST API. Packages and limits are on Limits and pricing. A client cannot set or override a price.

Troubleshooting

StatusLikely causeFix
401OAuth was not completed, or the key is missing or invalidComplete the OAuth sign-in, or check the Authorization header
403A write tool without monitors:writeExpected for OAuth and for API keys until issuance ships. See Authentication
404Wrong URLUse exactly https://mcp.replynodes.com/mcp
400Invalid JSON-RPC requestCheck the protocol version, tool name and arguments
429Rate limitHonor Retry-After and reduce concurrency
503A dependency is degradedRetry after Retry-After. See Errors

On this page