The social publishing layer for AI agents

Connect Postproxy once, and any MCP-aware agent can publish and schedule across 11 platforms. It can also reply to comments and DMs where the platform supports them. Works with Claude, ChatGPT, Cursor, Codex, Hermes, and OpenClaw. Your credentials stay with you.

Using an AI agent? Copy a setup prompt and it connects over MCP.

Get started Read the MCP docs

Free plan No credit card Live in under 5 minutes

Start here

Find your setup

Pick where your agent already lives. Each path is one connection, then plain-language publishing — the agent calls Postproxy while your credentials stay server-side.

claude mcp add Claude One claude mcp add, or connect from the Claude directory in a click. Set up Claude →

Developer mode ChatGPT Turn on Developer mode, add the plugin URL, and sign in. Set up ChatGPT →

.cursor/mcp.json Cursor One block in .cursor/mcp.json, committed with the repo. Set up Cursor →

~/.codex/config.toml Codex One entry in ~/.codex/config.toml, shared by every Codex session. Set up Codex →

skill + API key Hermes Install the skill, drop in one API key, publish from any chat. Set up Hermes →

ClawHub skill OpenClaw Install the skill from ClawHub; every routed channel gets the tools. Set up OpenClaw →

MCP The protocol behind it all — hosted endpoint or local npm package. https://mcp.postproxy.dev/mcp MCP docs →

How it works

Three steps from agent to published

The same flow for every client. Connect once, approve access, then ask in plain language.

Point your client at the MCP endpoint

Register `https://mcp.postproxy.dev/mcp` in your agent — one command, one config block, or one click in a connector directory.

Authorize with your Postproxy account

Sign in over OAuth or drop in an API key. Platform credentials stay in Postproxy, so the agent works with tools while tokens stay server-side.

Ask for what you want, in plain language

"Schedule Thursday's launch post to X and LinkedIn." The agent calls the tools; Postproxy handles formatting, media, rate limits, retries, and reports back.

Under the hood

We own the hard parts

Your agent focuses on what to say. Postproxy handles delivery, feedback, and every platform's quirks behind one stable contract.

Delivery & retries

Automatic retries with back-off on every publish, so a transient platform failure recovers on its own instead of dropping your post

Events back to your agent

Delivery status, incoming comments, DMs, and reviews come back as structured results. The agent knows what actually happened

Rate limits handled

Per-platform limits are tracked on our side. Your agent calls once and Postproxy queues intelligently

Insights on demand

Pull post and follower stats back after publishing, normalized across networks, ready for the next decision

Platform changes absorbed

When Instagram, LinkedIn, or TikTok shift their API, we absorb it. Your agent keeps working while we adapt

Credentials stay server-side

One OAuth sign-in or API key connects everything, and platform tokens stay server-side

For agents

Built for agentic workflows.

We know your stack: MCP, skills, n8n, Make. We're built to fit right in and keep publishing smooth.

Give your agent everything it needs to publish and respond to social content from your project.

npx skills add postproxy/postproxy-skill

MCP server

Postproxy MCP server lets Claude, Cursor, and other MCP clients publish to social media directly. Add the server and start posting, zero configuration.

Read the MCP docs

Cursor and IDE skills

Install the Postproxy skill to give your AI assistant publishing capabilities. One command to add, then publish from your project without leaving the editor.

Get started

n8n, Zapier, Make, and more

Connect Postproxy to n8n, Zapier, Make, or any workflow tool. Schedule posts, trigger on events, or let your automations decide when and what to publish.