Introduction

AI assistants in your editor can draft copy, summarize notes, and answer questions — but until now, turning that into a scheduled social post still meant switching to a browser, logging into Posttely, and clicking through the composer. Posttely MCP closes that gap.

MCP (Model Context Protocol) is the open standard that lets tools like Cursor and Claude talk to external services securely. Posttely now hosts a production MCP server so you can list workspaces, check channels, schedule posts, and generate captions from the same place you already work.

What Is Posttely MCP?

Posttely MCP is a hosted Streamable HTTP server at https://www.posttely.com/mcp. Once your client is authenticated, it exposes a fixed set of tools that map to real Posttely account actions — not a read-only demo.

It is built for:

• Developers and founders who live in Cursor or Claude Desktop
• Social teams who want assistants to draft and queue content with guardrails
• Power users who prefer natural language over clicking through every screen

Secure Sign-In (No Password in Config)

Posttely MCP uses OAuth 2.1 with PKCE, the same pattern modern apps use for “Sign in with…” flows. In Cursor you click Authenticate, sign in on the Posttely website (including 2FA or passkeys if you use them), and approve access on a consent screen.

Your password never goes into mcp.json or chat logs. Tokens are scoped to Posttely MCP, rotate on refresh, and can be revoked from the client or with the auth_logout tool.

What You Can Do With the Tools

The server currently exposes 11 tools, including:

• list_workspaces and activate_workspace — see and switch the workspace your channels belong to
• list_channels — connected networks and quota for the active workspace
• create_post — publish now or save a draft to selected channels
• schedule_post — pick a time, timezone, or add to your queue
• list_queue, list_recent_posts, and list_calendar — what is coming up and what went out
• generate_caption — AI-assisted copy using your Posttely allowance
• auth_me and auth_logout — check who is connected or end the session

Publishing and scheduling still respect your channel permissions and plan limits — the assistant is a interface, not a bypass.

How to Connect Cursor

1. Read the step-by-step guide at www.posttely.com/mcp-setup
2. Add a remote MCP server with URL https://www.posttely.com/mcp (with or without a trailing slash — both work)
3. Click Authenticate in MCP settings and complete login on Posttely
4. Approve the consent screen for Posttely MCP access
5. In chat, ask your assistant to list workspaces or schedule a post — it will call the tools automatically

Other MCP clients that support OAuth discovery and Streamable HTTP can use the same endpoint; the setup page includes notes for Claude, Gemini CLI, and generic clients.

Why This Matters for Your Workflow

Scheduling from an assistant is not about removing human judgment — it is about fewer context switches. You can paste a draft, ask for a caption tweak, confirm channels, and queue for Tuesday morning without leaving the editor.

Because authentication is standard OAuth, enterprise-friendly clients that refuse custom password tools can still connect. Posttely continues to improve the server (protocol version, discovery URLs, and tool coverage) on the same endpoint you configure once.

Get Started Today

Connect Posttely MCP in Cursor, authenticate once, and try: “List my Posttely workspaces” or “What is in my posting queue?” When you are ready to ship, ask your assistant to draft and schedule — you stay in control of every publish.

Setup guide: https://www.posttely.com/mcp-setup
What’s New: https://www.posttely.com/whats-new/