Schedule social posts from Manus
posterly is the publish layer. Manus is the agent layer. Add posterly as a Custom MCP Server by URL, then schedule and publish across your connected social accounts from Manus.
Hero prompt
Using posterly, run whoami and list_accounts. Which LinkedIn and Instagram accounts can I post to? Draft a LinkedIn post, run validate_post, and wait for my yes before create_post.
Preview what is copied
# posterly MCP brief for Manus
You are connected (or about to connect) to posterly, the publish layer. Manus is the agent layer. 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
- This is Custom MCP / Add by URL, 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.
## 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 agent layer.
- After create_post, send the View in posterly link. Avoid raw JSON unless debugging.
- Do not claim a verified Manus 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: Cue uses the same MCP URL and infra (https://www.poster.ly/cue).
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 Servers accept this transport before we claim a verified live connect. Until that clears, treat this page as setup guidance, not a guarantee. Chat attachments never reach posterly. Laptop files go through create_media_drop, then list_media.
What it looks like in chat
Draft, validate, then approve. Your AI never publishes until you say so.
your AI · connected to posterly MCP
MCPNever posts without approval · validate_post before create_post
View in posterlyWorks with Claude, ChatGPT, Gemini, Cursor, OpenClaw, Hermes, Grok Bot, Muse, Poke, Manus, Cue, and any MCP client.
Get Manus connected in three steps
This is custom Add by URL, not a directory listing. Do not look for posterly inside a Manus app directory for this setup.
Open Custom MCP Servers
In Manus, open Settings, then Integrations, then Custom MCP Servers, then Add Server.
Open API and MCPPaste the server URL
Server name: posterly. Server URL: https://www.poster.ly/api/mcp (www is required).
MCP hubChoose auth, then call whoami
Prefer OAuth sign-in to posterly when Manus offers it for this URL (same family as the Claude custom connector). If Manus only shows header, API key, or Bearer auth, use Authorization Bearer pst_live_… from Dashboard, API and MCP. Save, then ask the agent to call whoami.
posterly for CueWhat to enter in Add Server
Custom Add by URL only. Directory listing is out of scope for this setup. Need an account or API add-on first? Start at agent signup, or enable the API add-on in Dashboard, API and MCP.
Fields
Server name
posterlyOr any label you prefer.
Server URL
https://www.poster.ly/api/mcpwww is required. Hosted JSON-RPC 2.0, single POST. No SSE and no streamable HTTP in v1.
Authentication
OAuth preferred; Bearer pst_live_… fallbackPrefer OAuth sign-in to posterly when Manus offers it. If only header or API key auth appears, create a key at https://www.poster.ly/dashboard/api and send Authorization: Bearer pst_live_…
Add Server fields
Paste these into Manus Custom MCP Servers. This is not a directory install.
Server name: posterly
Server URL: https://www.poster.ly/api/mcp
Authentication: OAuth when offered
Fallback: Authorization: Bearer pst_live_your_key_hereIf Manus only shows header or API key auth, the Bearer fallback is the honest path.
Hosted transport
One JSON-RPC POST. There is no SSE stream and no streamable HTTP in v1.
POST https://www.poster.ly/api/mcp
Content-Type: application/json
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "whoami", "arguments": {} } }Eng is validating that Manus Custom MCP accepts this transport. Until that clears, this page is setup guidance, not a verified live connect.
Manus vs Cue
Cue is the personal agents app from Manus and shares the same connector infra. posterly uses one MCP URL for both. Cue early access or an invite may apply.
| Detail | Manus | Cue |
|---|---|---|
| What it is | Agent product (manus.im) | Personal agents app from Manus (same connector infra) |
| How you add posterly | Settings, Integrations, Custom MCP Servers, Add Server | Ask the agent to add custom MCP / Add MCP by URL (same MCP URL). You can also add the server in Manus Settings, Integrations |
| Auth | OAuth preferred; Bearer pst_live_… fallback | Same |
| MCP URL | https://www.poster.ly/api/mcp | Same |
What Manus 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_postswhoami(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_accountsworkspace_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_postaccount_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_postsame as validate_post, plus confirm: true (required): Destructive write. Refuse unless the user clearly approved caption, account, media, and schedule.upload_mediafilename, 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_uploadfilename, 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_dropfilename?, 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_medialimit?, 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_slotaccount_ids?, timezone?, workspace_id?, count?: Always pass timezone explicitly (IANA, e.g. Europe/London). Respects a 1-hour gap.generate_captionsplatforms (required), brief?, tone?, count?, mode?, source_caption?: Returns caption options only. It does not schedule or publish.list_postsstatus?, platform?, account_id?, workspace_id?, limit?: Upcoming or recent posts. status is scheduled, published, failed, or draft.
Example prompts
- Using posterly, run whoami and list_accounts. Which LinkedIn and Instagram accounts can I post to?
- Draft a LinkedIn, X, and Instagram launch post. Find the next free slot in Europe/London, run validate_post for each, and wait for my approval.
- Write three caption options for this product update with generate_captions. Do not schedule anything yet.
- List scheduled posts for this week and suggest one gap I could fill on LinkedIn.
- 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.
- Set a Manus task (or Automation-style recurring ask) that drafts next week's LinkedIn and X posts, runs validate_post, and pauses for my yes before any create_post. Prefer find_available_slot. Never publish live unless I explicitly ask.
Post to 18 platforms
Manus can schedule through posterly to every supported social platform.
Related setup guides
Manus is one route into the same publish layer. Cue uses the same MCP URL and connector infra.
posterly for Cue
Personal agents app from Manus. Ask the agent to add the same MCP URL. Early access or an invite may apply.
MCP setup guide
The hub for hosted HTTP MCP, local stdio, OAuth metadata, and the full tool list.
AI agents overview
How posterly connects to any agent that speaks MCP or REST, plus the agent signup flow.
Agent signup
Paid Starter + API onboarding. The agent never collects card details or passwords.
API dashboard
Activate the add-on, generate keys, and copy setup snippets from inside posterly.
Pricing
One Stripe subscription: your plan plus API & MCP. Charged now.
API, MCP & Agent Access
Starter $7 + API $3, charged now. No free trial on this path.
- Manus Custom MCP by URL, not a directory listing
- OAuth sign-in when Manus offers it, Bearer pst_live_ key otherwise
- 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
Manus questions
Is posterly listed in a Manus directory?+
Not for this setup. You add a Custom MCP Server by URL. Directory listing is out of scope for now.
What URL do I paste?+
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 Manus 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). Longer map: https://www.poster.ly/blog/solving-the-4mb-mcp-limit
Can Manus publish without asking me?+
No. Agents must validate, show a preview, and wait for a clear yes before create_post with confirm: true.
Where is the full tool list?+
https://www.poster.ly/mcp (59 hosted HTTP tools; 62 on local stdio).
Is a live Manus connect confirmed?+
Not yet. Eng is validating that Manus Custom MCP Servers accept a JSON-RPC 2.0 single POST with no SSE and no streamable HTTP. Until that clears, use this page as setup guidance, not a guarantee.
Ready to add posterly in Manus?
This page is setup guidance until transport validation clears. Create a posterly account, then add the Custom MCP URL.