Social media MCP server for AI agents

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.

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).

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

Claude, Claude Code, Cursor, Codex, OpenClaw, Hermes

Protocol
Remote MCP
Endpoint
https://app.replynodes.com/api/mcp
Authentication
Authorization: Bearer *** key, or MCP OAuth

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

How it works

1

Connect your MCP client

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.

2

Agent discovers your channels

The agent calls integrationList and groupList to see connected social accounts and groups before doing anything else.

3

Schedule, publish, and trigger

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.

MCP tools

ToolWhat it does
integrationListList all connected social media integrations
groupListList integration groups (channels)
integrationSchemaGet a channel's post rules and required fields before scheduling
integrationSchedulePostToolSchedule or publish posts to specific integrations with timing and content
triggerToolExecute integration-specific actions and triggers
generateImageToolGenerate AI images
generateVideoToolGenerate AI videos from scripts
generateVideoOptionsGet available video generation options
videoFunctionToolCall specific video manipulation functions
uploadFromUrlToolUpload media files from URLs

Tool availability depends on your connected integrations.

Security and authentication

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).

Frequently asked questions

What is a social media MCP server?

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.

Which clients can connect to the ReplyNodes MCP server?

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.

Can the MCP server publish without human approval?

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.

How do I get an API key for the MCP server?

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.