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 →
The ReplyNodes MCP server gives AI agents standardized tools for social publishing: schedule and publish posts, manage channels and groups, generate and upload media, and run approval-aware workflows — all through the Model Context Protocol.
ReplyNodes is social media infrastructure for AI agents and applications. One remote MCP server at app.replynodes.com/api/mcp works across every connected social network, so agents don't need a separate integration per platform.
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).
Point Claude Code, Cursor, Codex, VS Code, or another MCP-capable client at the remote server with your API key — or use the @replynodes/mcp bridge for stdio-only clients.
The agent calls integrationList and groupList to see connected social accounts and groups before doing anything else.
The agent drafts and validates content against the channel's integrationSchema, schedules or publishes with integrationSchedulePostTool, and runs integration actions with triggerTool — all under your approval rules.
| Tool | What it does |
|---|---|
| integrationList | List all connected social media integrations |
| groupList | List integration groups (channels) |
| integrationSchema | Get a channel's post rules and required fields before scheduling |
| integrationSchedulePostTool | Schedule or publish posts to specific integrations with timing and content |
| triggerTool | Execute integration-specific actions and triggers |
| generateImageTool | Generate AI images |
| generateVideoTool | Generate AI videos from scripts |
| generateVideoOptions | Get available video generation options |
| videoFunctionTool | Call specific video manipulation functions |
| uploadFromUrlTool | Upload media files from URLs |
Tool availability depends on your connected integrations.
The MCP server authenticates requests with a ReplyNodes API key as a Bearer token, or through MCP OAuth (endpoint: app.replynodes.com/api/mcp-oauth). The key grants access to your ReplyNodes organization and is only sent to app.replynodes.com — it is not transmitted anywhere else. Manage keys under the Developers page in the app (API Keys & Agents).
It's a Model Context Protocol server that exposes social publishing as tools an AI agent can call. ReplyNodes' MCP server provides tools for scheduling posts, managing connected channels, generating media, and running integration actions — so any MCP-capable agent can publish to social networks through one interface.
Any client that supports remote MCP servers, such as Claude Code, Claude.ai custom connectors, Cursor, VS Code with Copilot, and Codex. Clients that only support local (stdio) MCP servers can use the @replynodes/mcp bridge package, which forwards to the same remote server.
ReplyNodes supports approval-aware workflows. You can configure posts to require human approval before publishing, or allow auto-publish per channel — the agent schedules, and your approval rules decide what goes live.
Log in at app.replynodes.com, go to the Developers page in the app (API Keys & Agents), and create a key. The key is sent as a Bearer token only to app.replynodes.com — treat it like a password and rotate it if it leaks.
Get started: read the MCP integration guide, install the @replynodes/mcp bridge, or open ReplyNodes, or use the social media API for AI agents.