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.
Add a reliable publish step to any pipeline
We handle delivery, retries, and status.
Claude Code skill, n8n node, or raw HTTP — Postproxy sits at the publish step and makes sure posts reach their destination, whatever triggered them upstream.
The publish step always surprises
Looks trivial from the outside. Then a platform starts rate-limiting, a token expires mid-run, and someone is debugging delivery 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 status back
A trigger fires and moves on. Without delivery events, the workflow has no idea whether the post went out — debugging becomes log spelunking after the fact.
We own the hard parts
Postproxy handles everything between your trigger and a confirmed delivery — 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.
Status webhooks
Delivery events come back to your endpoint as webhooks. Your workflow knows exactly what happened — no polling.
Rate limit handling
Per-platform rate limits are tracked and respected on our side. Your trigger just calls once and Postproxy queues intelligently.
One node for every platform
One HTTP call, one n8n node, one MCP tool — it fans out to Instagram, LinkedIn, TikTok, and the rest. No separate node per network.
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.
Error surfacing
Structured error codes per platform make failures actionable. No more guessing which network rejected a post and why.
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 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 a publish tool
The Postproxy MCP server exposes a single publish_post tool.
Your agent calls it, we handle the rest — 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
- Structured delivery 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 ends with a social post, Postproxy can own that step. These are typical patterns — not a closed list.
AI content generators
Claude, GPT, or any LLM pipeline produces copy and assets — Postproxy is the last step that gets it out to the networks without extra tooling.
No-code workflow builders
n8n, Make, or Zapier flows call one HTTP node. Postproxy handles the platform-specific complexity so the workflow stays clean.
Scheduled batch publishers
Cron jobs and batch scripts publish at volume without worrying about rate limits, retries, or per-platform token management.
Event-triggered pipelines
CMS publish hooks, repository events, or any webhook trigger can fan out to social channels as a side effect — zero manual steps.
Ship the publish step. Not the project around it.
One API call from any trigger — Postproxy handles delivery to every network.