Everything you need to integrate ReplyNodes with your agents and workflows.
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 → |
Connect any MCP-capable agent to ReplyNodes in minutes.
Full API documentation for building on ReplyNodes. See the API reference for verified base URL and authentication facts.
The OpenAPI 3.0.3 document (v1) is published in machine-readable form and as an interactive reference. See where to fetch it and how it relates to the gateway capabilities document.
Connect verified MCP clients with the remote server and Bearer API-key authentication.
Review the documentation for current supported agent and API workflows.
Call the read-only REST API from an n8n workflow to fetch public data.
Call the read-only REST API from a Zap to fetch public data.
Building your own client? Read the current web-context implementation guide for the design decisions behind it.