Delivery is not fire-and-forget
Social APIs fail silently, rate-limit unexpectedly, and each platform speaks a different error dialect. You only find out something went wrong when someone notices the post is missing.
Connect any pipeline to the full social API
Publish out. Pull insights back. React to comments, DMs, and reviews.
Claude Code skill, n8n node, or raw HTTP. Postproxy handles delivery, retries, rate limits, and incoming events so your pipeline stays focused on what it actually does.
Social APIs always surprise
Looks trivial from the outside. Then a platform starts rate-limiting, a token expires mid-run, a comment event never arrives, and someone is debugging at midnight instead of shipping the next feature.
Retry logic is a project, not a line
Back-off, per-platform quotas, dead-letter handling. Getting it right takes longer than the feature that needed it.
Async pipelines need data back
A trigger fires and moves on. Without delivery events, insight data, and incoming comment or DM webhooks, the workflow is blind to what actually happened downstream.
We own the hard parts
Postproxy handles publishing, insights, and incoming events (comments, DMs, reviews) across every platform, so your pipeline stays focused on what it actually does.
Delivery & retries
Automatic retries with back-off on every publish attempt. Posts don't silently disappear when a platform hiccups.
Delivery & event webhooks
Delivery status, incoming comments, DMs, and review events come back to your endpoint. Your workflow knows exactly what happened, no polling.
Rate limit handling
Per-platform rate limits are tracked and respected on our side. Your trigger calls once and Postproxy queues intelligently.
Insights & analytics back into your pipeline
Pull post performance data back after publishing. One endpoint, normalised across networks, ready to feed downstream steps or dashboards.
Platform changes don't break your workflow
When Instagram, LinkedIn, or TikTok updates their API, we absorb it. Your n8n flow or Claude skill keeps working without a fix on your end.
Comments, DMs, and reviews as pipeline triggers
Incoming comments, direct messages, and platform reviews arrive as structured webhook events. Route, classify, or respond to them from any automation tool.
FOR AGENTS
Built for agentic workflows.
We know your stack: MCP, skills, n8n, Make, Needle. 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
Postproxy MCP server lets Claude, Cursor, and other MCP clients publish to social media directly. Add the server and start posting — zero configuration.
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.
Agentic workflows
Connect Postproxy to n8n, Zapier, Make, Needle, or any workflow tool. Schedule posts, trigger on events, or let your automations decide when and what to publish.
INFRASTRUCTURE
Serious about where your data lives.
Postproxy runs on European infrastructure, handles credentials the way you'd want your own handled, and is GDPR-compliant without you having to think about it.
SECURITY
Security at core.
Your data is protected by enterprise-grade encryption, secure APIs, and strict access controls designed to keep everything safe.
HOSTING
Europe hosted.
All data is stored and processed on European servers, ensuring sovereignty, reliability, and compliance with local regulations.
COMPLIANCE
GDPR-compliant.
Built to meet Europe's highest privacy standards, Postproxy processes and stores data with full compliance and transparency.
Give your agent the full social toolkit
The Postproxy MCP server exposes tools for publishing, reading insights, fetching comments and DMs, and pulling reviews. Your agent calls them; we handle platform routing, retries, token lifecycle, and delivery confirmation.
One command to connect
claude mcp add --transport http postproxy \
https://mcp.postproxy.dev/mcp?api_key=YOUR_KEY- Works with Claude Code, Cursor, and any MCP-compatible host
- No token management inside the agent: credentials stay server-side
- Publish posts, pull insights, read comments, DMs, and reviews from the same connection
- Structured delivery and event feedback so the agent knows what happened
MCP
Publishing for AI agents
n8n
Self-hosted workflow automation
Needle
AI-powered knowledge workflows
Make
Coming SoonVisual automation platform
Zapier
No-code automation
Common automation shapes
If your pipeline touches social in any direction, Postproxy can own that layer. These are typical patterns, not a closed list.
AI content generators
LLM pipeline produces copy and assets, Postproxy publishes it. Insights flow back to close the loop: what performed, what to generate next.
No-code workflow builders
n8n, Make, or Zapier flows call one HTTP node to publish, pull analytics, or react to incoming comments and DMs. Postproxy handles the platform complexity.
Scheduled batch publishers
Cron jobs and batch scripts publish at volume without managing rate limits or tokens. After publishing, pull insights back in the same run.
Event-triggered pipelines
CMS hooks or repository events fan out to social as a side effect. Incoming comments, DMs, and reviews trigger downstream steps: routing, classification, auto-reply.
Ship the social API step. Not the project around it.
One integration from any trigger: publish out, pull insights back, receive comments, DMs, and reviews as events.