ReplyNodes fits into your existing stack. Connect your agents, automation platforms, and custom tools.
Connect Hermes, OpenClaw, Claude Code, or Codex through our standardized MCP server, or ChatGPT via a GPT Action. Your agent discovers and reads public web, social, app-store, and community data through one read-only gateway.
Call the read-only REST API from an n8n workflow to fetch public web, social, app-store, and community data using an HTTP Request node and your workspace Read API key.
Call the read-only REST API from a Make.com scenario to bring public data into your automations. No write or publishing actions are exposed.
Call the read-only REST API from a Zap to bring public data into over 6000 apps. No write or publishing actions are exposed.
Build your own integration with the public REST API using documented authentication and workflow guidance.
Use this crawlable reference to choose the right client, protocol, endpoint, authentication, and setup guide.
ReplyNodes is read-only public data at https://api.replynodes.com. The preferred remote MCP endpoint is https://mcp.replynodes.com/mcp. Native MCP OAuth uses https://auth.replynodes.com with mcp:read; headless/manual clients use an rn_test_ or rn_live_ API key. No write or mutation tools are exposed.
| Client | Protocol | Endpoint | Auth | Setup |
|---|---|---|---|---|
| Claude Code, Codex, Claude, Hermes, OpenClaw | Remote MCP | https://mcp.replynodes.com/mcp | OAuth mcp:read or rn_test_/rn_live_ Bearer key | MCP config → |
| Applications and GPT Actions | REST API | https://api.replynodes.com | Authorization: Bearer $REPLYNODES_API_KEY | REST quickstart → |
Each MCP-capable agent has its own setup guide with a concrete workflow example: