Hey!

We’ve shipped a remote MCP server for Postproxy.

This makes Postproxy directly usable from MCP-compatible tools and AI agents — without running any local services or adapters. Instead of wiring publishing logic yourself, you can treat Postproxy as a remote tool that executes publish actions on your behalf.

Why this matters:
More and more automation setups are moving toward agent-driven workflows. In those setups, content is generated, reviewed, and approved upstream, while publishing should be a reliable, well-defined execution step. The MCP server turns Postproxy into exactly that: a remote publishing surface that agents can call when it’s time to go live.

What this enables in practice:

• Use Postproxy from MCP-compatible environments (for example, AI coding and automation tools)

• Delegate publishing to a remote service instead of running local bridges

• Keep the same Postproxy contract underneath: platform-specific constraints, retries, partial failures, and final publish outcomes are still handled by us

The MCP endpoint is designed to work well in automation and agent-based systems where you want a clean separation between content decisions and publishing execution.

You can find documentation, examples, and connection details here:
https://postproxy.dev/automation/mcp/

We also wrote a longer post explaining the motivation behind the MCP server and how it fits into Postproxy’s role as a stable publishing layer for automation and AI-driven systems. That’s available in the blog if you want the deeper context.

Cheers,
Dmitry