ReplyNodes for ChatGPT and Codex
ChatGPT uses GPT Actions with the ReplyNodes public REST API. Codex uses the ReplyNodes remote MCP server to schedule posts, inspect connected channels, and generate media through standardized MCP tools.
ReplyNodes is social media infrastructure for AI agents and applications. These are separate client paths: GPT Actions→REST for ChatGPT, and remote MCP for Codex.
How it works
Choose the client path
Configure a GPT Action for ChatGPT to call https://app.replynodes.com/api/public/v1, or point Codex at the remote MCP server at https://app.replynodes.com/api/mcp.
Agent inspects your setup
Using integrationList and groupList, the agent sees which social accounts are connected and where it can publish.
Schedule and publish
The agent drafts, validates against the integrationSchema, and schedules or publishes through integrationSchedulePostTool — with approval workflows when you want them.
What the agents can do
Schedule posts across networks
integrationSchedulePostTool schedules or publishes to one or more connected integrations, so a single agent can manage LinkedIn, X, and 30+ networks from one conversation.
Manage channels and groups
integrationList and groupList expose connected accounts and groups; triggerTool runs integration-specific actions once the required fields are known.
Generate and upload media
generateImageTool, generateVideoTool, generateVideoOptions, videoFunctionTool, and uploadFromUrlTool cover image, video, and media-library workflows.
Approval-aware publishing
ReplyNodes supports approval workflows, so agent-scheduled posts can wait for human review instead of publishing instantly.
Security and authentication
ChatGPT REST requests use the raw API key in the Authorization header with no Bearer prefix (or a pos_ OAuth app token). Codex MCP requests use Authorization: Bearer API key (or MCP OAuth). API keys are managed at Developers → API Keys & Agents in the app.
Frequently asked questions
Which ChatGPT clients can use ReplyNodes?
ChatGPT connects through a supported GPT Action calling the ReplyNodes public REST API. ChatGPT Custom GPTs do not connect to the ReplyNodes MCP server directly.
How does Codex connect to ReplyNodes?
Codex connects the same way any MCP client does: add the ReplyNodes MCP server to your Codex configuration (or run the @replynodes/mcp bridge as a stdio command) with your API key. Codex can then call the same tools from interactive sessions or automated workflows.
Is there a separate integration path for ChatGPT versus Codex?
Yes — ChatGPT uses GPT Actions with the REST API, while Codex uses the remote MCP server. They are separate client paths to the same ReplyNodes capabilities.
Can ChatGPT or Codex publish without human review?
That depends on your approval settings. ReplyNodes supports approval-aware workflows, so you can require a human to approve scheduled posts before they go live, or allow auto-publish per channel.
Get started: read the MCP integration guide, or open ReplyNodes, or use the social media MCP server for AI agents.