Connect an assistant to Dispatch
Add Dispatch as a connector in the assistant you already use, then ask in plain sentences: draft a post, schedule it, publish it, or see how it did.
The connector address
https://dispatch.replybeam.app/mcp
The address is the same for everyone, and Settings → Assistants shows it with a Copy button. Dispatch speaks MCP, the Model Context Protocol. You sign in to Dispatch to allow each app, so there is no key or password to copy.
Connect your assistant
Claude
On the web or in the desktop app: Customize → Connectors → Add → Add custom connector. Paste the address, then sign in to Dispatch and press Allow access. Claude’s own instructions
ChatGPT
On the web: Plugins → Add → Add custom MCP server. Paste the address, then sign in to Dispatch and press Allow access. OpenAI decides which ChatGPT plans can add a custom server and which can make changes with it. ChatGPT’s own instructions
Claude Code
In your terminal:
claude mcp add --transport http dispatch https://dispatch.replybeam.app/mcp
Then sign in to Dispatch in the browser when Claude Code asks you to, and press Allow access.
Other apps
Anything that supports MCP connectors works the same way: add the address as a connector (a remote MCP server over Streamable HTTP), then sign in to Dispatch and press Allow access.
The menus are each app’s own and can change. These steps were checked on November 12, 2026.
What you allow
The first time an app connects, Dispatch shows who is signed in, what the app calls itself and where it will send you back, and asks you to choose Allow access or Cancel. The app’s name is its own claim, so allow an app only when you have just started connecting it yourself: there is a box to tick that says so before Allow access works. An app you allow can:
- See your connected accounts, your plan and how much of it is used
- See your uploads and posts, and how published posts did
- Create and change drafts, and make links for uploading videos and photos
- Publish posts to your connected accounts, now or on a schedule, and cancel a schedule
It can’t:
- Delete posts or uploads
- Connect, disconnect or remove accounts
- See or change billing, webhooks or sign-in, or delete your account
The app works as you: it sees your accounts, uploads and posts and nobody else’s.
What an assistant can do
These are the tools Dispatch gives a connected app. You don’t call them yourself: you ask, and the assistant chooses.
| Tool | What it does |
|---|---|
get_account | Your plan, its limits and what is used, and your connected accounts |
list_media | Your uploads that can still go on a post |
create_upload_link | A one-time address that takes one video or photo, for 30 minutes |
list_posts | Your posts and their states |
get_post | One post, with how each destination went |
create_post | A new draft. Never publishes |
update_post | Changes to a draft |
schedule_post | Publish a draft at a time, or move a scheduled post |
publish_post | Publish a draft or a scheduled post now |
cancel_schedule | Take a scheduled post back to a draft |
retry_destination | Try one failed destination again |
get_post_results | Likes, comments, views and the rest for a published post |
get_results | The same numbers for everything published in the last days |
Every tool goes through the same checks as the studio, so a post the studio would refuse is refused here too.
Publishing waits for you
create_post only makes a draft. Before an assistant schedules or publishes, Dispatch tells it to confirm the accounts, the caption and the time with you. Read what it shows you before you agree: a published post is on your public accounts, and Dispatch can’t take it back. Dispatch writes nothing itself. It saves the caption exactly as the assistant sends it.
A scheduled post goes out from Dispatch’s server, so neither you nor the assistant has to be there. Until publishing starts you can ask the assistant to move it or cancel it, or do that in the studio.
Getting a video in
There are two ways.
- Upload it in Dispatch. Open Create and add the video or photo as usual. The assistant finds it with
list_media. - Ask the assistant for an upload link.
create_upload_linkgives it an address that takes one file. This suits an assistant that can run commands where the file is, such as Claude Code:
curl -F file=@video.mp4 "https://dispatch.replybeam.app/uploads/…"
An upload link works once and for 30 minutes, and you can have 5 unused ones at a time. Anyone who has the link can use it, so it is made when it is needed and not kept. It takes a video of up to 4 GB, or a photo (JPEG, PNG, WebP or HEIC) of up to 50 MB.
Either way Dispatch then prepares the file, which takes a little while, and it can go on a post once list_media shows it as ready. Dispatch prepares up to 3 of your uploads at a time.
Limits
Your plan’s limits apply to a connected app exactly as they do in the studio. The free plan has 15 posts a month, 3 connected accounts and 1 GB of media. Pro has 300 posts, 12 accounts and 25 GB. A post counts once towards your month when it is published or scheduled, however many accounts it goes to. You can keep 100 drafts on the free plan and 1000 on Pro. get_account shows where you stand.
You can have 10 apps connected. Each app can make 120 requests a minute, and your apps together can make 30 changes a minute (drafts, schedules, publishing and upload links). Past either, the app is asked to wait and try again.
YouTube in Dispatch is in early access: the number of uploads Dispatch can make each day is limited, and an upload over the day’s capacity waits and is tried again about a day later.
Connecting an account needs a browser
You connect an Instagram account, a Facebook Page or a YouTube channel on the platform’s own consent screen, where you choose what Dispatch may use. An assistant can’t do that for you. Sign in to Dispatch, open Accounts and connect the account there. The assistant can then see it and post to it.
If an account’s state becomes reauth_required, the platform wants your consent again. Reconnect it in the browser, then ask the assistant to retry what failed.
Disconnect an app
Settings → Assistants lists every app you allowed, with when it was connected and when it was last used. Choose Disconnect beside one and confirm: its access ends at once. You can remove the connector in the app as well; disconnecting it here is what ends its access for certain.
For people building an MCP client
The MCP endpoint is https://dispatch.replybeam.app/mcp, over Streamable HTTP. It is protected by OAuth 2.1 with PKCE (S256), and Dispatch is its own authorization server: a request without a token answers 401 with a WWW-Authenticate header that names the metadata at /.well-known/oauth-protected-resource/mcp. A client identifies itself with a Client ID Metadata Document or through dynamic registration, and is a public client either way. Access tokens last an hour; refresh tokens are replaced each time they are used.