Any client

PostPublish for Any MCP client

Any client that speaks MCP can use PostPublish. Ask in plain words and it writes, checks and schedules posts to Facebook Pages, Instagram, Threads, X, LinkedIn and Telegram.

Start free trial Server and tools

Set up Any MCP client

1
Open the client's MCP or connectors settings and add a new remote (HTTP) server.
2
Set the server URL to https://postpublish.pro/api/mcp.
3
When your browser opens, sign in to PostPublish and approve access. OAuth is the recommended sign-in; no key is copied around.
4
If the client only supports local (stdio) servers, use the bridge snippet instead.

MCP config (JSON)

{
  "mcpServers": {
    "postpublish": {
      "url": "https://postpublish.pro/api/mcp"
    }
  }
}

stdio bridge (npx mcp-remote)

{
  "mcpServers": {
    "postpublish": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://postpublish.pro/api/mcp"
      ]
    }
  }
}

API-key variant

{
  "mcpServers": {
    "postpublish": {
      "url": "https://postpublish.pro/api/mcp",
      "headers": {
        "Authorization": "Bearer pp_live_YOUR_KEY"
      }
    }
  }
}

Server URL: https://postpublish.pro/api/mcp. OAuth is recommended. If your client cannot do OAuth, create an API key in PostPublish (Settings, then API keys) and send it as a Bearer token; if it only runs local servers, use the stdio bridge with npx mcp-remote.

Example prompts

“List my connected accounts, then schedule a post to all of them for tomorrow at 9:00.”
“Draft a week of posts for our Facebook Page and save them as drafts.”
“Check this caption against every network's limits.”
“Post this announcement to our Telegram channel and LinkedIn tomorrow at 10:00.”

Troubleshooting

The connector or server does not show up.

Check that the URL is exactly https://postpublish.pro/api/mcp and that your version of Any MCP client supports remote MCP servers. If it only supports local servers, use the stdio bridge (npx mcp-remote).

Sign-in loops or fails.

Make sure you can sign in to app.postpublish.pro in the same browser, and that your workspace's trial or plan is active. If it still fails, remove the connection and add it again.

A post is rejected.

Each network has limits (Threads 500 characters, Instagram 2,200, plus media rules). Ask the agent to preview first; it reports warnings before anything is created.

The agent cannot see my accounts.

Connect your Facebook Pages, Instagram, Threads, X, LinkedIn or Telegram accounts in the PostPublish app first, and check that your role or key can read and write posts.

Revoke access

Remove the PostPublish connection in Any MCP client's MCP or connectors settings.
In the PostPublish app, open Settings, then AI agents, and revoke any key you created for this client. A revoked key stops working immediately.
To end an OAuth sign-in, remove the connector in the client. Leaving the workspace ends all access for that user.

All AI agents

Any MCP client and its logo are the property of their respective owners. They are shown only to indicate compatibility; use does not imply endorsement or partnership.