Cue custom MCP by URL

Schedule social posts from Cue

posterly is the publish layer. Cue is the personal agents layer (from Manus, same connector infra). Add posterly as a custom MCP by URL, then let your Cue agent draft, validate, and schedule posts across your connected social accounts. Cue is built for responsibility and routines: agents that carry ongoing work, not one-off chats. posterly is where those posts actually queue and go live.

Hero prompt

Add posterly as a custom MCP at https://www.poster.ly/api/mcp. Prefer OAuth. Then run whoami and list_accounts. Draft next week's LinkedIn posts, validate_post each, and pause for my yes before any create_post.

Get Starter + API · $10/moCreate API key
Preview what is copied
# posterly MCP brief for Cue

You are connected (or about to connect) to posterly, the publish layer. Cue is the personal agents layer (Manus infra). Schedule and publish social posts only through posterly MCP tools. Never invent account IDs, never collect passwords or card details, never publish without a clear user yes.

## Endpoint and auth

- MCP URL: https://www.poster.ly/api/mcp (www required)
- Transport: hosted HTTP MCP, JSON-RPC 2.0, single POST. No SSE. No streamable HTTP in v1.
- Auth preferred: OAuth sign-in to posterly when the client offers it for this URL.
- Auth fallback: Authorization Bearer pst_live_… from https://www.poster.ly/dashboard/api
- Connect: add as custom MCP / Add MCP by URL (one user message is enough to request this). Same server can be added in Manus Settings, Integrations, Custom MCP Servers. Not a directory listing.

## Connect check

1. Call whoami (no params). Confirm user, scopes, workspaces.
2. Call list_accounts. If empty, stop and send the user to connect social accounts in posterly.
3. Prefer validate_post before create_post. Show the preview. Wait for a clear yes.
4. Only then create_post with confirm: true.
5. Prefer scheduled_at (ISO 8601 UTC) or find_available_slot. Do not publish immediately unless the user asks.
6. Routines and recurring asks: still validate and wait for yes on each live create_post, unless the user gave an explicit standing rule for that routine in writing.

## Media (honest)

Chat attachments never reach MCP. The paperclip in this chat does not give posterly the file.

