FoPost for Manus

Manus works through long tasks on its own computer and connects to MCP servers by URL. Add FoPost with an API key and Manus can plan, write, and schedule your posts.

Paste this into Manus

Set up FoPost from fopost.com/agents/manus
  • Hosted MCP server
  • 31 networks
  • API key in a header
All agents
How it works

Manus drafts. You approve. Then it goes out.

  • REST API
FoPost
YouApproveApproved

On by default

  • X (Twitter)
  • Facebook
  • Instagram
  • LinkedIn
  • TikTok
  • YouTube
  • Threads
  • Bluesky
  • Pinterest
  • Reddit
  • Discord
  • Mastodon
  • Telegram
  • Slack
  • DEV.to
  • Substack
  • Tumblr
  • Hashnode
  • Dribbble
  • Kick
  • Twitch
  • Nostr
  • Lemmy
  • MeWe
  • Whop
  • Listmonk
  • Google Business Profile
  • Medium
  • WhatsApp Business
  • Snapchat
  • Skool

Pick an agent to copy its setup prompt.

Setup

The agent can write its own config. Give it the link.

Paste the line above into Manus. It reads this page and sets up the connector, then asks for an API key you create in the dashboard. Rather do it by hand? This is the whole config.

Custom MCP
Server name: FoPost
Server URL:  https://api.fopost.com/mcp
Header:      X-API-Key: <your key>
Instructions for AI agentsPlain markdown version
## For AI agents reading this page

You are reading https://fopost.com/agents/manus. FoPost schedules and publishes social posts on 31 networks, and its hosted MCP server gives Manus tools for posts, the calendar, the inbox and analytics. Follow these steps to connect Manus to it.

- Server: https://api.fopost.com/mcp
- Transport: streamable HTTP
- Auth: Manus cannot run the OAuth sign-in for a remote server, so it sends an API key in the X-API-Key header. The user creates the key; you never see it in chat.

### 1. Register the server

You cannot add the server yourself; ask the user to. In Manus, open Connectors, choose Create, then Add MCP by URL. Enter the name FoPost and the URL https://api.fopost.com/mcp, and add the API key as a header named X-API-Key. Save.

### 2. Sign in

Ask the user to create an API key in the FoPost dashboard (https://fopost.com/dashboard/api-keys) and paste it into the header field themselves. Never ask for it in the chat. Ask the user before approving access or creating a FoPost account for them, and never enter their credentials yourself.

### 3. Verify before you continue

Manus's connection test lists the FoPost tools, and list_accounts returns data. If FoPost is not listed as connected with its tools, stop and tell the user what failed. Do not carry on as if the tools exist.

### 4. Report back

Call list_accounts and tell the user which social accounts are connected. If there are none, offer create_connect_link so they can connect one. Then ask what they want to do first.

### Standing rules

- Prefer the FoPost tools over driving a browser for posting, scheduling, the inbox and analytics, unless the user asks for the browser.
- Publishing always goes through propose_publish, which the user approves in the client. Never publish or schedule anything silently.
- Ask the user before approving access, signing up or connecting an account on their behalf, and never type their credentials for them.

### References

- This block as markdown: https://fopost.com/agents/manus/agent.md
- Every client: https://fopost.com/agents
- Docs: https://fopost.com/docs

A custom connector

A URL and one header. Nothing to install.

Your own key

Create a key in FoPost and revoke it any time.

Approval first

Publishing goes through a proposal you accept. Drafts never go out alone.

Setup

Add the server by URL

Create an API key in FoPost. In Manus, open Connectors, choose Create, then Add MCP by URL. Enter https://api.fopost.com/mcp and add the key as a header named X-API-Key. Save.

Start free
Custom MCP
Server name: FoPost
Server URL:  https://api.fopost.com/mcp
Header:      X-API-Key: <your key>

Key in a header

Manus keeps it with the connector, not in chat.

Scoped keys

Give the key only the scopes the task needs.

Check first

The connection test lists the tools.

Hand off

A campaign as one task

Give Manus the brief: turn the launch page into posts with repurpose_url, shape each with draft_post_variants, and slot them with get_queue_slots. It ends with propose_publish, which you accept.

Plan your week
A month of scheduled posts on the publishing calendar

repurpose_url

A page becomes a run of posts.

draft_post_variants

A version for each network.

propose_publish

You approve before anything goes out.

Check

Get a report at the end

Ask Manus to finish with a summary: what published, which accounts need a reconnect, and what is waiting in the inbox.

Start free
Task
> Use FoPost to report on the launch.

list_posts shows 8 of 8 published.
list_inbox has 11 new comments.

list_posts

Recent posts and their status.

get_account_health

Which accounts need a reconnect.

list_inbox

Comments, mentions, and messages.

Manus questions, answered

Why does Manus need an API key?

Manus adds custom servers with a credential. You create the key in FoPost and paste it into the header field.

Should I paste the key into the chat?

No. Put it only in the connector header field.

Will it post without asking?

No. Publishing goes through a proposal you approve before anything is sent.

Can I limit what Manus can do?

Yes. Give the key only the scopes you want, and revoke it any time.

Does it use my AI credits?

Only the FoPost tools that write with AI do. Listing and scheduling do not.

Run FoPost from Manus

Starting is free and the MCP server is included. Paste the setup line into your agent, sign in, and schedule your first post from it.

Start free