FoPost for Muse

Muse adds services through custom connectors that it builds itself when you ask. Give it the prompt below and a FoPost API key, and it can plan posts, fill your queue, and tell you what went out.

Paste this into Muse

Set up FoPost from fopost.com/agents/muse
  • Hosted MCP server
  • 33 networks
  • API key in a header
All agents
Setup

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

Paste the line above into Muse. 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.

Prompt for Muse
Create a custom connector for FoPost.
It is an MCP server at https://api.fopost.com/mcp.
Authenticate with my API key, sent in the X-API-Key header.
When it works, list my connected social accounts.
Instructions for AI agentsPlain markdown version
## For AI agents reading this page

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

- Server: https://api.fopost.com/mcp
- Transport: streamable HTTP
- Auth: Muse 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

Muse builds custom connectors itself when asked, and keeps the credential in its secure credentials store. Create the connector for the MCP server at https://api.fopost.com/mcp, sending the API key in the X-API-Key header.

### 2. Sign in

Ask the user to create an API key in the FoPost dashboard (https://fopost.com/dashboard/api-keys) and enter it when Muse asks for the connector credential. Never ask for it in the chat itself. Ask the user before approving access or creating a FoPost account for them, and never enter their credentials yourself.

### 3. Verify before you continue

The connector calls list_accounts and gets data back. 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/muse/agent.md
- Every client: https://fopost.com/agents
- Docs: https://fopost.com/docs

A setup prompt

There is no form to fill in. Muse builds the connector from what you tell it.

A scoped key

Muse keeps the key in its secure credentials store. Grant only the scopes it needs.

Approval first

Muse asks before important actions, and publishing also waits on your approval.

Setup

Ask Muse to build the connector

Create an API key in the FoPost dashboard. In Muse, send the setup prompt above. Muse walks you through creating the custom connector and asks for the key, which it stores in its secure credentials store. When it can list your accounts, the connection works. Muse is available in the US and Canada.

Start free
A caption written once, with the post previewed as each network renders it

Read first

Start the key with read scopes, and add posting once you trust the setup.

One workspace per key

Muse sees the workspace the key belongs to, and no other.

Check first

The prompt ends by listing your accounts, so you know it connected.

Plan

Plan the week in conversation

Tell Muse what is coming up and where it should go. It drafts with create_draft_post, finds open times with get_queue_slots, and hands you a propose_publish to accept before anything is sent.

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

draft_post_variants

A version of each post for every network.

get_calendar

What is already booked.

propose_publish

The plan you approve before it goes out.

Check

Ask how it went

Ask Muse which posts went out, which accounts need attention, and what is waiting in your inbox.

Start free
Prompt
> How did this week's posts do?

Muse: list_posts shows 6 published.
get_analytics_summary: engagement up on last week.

list_posts

Recent posts and where each stands.

get_analytics_summary

How the week performed.

list_inbox

Comments and messages to answer.

Muse questions, answered

Where is the MCP setting in Muse?

There is none. Built-in connectors live under Settings > Connectors; for a service that is not listed, you ask Muse to create a custom connector and it guides you through it.

Why an API key here?

Muse sets up custom connectors with credentials you give it, so a scoped FoPost API key is the reliable way in. Revoke it from the dashboard at any time.

Will it post without asking?

No. Muse asks before important actions by default, and publishing goes through a proposal you approve.

Is Muse available where I am?

Muse is available in the US and Canada.

Does Meta review my connector?

No. Custom connectors are your own setup, so give the key only the scopes you are comfortable with.

Run FoPost from Muse

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