Remote MCP authentication
The remote MCP server is available at https://app.replynodes.com/api/mcp and uses an Authorization: Bearer header. The MCP OAuth endpoint is /api/mcp-oauth.
Security & trust
Know which authentication path you are using.
ReplyNodes documents separate authentication paths for remote MCP and the REST Public API. This page keeps those boundaries visible and avoids claims that are not verified in the product facts source.
Documented boundary
Remote MCP
Bearer authentication at /api/mcp
REST Public API
Raw API key authentication at /api/public/v1
Use the authentication format documented for the path you selected.
The boundary
Authentication should be specific, not implied.
REST API authentication
The Public API base is https://app.replynodes.com/api/public/v1. REST requests use the raw API key in the Authorization header; do not add the Bearer prefix.
Keys have a documented home
Create API keys from app.replynodes.com → Developers → API Keys & Agents. Review the current documentation before connecting a client or application.
Supported client paths
Connect through a documented route.
The verified client list distinguishes MCP connections from ChatGPT’s GPT Actions path.
Claude
Cursor
Codex
OpenClaw
Hermes
ChatGPT via GPT Actions
Explicit limits
Trust starts with claims we can support.
ReplyNodes does not claim SOC 2, ISO 27001, an independent security audit or certification, shipped SSO/SAML, shipped audit logs, or an open-source self-hostable edition. Those claims are not verified in the canonical product facts source.
For current behavior and setup details, use the documentation and the controls available in your workspace. Do not share passwords or API keys in agent conversations.
Need to review a connection?
Start with the documented authentication path and contact the team with questions about your use case.