- Laptop files: create_media_drop, then send drop_url (https://www.poster.ly/drop/), then list_media with drop_session_id, then use public_url.
- Public HTTPS URL: upload_media with url, or media_url / media_urls on validate/create.
- Client can PUT: create_signed_upload, PUT to upload_url, then pass public_url to create_post.
- Hosted upload_media with base64 hits the ~4MB Vercel request body on posterly API routes. It is for small images only (relay cap 5MB decoded).

## Starter tools

whoami, list_accounts, validate_post, create_post (confirm: true), upload_media, create_signed_upload, create_media_drop, list_media, find_available_slot, generate_captions, list_posts.

Full list (59 hosted HTTP tools): https://www.poster.ly/mcp

## Platforms

Instagram, Facebook, TikTok, X, LinkedIn, YouTube, Pinterest, Threads, Google Business, Telegram, Bluesky, Discord, Slack, Mastodon, Dev.to, Hashnode, WordPress, Lemmy.

## Behaviour

- posterly is the publish layer. You are the personal agents layer.
- After create_post, send the View in posterly link. Avoid raw JSON unless debugging.
- Do not claim a verified Cue connect until transport validation has passed.
- Signup / API add-on: https://www.poster.ly/agents/signup and https://www.poster.ly/dashboard/api
- Sibling client: Manus uses the same MCP URL and Settings, Integrations path (https://www.poster.ly/manus).

Our hosted MCP is POST https://www.poster.ly/api/mcp (JSON-RPC 2.0, single POST). We do not offer SSE or streamable HTTP in v1. Eng is validating that Manus Custom MCP (the same infra Cue uses) accepts this transport before we claim a verified live connect. Until that clears, treat this page as setup guidance, not a guarantee. Cue may be early-access or invite-only. We do not invent pricing or invite mechanics here. Chat attachments never reach posterly.

What it looks like in chat

Draft, validate, then approve. Your AI never publishes until you say so.

your AI · connected to posterly MCP

Never posts without approval · validate_post before create_post

View in posterly

Works with Claude, ChatGPT, Gemini, Cursor, OpenClaw, Hermes, Grok Bot, Muse, Poke, Manus, Cue, and any MCP client.

Get Cue connected in three steps

Preferred path: one message to your Cue agent. The same server can also be added in Manus Settings, Integrations, Custom MCP Servers. We do not invent a separate Cue Settings path. This is not a directory listing.

1

Ask your Cue agent

Send one clear message: add this custom MCP server, name posterly, URL https://www.poster.ly/api/mcp. Prefer OAuth sign-in to posterly. If only Bearer or API key auth is available, you will paste a pst_live_ key from Dashboard, API and MCP.

Open API and MCP
2

Or use Manus Settings

Add the same server in Manus via Settings, Integrations, Custom MCP Servers, Add Server. Server URL https://www.poster.ly/api/mcp. Prefer OAuth when offered; otherwise Authorization Bearer pst_live_…

posterly for Manus
3

Confirm with whoami

Call whoami, then list_accounts. Prefer validate_post. Wait for a clear yes before create_post with confirm: true. If you cannot open Cue yet, start from the Manus page.

Agent signup

What to send or paste

Custom Add by URL, or the shared Manus Integrations path. Do not look for posterly inside an official Cue or Manus directory. If you cannot open Cue yet, use the Manus path.

Fields

MCP URL

https://www.poster.ly/api/mcp

www is required. Same URL as Manus. Hosted JSON-RPC 2.0, single POST. No SSE and no streamable HTTP in v1.

Preferred connect

Ask the agent to add custom MCP by URL

One user message is enough to request this. We do not document a separate Cue Settings screenshot path.

Authentication

OAuth preferred; Bearer pst_live_… fallback

Prefer OAuth when the client offers it. If only Bearer or API key auth appears, create a key at https://www.poster.ly/dashboard/api.

Message to your Cue agent

Send this once. It asks for custom MCP by URL, not a directory install.

Add this custom MCP server: name posterly, URL https://www.poster.ly/api/mcp. Prefer OAuth sign-in to posterly. If only Bearer / API key auth is available, I will paste a pst_live_ key from https://www.poster.ly/dashboard/api.

Same server in Manus Settings

Shared Integrations path. Prefer OAuth when it is offered.

Settings → Integrations → Custom MCP Servers → Add Server
Server name: posterly
Server URL: https://www.poster.ly/api/mcp
Authentication: OAuth when offered, otherwise Authorization: Bearer pst_live_your_key_here

Hosted transport is JSON-RPC 2.0 over a single POST. No SSE and no streamable HTTP in v1. A verified live connect is still being validated.

Cue vs Manus

Cue leans routines and ongoing responsibility. Manus is the broader agent product at manus.im. Both use the same MCP URL. We do not invent Cue pricing or a Cue Settings menu beyond asking the agent to add MCP by URL.

Cue vs Manus
DetailCueManus
What it isPersonal agents app from Manus (routines and responsibility)Agent product at manus.im
How you add posterlyAsk the agent to add custom MCP / Add MCP by URL (same MCP URL). The same server can be added in Manus Settings, Integrations, Custom MCP ServersSettings, Integrations, Custom MCP Servers, Add Server
AuthOAuth preferred; Bearer pst_live_… fallbackSame
MCP URLhttps://www.poster.ly/api/mcpSame
AccessMay be early-access or inviteGenerally the broader Manus product

See posterly for Manus

What Cue can do once connected

Start with these tools. The rest of the 59 hosted HTTP MCP tools live on the MCP hub. Prefer validate_post, then wait for a clear yes before create_post with confirm true.

Starter tools

whoamilist_accountsvalidate_postcreate_postupload_mediacreate_signed_uploadcreate_media_droplist_mediafind_available_slotgenerate_captionslist_posts
  • whoami (none): Call first. Returns the authenticated user, API key scopes, and workspaces. Covers: You, your scopes, and your workspaces, MCP server and connection status.
  • list_accounts workspace_id?: Connected social accounts. Stop if this is empty and send the user to connect accounts in posterly. Covers: Connected accounts, Learned voice of an account, Performance profile of an account, Check a connect session.
  • validate_post account_id or username+platform, caption, scheduled_at?, media_url?, media_urls?, post_type?, workspace_id?: Dry run. Does not create a post. Use this before showing a preview.
  • create_post same as validate_post, plus confirm: true (required): Destructive write. Refuse unless the user clearly approved caption, account, media, and schedule.
  • upload_media filename, base64_data (hosted), or url. content_type optional. Stdio also accepts file_path.: Hosted path is base64 with a decoded file of 5MB or less. With url, posterly fetches a public HTTPS URL into storage (localhost and private IPs are blocked). Chat paperclip files never arrive here. Covers: Upload a file, Upload from a URL.
  • create_signed_upload filename, content_type, size: Bypasses the Vercel ~4MB API body. Returns upload_url (object storage) and public_url. PUT raw bytes to upload_url, then pass public_url to create_post. Use this when the client can PUT (Cursor, Claude Code, Codex).
  • create_media_drop filename?, max_files?: Creates a no-login page at https://www.poster.ly/drop/<token>. Send drop_url to the user. ChatGPT web, Claude.ai, and Gemini web laptop files use this, then list_media. Not the chat paperclip.
  • list_media limit?, drop_session_id?: Newest media assets. After create_media_drop, pass drop_session_id and use public_url on validate_post / create_post.
  • find_available_slot account_ids?, timezone?, workspace_id?, count?: Always pass timezone explicitly (IANA, e.g. Europe/London). Respects a 1-hour gap.
  • generate_captions platforms (required), brief?, tone?, count?, mode?, source_caption?: Returns caption options only. It does not schedule or publish.
  • list_posts status?, platform?, account_id?, workspace_id?, limit?: Upcoming or recent posts. status is scheduled, published, failed, or draft.
See all MCP tools

Example prompts

  • Add posterly as a custom MCP at https://www.poster.ly/api/mcp. Prefer OAuth. Then run whoami and list_accounts.
  • You own my weekly LinkedIn and X routine. Draft next week's posts, find_available_slot in Europe/London, validate_post each, and pause for my yes before any create_post.
  • Write three caption options with generate_captions for this product update. Do not schedule anything yet.
  • List scheduled posts for this week and suggest one gap I could fill on Instagram.
  • After I approve, create_post the LinkedIn draft with confirm true and send me the View in posterly link.
  • I have a public image URL. upload_media with url, then validate_post an Instagram image post for tomorrow 09:00 Europe/London. Wait for my yes.
  • I have a video on my laptop. Call create_media_drop, send me the /drop/ link, wait, then list_media and validate_post. Do not use the paperclip.
  • Keep a standing Cue routine: every Monday draft LinkedIn and X from my brief, validate_post, and wait. Never publish live unless I explicitly ask for that run.

Post to 18 platforms

Cue can schedule through posterly to every supported social platform.

InstagramFacebookTikTokXLinkedInYouTubePinterestThreadsGoogle BusinessTelegramBlueskyDiscordSlackMastodonDev.toHashnodeWordPressLemmy

Related setup guides

Cue and Manus share connector infra. These pages pair with the same MCP hub.

Pricing

One Stripe subscription: your plan plus API & MCP. Charged now.

API, MCP & Agent Access

$10/month

Starter $7 + API $3, charged now. No free trial on this path.

  • Cue custom MCP by URL, or the shared Manus Integrations path
  • Routines still wait for a clear yes before each live create_post
  • 59 hosted HTTP MCP tools covering 92 actions for status checks, scoped API keys, schemas, scheduling, support, media, brands, analytics, webhooks, OAuth, connect sessions, subscription management, and GBP
  • 100 create-post requests/hour plus separate media/read limits
  • All 18 supported platforms
Get Starter + API · $10/mo

Cue questions

Is Cue the same as Manus?+

Cue is the personal agents app from Manus and shares connector infra. posterly uses the same MCP URL for both. Framing differs: Cue leans routines and ongoing responsibility; Manus is the broader agent product.

Is posterly listed in a Cue or Manus directory?+

Not for this setup. You add a custom MCP by URL (or via Manus Custom MCP Servers). Directory listing is out of scope for now.

What URL do I paste or send the agent?+

https://www.poster.ly/api/mcp (include www). Hosted JSON-RPC 2.0 single POST. No SSE and no streamable HTTP in v1.

OAuth or API key?+

Prefer OAuth sign-in to posterly when the client offers it. If only Bearer or API key auth appears, create a key at https://www.poster.ly/dashboard/api and use Authorization Bearer pst_live_…

Will chat attachments or the paperclip upload my media?+

No. Chat attachments never reach MCP. Use create_media_drop then list_media for laptop files, a public HTTPS URL via upload_media, or create_signed_upload when the client can PUT. Hosted upload_media with base64 hits the ~4MB Vercel request body and is for small images only (relay cap 5MB decoded).

Can a Cue routine publish without asking me?+

Not by default. Agents must validate, show a preview, and wait for a clear yes before create_post with confirm: true, unless you have given an explicit standing rule for that routine in writing.

Where is the full tool list?+

https://www.poster.ly/mcp (59 hosted HTTP tools; 62 on local stdio).

Ready to add posterly in Cue?

This page is setup guidance until transport validation clears. If Cue is still invite-only, use the shared Manus Custom MCP path.