Claude connector
Add the URL as a custom connector, then sign in to Postqued.
One remote MCP server for Claude, ChatGPT, Cursor and any MCP client. Publish to 10 networks with the same permissions as your team.
list_workspaceslist_accountsstart_content_uploadcomplete_content_uploadpublish_contentafter approval
Meet the Dew Serum. Three weeks of testing, one very glowy result. Link in bio.
Sign in with OAuth where your client supports it, or use an organization-bound API key.
Get API keyAdd the URL as a custom connector, then sign in to Postqued.
$ claude mcp add --transport http postqued https://mcp.postqued.com/mcp \
-H "Authorization: Bearer pq_your_api_key"
$ ▍Register the remote server from your terminal.
{
"mcpServers": {
"postqued": {
"type": "http",
"url": "https://mcp.postqued.com/mcp",
"headers": {
"Authorization": "Bearer pq_your_api_key"
}
}
}
}The same HTTP server config, with your API key in the Authorization header.
Agents work inside the organization, workspace and role limits you already set. Route work through approvals to decide what goes live.
Explicit workspace boundaries keep one client's work out of another's.
Approval changes run revision and version checks before anything moves forward.
Work an agent prepares stays visible, so you can change, reschedule, cancel or approve it.
Two questions matter: does it publish or only draft, and does it cover the networks you post to?
Remote MCP server inside a full scheduler with approvals and client workspaces.
Teams and agencies publishing to 10 networks with approvals.
Open-source scheduler whose MCP server schedules and publishes to 30+ platforms, with OAuth sign-in.
Self-hosting and a larger platform catalog.
Official Buffer MCP server to draft and schedule posts and check what is coming up from Claude or ChatGPT.
Existing Buffer users who want to add an agent.
Social posting API with a documented MCP server and tool catalog.
Developers building posting into their own product.
Connects Claude, ChatGPT and Cursor to about 9,000 apps with managed authentication.
Reaching a scheduler you already use through one connector.
Choose Postqued for publishing, approvals and client workspaces on one plan. Choose Postiz to self-host, Ayrshare to build posting into your own product.
From each vendor's own MCP page, checked 30 September 2026. Confirm current details there.Setup, plans and approvals, answered plainly.
Yes. Add https://mcp.postqued.com/mcp to Claude as a custom connector and sign in, or use Claude Desktop or Claude Code with an API key. Claude can then schedule and publish to all 10 networks.
Yes. It is a standard remote MCP server, so any client that supports remote MCP can connect, including ChatGPT and Cursor. Clients that support OAuth sign in through Postqued; others use an API key. The setup above covers Claude, Claude Code, Claude Desktop and Cursor.
Not if you use approvals. Route work through Postqued's approval workflow, where posts are reviewed, changed, rescheduled, cancelled, or approved before they go live. Agents act with the same organization, workspace, and role limits as your team.
TikTok, Instagram, LinkedIn, YouTube, X, Facebook, Threads, Pinterest, Bluesky, and Mastodon. All 10 are included on every plan, and each network still has its own media and provider limits.
No. The MCP server is hosted by Postqued at mcp.postqued.com/mcp. You add the URL and either sign in or provide an API key; there is nothing to install or run.
Yes. REST API and remote MCP access are included on every paid plan, starting with Solo at $19 per month for five connected accounts. There is a 7-day free trial.
They cover the same workflow with the same permissions. The MCP server gives AI agents 62 tools they can discover and call, while the REST API is for code you write yourself. Both use Postqued's v2 API.
MCP and API on every paid plan from $19/mo. 7-day free trial.