Skip to content
BuzzTake
Sign inGet started
MenuClose

Muse by Meta

Muse and BuzzTake: a connector to try

Muse runs errands from WhatsApp and the Muse app. It builds a custom connector in chat from an API's docs, and BuzzTake needs one header and one route.

Get startedSet up Muse
Connects through
A custom connector, not tested
API
api.buzztake.com, Bearer key
Permission
Settings, Permissions, Always ask
Where
The US, Canada and Singapore, 18 or more
Muse, sample run. Muse in WhatsApp. The user asks what came in on Instagram. Muse asks to use the BuzzTake custom connector, the user allows it once, and Muse lists six new messages and offers to plan a draft.

What Muse can do in your social accounts

Muse is Meta's personal agent, launched on 8 September 2026. It works on its own secure computer with its own browser, from iOS, Android, muse.ai and WhatsApp. Built-in connectors are under Settings, Connectors; for another service, you ask Muse in chat to make a custom connector.

To make one, Muse reads the service's API information and keeps the credentials in its Secure Credentials Store. The BuzzTake REST API is short: GET /v1/workspaces/{id}/accounts lists the accounts, and POST /v1/accounts/{id}/actions runs any action with Authorization: Bearer.

Meta does not review custom connectors. Give Muse a BuzzTake key with read and draft permissions only, and set the connector to Always ask, so the first weeks change nothing without you.

Meta documents no MCP setting for Muse, and BuzzTake has not tested a Muse custom connector. The steps below are a test: start with a key that can read and plan drafts, and nothing more.

It works on Instagram, LinkedIn, Facebook and Threads, and on every other platform BuzzTake connects. Each action is one tool, named as in the actions reference.

Jobs for Muse

Say it in plain words. These are prompts that work, and the calls they make.

  1. Ask from WhatsApp what came in

    Muse lists your new Instagram conversations and LinkedIn notifications and sums them up in the chat.

    With the BuzzTake connector, tell me what came in on Instagram and LinkedIn today.

    1 × list_conversations, 1 × read_notifications8 credits ($0.08)

  2. Plan a post while you are out

    You dictate the idea; Muse plans it as a draft on the BuzzTake calendar for a reviewer.

    Plan a Facebook post for Saturday 10:00 about our new opening hours, as a BuzzTake draft.

    1 × create_content10 credits for each draft that goes out

  3. Look at a competitor's profile

    Muse reads a profile and its latest posts and tells you what they announced this week.

    Read the Instagram profile of globex_demo and tell me what they posted this week.

    1 × read_profile4 credits ($0.04)

Set up Muse

This is a test. Use a key that can read and plan drafts only, and keep the connector on Always ask.

  1. Make a key for Muse

    Under Developers in the BuzzTake app, make a key with inbox_read and content_write only. It can read and plan drafts; it cannot post.

  2. Ask Muse for a custom connector

    Describe the API in one message.

    To Muse
    Create a custom connector for the BuzzTake API at https://api.buzztake.com. It sends the header Authorization: Bearer <key>. GET /v1/workspaces/{workspace_id}/accounts lists the accounts. POST /v1/accounts/{account_id}/actions runs an action with a JSON body such as {"type": "read_notifications", "wait": 60}.

  3. Give the key when Muse asks

    Enter it only where Muse asks for the credential, which keeps it in the Secure Credentials Store. Do not paste it into the chat.

  4. Set the permission

    Open Settings, Permissions, and set the connector to Always ask.

  5. Try a read

    A read changes nothing and costs 4 credits.

    To Muse
    Use the BuzzTake connector to read my latest Instagram notifications.

Ways to connect Muse

The routes that reach BuzzTake from Muse, and how well each one fits.

REST APINot tested

A custom connector that Muse builds from the REST API, with a key in its Secure Credentials Store.

POST /v1/accounts/{id}/actions
curl https://api.buzztake.com/v1/accounts/$ACCOUNT_ID/actions \
  -H "Authorization: Bearer $BUZZTAKE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type": "post", "text": "Version 2.4 is out.", "wait": 60}'
Remote MCP, OAuth sign-inDoes not work

Meta documents no MCP setting for Muse.

Local stdio bridgeDoes not work

