Run your marketing from Meta Muse with ReachPill

Meta Muse doesn't have a connector store. You tell it what you want to connect, and it writes the integration itself on its own cloud machine, tests every tool, and saves the result as a skill you can reuse. It works best with an MCP server over streamable HTTP or a public OpenAPI document.

ReachPill offers both, so connecting it takes one message. After that, your Muse agent can do what you'd otherwise do in the console: set up your brand, run campaigns, publish posts you wrote yourself, write blog articles, and tell you how it's all going.

What you need

• MCP server: https://app.reachpill.com/mcp (streamable HTTP; an org API key works as a bearer token)
• OpenAPI spec: https://app.reachpill.com/openapi.yaml
• Skill file: https://app.reachpill.com/docs/skill.md, with the ground rules, the main workflows and the full tool catalog, written for agents
• An API key from ReachPill under Settings → MCP → API keys

Muse runs in the cloud, so it can't reach anything on your laptop. ReachPill's server is public, so that isn't a problem here.

Connect it in five steps

1. Create a test key first. In ReachPill, open Settings → MCP → API keys and create a key starting with mg_test_. With a test key, generations finish instantly with placeholder images at no cost, and publishing goes to a simulated channel. That makes Muse's tool-testing pass completely safe.

2. Ask Muse to connect. Send it this:

   Connect ReachPill for me. It is an MCP server over streamable HTTP at https://app.reachpill.com/mcp and uses a bearer API key (I will enter it in the secure prompt). Its skill file with workflows and the tool catalog is at https://app.reachpill.com/docs/skill.md — read it first. Build the connector, list and test the tools read-only, then save it as a skill named "reachpill".

3. Enter the key in Muse's secure prompt when it asks. Never paste it into the chat, where it would stay in your history.

4. Set the approval policy. Read-only is fine for reporting. For anything that publishes or spends, choose "approve each action".

5. Switch to a live key (mg_live_…) once the loop works. Nothing else changes.

The same steps, with the message ready to copy, are on the Meta Muse tab under Settings → MCP in ReachPill.

What your agent can do

Each item below lists a prompt you can give Muse and the ReachPill tools it ends up using.

Set up your brand from your website

Set up our brand in ReachPill from https://ourcompany.com.

Muse runs derive_brand, reads the result, and saves the voice, palette, imagery style and logo with update_brand_kit. Every post ReachPill makes afterwards is grounded in that brand.

Post now or schedule

Post this announcement to LinkedIn and X tomorrow at 9am, using the open slots.

get_social_slots finds the times, and schedule_social_post books the post on your connected channels. Your agent can also edit, cancel or retry a post later.

Run a campaign on autopilot

Plan a two-week launch campaign for our new feature on LinkedIn and Instagram. I want to review every post.

create_campaign and plan_campaign_arc build a narrative across the posts and a cadence. Muse can then go through the queue with list_campaign_occurrences and approve, reject or edit each post (approve_occurrence, reject_occurrence, edit_occurrence). reschedule_occurrence moves a post even after it's been scheduled.

Put your own posts through ReachPill

Here are 12 posts with captions, headlines and screenshots. Schedule them over the next month in our campaign, with our brand background behind each screenshot.

If you already write your posts, ReachPill doesn't need to write them. A provided-content campaign (create_campaign with content_source: "provided") takes your captions exactly as written and handles the rest: scheduling, review, brand checks and publishing.

• Muse uploads your images with create_upload_url and confirm_upload, or upload_media for an image at a public URL.
• It adds the posts with import_campaign_posts, or add_campaign_post for a single one. Each post has its own id, so running the import again updates posts instead of duplicating them.
• It can approve a whole date range at once with approve_occurrences, and check any post, including the exact image that will go out, with get_occurrence.
• Campaigns can also enforce content rules: banned terms, and required spellings such as your product name's capitalization. A post that breaks a rule can't be approved until it's fixed.
• Placeholders like {SITE_URL} are filled in when a post is scheduled.
• ReachPill e-mails you if a post misses its slot.

Images without AI

Use our brand background for this campaign's images. No AI images.

Each campaign's image setting (media.source) can be:

• generated, the default: an AI image for each post, grounded in your brand
• brand: your Brand Kit background with the post's headline, an optional screenshot and your logo composed on it. No image model runs, so it costs no credits and needs no AI provider key.
• none: text-only posts

Individual posts can override the campaign with image_mode:

• composite: your image in a phone frame over an AI-generated background
• brand: your image on your brand background, no AI
• as_is: your image exactly as you supplied it
• none: no image

Posts don't stop over billing

If your ReachPill credits run out, or your own AI provider key goes missing or gets locked, a post that needed an AI image goes out on your brand background instead of failing. You're told in the queue and by e-mail. If you'd rather such posts wait, set the campaign's media.fallback to hold.

One limit: when ReachPill writes the captions, it still needs a language model. An org with no credits and no text key of its own will see those posts wait until it tops up. Posts you wrote yourself keep publishing.

Blog articles

Write a blog post about our new pricing and publish it to our site.

create_blog_post and generate_blog_post draft the article and its hero image, and publish_blog_post commits it to your GitHub repo or delivers it to your site through a webhook.

Reporting and spend

How did last week's campaign do, and what have we spent this month?

get_campaign_report shows results per post, grouped by the feature each post was about. get_balance, get_usage_summary and get_spend_breakdown cover credits and spend. These are all read-only, so they're safe to allow without approval.

What costs money

• Billed: AI-generated images, including the composite image mode (paid in ReachPill credits, or to your own provider if you use your own AI key), and captions ReachPill writes for you (billed as text generation)
• Free: the brand, as_is and none image modes, and publishing and scheduling

Your agent can call get_balance before it starts anything big.

Keep it safe

• Enter keys only in Muse's secure prompt, never in the chat.
• Start with a test key. Muse's testing pass and your first experiments then cost nothing and post nowhere.
• Scope the approvals. Meta doesn't review custom connectors, so approve each action for anything that publishes or spends.
• Keep review on in ReachPill. Campaign review settings apply whatever tool asks, so if a campaign requires review, nothing in it publishes until a person approves it, even when Muse is driving.

Muse is available to adults in the US at launch. If you're there, create a test key and send it the message above.