ChatGPT
- Protocol
- GPT Actions
- Endpoint
- https://app.replynodes.com/api/public/v1
- Authentication
- Raw API key in Authorization (no Bearer), or pos_ OAuth app token
- Setup
- ChatGPT setup →
API Reference
Build on ReplyNodes with our public REST API and documented connection workflows.
Technical details: integration evidence
ChatGPT uses GPT Actions calling the REST API. It is not an MCP client. MCP clients use the remote MCP server. API keys are created in the app at Developers → API Keys & Agents (/developers).
Claude, Claude Code, Cursor, Codex, OpenClaw, Hermes
- Protocol
- Remote MCP
- Endpoint
- https://app.replynodes.com/api/mcp
- Authentication
- Authorization: Bearer *** key, or MCP OAuth
- Setup
- MCP setup →
Applications and workflow tools
- Protocol
- REST API
- Endpoint
- https://app.replynodes.com/api/public/v1
- Authentication
- Raw API key in Authorization (no Bearer), or pos_ OAuth app token
- Setup
- REST API setup →
Authentication
Use a raw API key in the Authorization header (no Bearer prefix), or an OAuth app token prefixed with pos_. Create API keys at Developers → API Keys & Agents (/developers).
Posts
Create, read, update, and delete posts programmatically. Draft, schedule, and publish across any connected channel.
Channels
Manage connected social channels — add, remove, and check connection status.
Workflow guidance
Consult the current public API documentation for supported endpoints and usage guidance.
For the full story on how our MCP server and REST API fit together, see building an MCP server for social publishing.
Verified OpenAPI publication status → No speculative schema is published while the authoritative backend export is unavailable.