Muse documents no shell on its computer.

What it costs

BuzzTake charges in prepaid credits for the actions it runs. One credit is one US cent.

Credits for each job on this page
JobCreditsUSD
Ask from WhatsApp what came in8$0.08
Plan a post while you are out10 per post$0.10 per post
Look at a competitor's profile4$0.04

A post, a quote or a message is 10 credits, a reply 8, a like or a follow 3, and a read or a search 4. A planned post costs nothing until it goes out. Reads are charged when they succeed, and a write that fails before the page changes is refunded.

Muse's model use is billed by Meta, not by BuzzTake. Every price is on the pricing page, and the rules are in Credits.

Approvals and safety

A person can approve before anything goes out, and every action is recorded.

Muse's approval card offers Allow once, Allow for this task, Allow for this site, Always allow and Deny. Under Settings, Permissions, a connector can be set to Ask for some actions or to Always ask.

A key without content_publish is the second lock: Muse can then plan drafts, and a reviewer approves each post in BuzzTake.

  • Ask for drafts when a person must check first. create_content puts the post on the calendar, submit_for_review sends it to a reviewer, and it goes out only after the approval.
  • Give the agent an API key without the content_publish permission. It can then plan drafts and send them for review, and it cannot post by itself.
  • BuzzTake records every action: who asked, through which key, on which account, what the page returned and what it cost.
  • A sign-in step that BuzzTake cannot finish, such as a 2FA code, becomes a challenge. The agent asks you for the code, or gives you a link to a live browser where you answer it.
  • Only an owner or an administrator can allow an OAuth client. Disconnect it under Developers in the app, and its token stops working.

More in Approvals and Reports and audit.

Limits

  • Muse is for people aged 18 or more in the US, Canada and Singapore.
  • Meta does not say whether custom connectors appear in the permission list. Check it after Muse makes the connector.
  • An action tool waits up to 120 seconds for its result. A longer action comes back with its id, and get_action follows it to the end.
  • The MCP server runs up to 8 requests at a time for one key or sign-in. Above that it answers 429 with Retry-After, and the client tries again.
  • One organization connects up to 200 accounts.
  • The platforms set their own pace. When one asks an account to slow down, the action ends with rate_limited, and a write that failed before the page changed is refunded.

Troubleshooting

Every error code and its fix is in Errors and challenges.

Muse cannot build the connector
Give it the two routes and the header in one message, as in the steps, and the quickstart page of the BuzzTake docs.
The connector gets 401
The key is missing or wrong. Make a new key and enter it where Muse asks for the credential.
The client says the server refused the token (401)
The sign-in expired or was revoked, or the API key is wrong. Sign in again from the client, or make a new key under Developers.
An action stops at needs_input
The platform asked for a code. Give the code to the agent so it calls answer_challenge, or open the challenge's sign_in_url and answer in the live browser.
The answer is insufficient_credits
The balance is lower than the price, and nothing was queued. A post needs 10 credits. Top up, then ask again.
The answer is unsupported
The platform has no such action. The error lists the actions it has, and the generic browser action can do the rest step by step.
An account shows signed_out
Its session ended and no stored password could sign it in again. Ask the agent for a sign-in link with get_sign_in_link and open it, or reconnect the account in the app.

Muse questions

Does Muse support MCP servers?
Meta's help pages do not mention MCP. Muse builds custom connectors from an API's docs, which is the route this page tests with the BuzzTake REST API.
Is it safe to give Muse a BuzzTake key?
Give it a key with read and draft permissions only, and set the connector to Always ask. Muse keeps the key in its Secure Credentials Store, and you can revoke the key in BuzzTake at any time.
What can a key without content_publish do?
Read feeds, notifications, profiles and inboxes, and plan drafts on the calendar. It cannot post, reply or send messages.

Related agents

All AI agents, the MCP server docs, the quickstart, and the platforms: Instagram LinkedIn Facebook Threads

Muse is a trademark of Meta. Platform names belong to their owners. BuzzTake is not affiliated with or endorsed by Meta or any platform.

Give Muse your social accounts.

Add an account with a password, cookies or a sign-in link, then connect the MCP server and ask.

Get startedRead the MCP docs