Skip to content

OpenRouter + Postly

Manage social media with OpenRouter.

Use OpenRouter-powered agents with Postly to test models, route content and analytics tasks, create structured campaign outputs, manage drafts, and standardize publishing across connected channels.

Requires an MCP-capable agent host. Requires Postly API access and an eligible client account.

Setup reviewed October 25, 2026 · Postly Team

Connect OpenRouter to Postly

  1. Connect publishing channels in Postly and select the workspace for your assistant. Check API access in your plan.
  2. Configure Postly in the MCP host running your OpenRouter-powered agent. OpenRouter routes models; the host must execute the tools.
  3. Use https://mcp.postly.ai/openrouter. When OAuth is offered, enter your key only on the Postly authorization page. For API-key clients, use Authorization: Bearer <your-api-key> in connection settings.
  4. Start a fresh session, enable Postly tools, and verify your workspace and channels with the read-only task below.

Confirm your first successful connection

List my Postly workspaces and connected publishing channels. Show the workspace and destination names. Do not create, schedule, or publish anything.

Match the result to your intended brand. Check API activity for a successful request, then try a publishing workflow.

Copy a launch, weekly-plan, or content-reuse brief →

Publishing workflows for OpenRouter

OpenRouter gives teams flexibility across models. Postly gives that flexibility a practical marketing layer: workspace discovery, validated publishing actions, analytics access, and reusable workflows.

Route ideation, analytics, validation, and rewriting to the model best suited for each task.

Try: “Generate three model-routed campaign approaches, then create the strongest drafts in Postly.”

Generate structured JSON campaign briefs before creating Postly drafts.

Try: “Compare hook options for LinkedIn, X, Instagram, and email, then schedule the winners.”

Compare model outputs for hooks, CTAs, platform tone, and report quality.

Try: “Use structured output for a weekly analytics report and convert it into a client summary.”

Before a write action, confirm content, media, workspace, destinations, date, time, and timezone. Use team approvals where required. Keep the returned post ID and inspect its destination status; accepted or scheduled does not mean published.

Scheduled agent runs depend on your assistant’s orchestration. For recurring source-based publishing, use Auto Post. Your editor and calendar remain available throughout.

Connection and publishing help

No Postly tools appear

Check the endpoint and connection method, enable the tools, and start a fresh session. Client plans and administrator settings can affect custom MCP access.

The workspace or channel is missing

Check the allowed workspace named in the error. Use its workspace ID, switch to the correct API key, or edit Workspace access in API keys. Reconnect a channel if its provider authorization expired.

An accepted request has not published

Retrieve the Postly post ID and inspect the schedule, approval state, and destination results. Resolve the specific validation or provider error before retrying.

How do I stop the connection?

Disable the client connection and revoke its API key in Postly. Review scheduled posts separately; revoking a key does not cancel already accepted publishing work.

Guides and references