Connect Bolta to any MCP client
Bolta hosts an MCP server at https://mcp.bolta.ai/mcp. An AI app that accepts a remote MCP server over Streamable HTTP can use it to draft and review social posts and to plan repeating work in your brand voice. You sign in through the browser, or send an API key where the app has no sign-in button. Nothing is approved, scheduled or published until you say yes.
- One address: https://mcp.bolta.ai/mcp, over HTTP.
- Browser sign-in, or an API key where there is no sign-in button.
- Drafts save freely. Nothing posts until you say yes.
Nothing is approved, scheduled or published until you say yes.
Partly confirmed, see what is and is notChecked 2026-11-21
The same address works in every app. Where you paste it depends on the app.
Which Bolta brands can you see? List them only.
Illustration of the reply: Bolta returns a draft showing the connected account and the scheduled time, with Approve, Edit and Reject actions.
Add Bolta to your MCP app in two steps
- 01
Add the address
In your app's MCP or connectors area, add a remote server named Bolta with the address https://mcp.bolta.ai/mcp. Choose HTTP (Streamable HTTP) if it asks for a type.
- 02
Sign in, then ask
Approve the browser window on Bolta and tick your brands. Then ask: Which Bolta brands can you see? List them only.
What is and is not confirmed
Read this before you set up MCP Server
- Confirmed: the address https://mcp.bolta.ai/mcp answers over HTTP and asks for a Bearer token, pointing to OAuth sign-in details. Bolta's own docs describe the browser sign-in and the Bearer API key route.
- Confirmed from the MCP specification: remote servers can ask for OAuth sign-in or accept a bearer token over HTTP.
- Not confirmed: nobody has run a full draft, review and schedule in each MCP client. Bolta's skills repository lists every client except the Claude Code plugin as not tested, and the Claude Code row runs its behavioural checks against a mock Bolta.
- Not confirmed: whether your app's settings screen has a box for an Authorization header. The protocol allows it, but apps differ.
- Menu names and config file locations change between app versions. Use your app's own MCP docs for where to click, and keep the address the same.
What happens when any MCP app calls Bolta
The steps are the same whichever app you use. Only the screen where you paste the address changes.
- 01
The app finds the server
You give your app the address https://mcp.bolta.ai/mcp. The app opens a client for that one server and asks which tools it offers.
- 02
Bolta asks who you are
A request with no credentials gets a 401 with a WWW-Authenticate header that points to Bolta's sign-in details. The app then opens the browser sign-in, or sends the Bearer API key you set.
- 03
Your brands are listed
list-workspaces returns the brands this connection can reach, and only the ones you ticked at sign-in appear. list-accounts then shows the social accounts connected to a brand, and a draft needs one as its destination.
list-workspaces - 04
The AI reads your voice
get-voice-context hands the AI the voice and business details you set up in Bolta, so the draft is written from those and not from the AI's own default style.
get-voice-context - 05
It checks the rules, then saves a draft
get-posting-rules gives the limits for the network you chose, and save-post stores the text as a draft. Making a draft costs nothing and sends nothing.
get-posting-rules - 06
You decide
The AI shows you the exact text. publish-post is called only after you say yes to that post, and Bolta's own checks can still refuse it.
publish-post
Set up MCP Server
Connect once. Everything below works from MCP Server afterwards.
- 01
Find where your app adds MCP servers
Look for MCP or Connectors in the app's settings, or for a JSON config file. If you find neither, the app may not support remote MCP servers yet, so check its release notes or MCP docs.
- 02
Add a remote server with Bolta's address
Use https://mcp.bolta.ai/mcp and, if asked, the type HTTP (Streamable HTTP). In a JSON file, use the key your app expects: servers or mcpServers for the group, and url, serverUrl or httpUrl for the address. Bolta's server is remote, so choose a remote or HTTP server, not a local command.
- 03
Save and start the server
Save the setting or file, then start the server if your app leaves that to you. An app that supports sign-in for remote servers should open a Bolta window in your browser.
- 04
Sign in and tick your brands
Sign in on the Bolta page and tick the brands this app may use. A connection covers one organization, and with this route no key is copied anywhere.
- 05
No sign-in button? Use an API key
Create a key under Settings, API Keys in Bolta. It starts with bolta_sk_, and you tick only the permissions the job needs. Send it as the header Authorization: Bearer followed by the key, and enter it through your app's secret field where it has one, so it stays out of a file that could reach Git.
- 06
Check that your app lists Bolta's tools
Open the app's tools list, or expand a tool call after your first question. If Bolta is listed and switched on, the connection works.
- 07
Add the Bolta skill
Optional. The server works without it. If your app reads a skills folder, install it from a terminal with npx skills add boltaai/bolta-skills --skill bolta, or copy skills/bolta from the bolta-skills repository by hand. Keep the folder name bolta.
- 08
Ask it to name your brands
Start a new chat and ask it to list your Bolta brands without changing anything. The reply should name your real brands and show a Bolta tool call. A confident answer with no tool call means the connection is not live.
- 09
Ask for a first draft
Ask for three draft posts for next week. They save as drafts you can read and edit, and none of them is approved, scheduled or published until you say yes.
Connect MCP Server to Bolta
The same address works in every app. Where you paste it depends on the app.
Which Bolta connection methods work with a generic MCP app
This page covers apps that have no page of their own here, so most rows depend on your app. Where the app decides, the row says Not confirmed.
| Method | With MCP Server | How |
|---|---|---|
| Remote MCP server with browser sign-in | Not confirmed | The address answers over HTTP and Bolta documents the sign-in. Whether your app opens the browser window for a remote server has not been tested in every app. |
| Remote MCP server with an API key header | Not confirmed | The protocol allows a Bearer header. Some apps have a header box and some do not, so check yours. Keys start with bolta_sk_ and come from Settings, API Keys. |
| Local (stdio) MCP server | Not available | Bolta's server is remote, so an app that only starts local commands cannot reach it directly. |
| Bolta skill via npx skills add | Not confirmed | Optional add-on that only matters if your app reads a skills folder. Bolta has not tested it in a generic app. |
| REST API | Works | For code you write yourself, with API keys. It does not need an AI app at all. See the API docs. |
| Claude Code plugin | Not available | Not part of this generic route. Claude Code has its own page with its own steps. |
What you can run in Bolta from MCP Server
Each row is an area of Bolta, with the real tools behind it.
Posts and drafts
Save one post, or a batch, as drafts, then read them back or delete them. A deleted post can be listed and restored for 7 days.
save-postbulk-create-postsget-postdelete-postlist-recently-deletedrestore-deletedReview and approval
See what is waiting and send a draft to the team review list. Approval is tied to the exact text, so a changed post needs a fresh yes. Bolta's skills README says batch approval and rejecting with a reason reach Claude and Cursor today, and other apps fall back to one approval at a time or a link to Bolta.
list-inbox-itemssubmit-for-reviewVoice and brand
Read the voice the AI writes in, add a voice profile, and read or change the business details it works from.
get-voice-contextcreate-voice-profilelist-business-dnaupdate-business-dnaPlans and routines
Say what should repeat, read the plan the AI proposes, ask for changes, and save it switched off. Switching it on takes a second yes from you.
planrevise-planconfirm-plancreate-routineactivate-routinepause-routineCampaigns
Attach a web page or file as a source for a campaign of posts. A campaign needs its own go-ahead before it runs. The skills README says campaign set-up from chat reaches Claude and Cursor today, so in another app you may be sent to Bolta for this step.
plan-campaigncreate-content-campaignset-content-campaign-statusResults
Ask how recent posts and accounts did, then ask for ideas from that. Post figures come from Bolta and sync nightly, so a very new post may show no numbers yet.
get-account-analyticslist-account-insightslist-workspace-postsReplies and conversations
Find posts worth joining, which needs a monitoring campaign already set up in Bolta, and draft replies to comments on your own posts. Drafting is free, and sending a reply is a separate step that needs your yes.
list-engagementssearch-engagement-opportunitiesdraft-engagement-replydraft-inbound-reply
A first session in an MCP app
A made-up chat that shows the order of events. The brand, the wording and the replies are invented for this page, not output from a real session.
- You
Which Bolta brands can you see? List them only. Do not change anything.
- Tool call
list-workspacesRead only. Returns the brands this connection can reach.
- MCP Server
I can see one brand, Fernhill Bakery. I have not changed anything. Want a draft for it?
- You
Yes. One post for Threads about our Saturday sourdough, short and friendly.
- Tool call
list-accountsRead only. Checks that the brand has a Threads account.
- Tool call
get-voice-contextReads the brand's voice before writing.
- Tool call
get-posting-rulesReads the limits for Threads.
- Tool call
save-postSaves a draft. Not scheduled, not published.
- MCP Server
Saved as a draft: "Saturday means sourdough. Come early, because the first loaves go fast." It is not scheduled and will not post. Want a change first?
- You
Swap 'go fast' for 'disappear'. Then leave it for me to check.
- Tool call
save-postEdits the same draft. Still not scheduled, not published.
- MCP Server
Changed, and it is still a draft. When you want it out, tell me to schedule it and I will show you the exact time and text first.
Browser sign-in or API key?
Both reach the same server. Pick by what your app offers.
Browser sign-in (OAuth)
Choose this when the app opens a browser window for remote servers.
Bolta opens in your browser, you sign in and tick the brands. Bolta's setup guide says posts made this way wait on your review list until you approve them. The sign-in is valid for about 60 days and usually renews itself.
API key (Bearer header)
Choose this when the app only accepts headers and has no connect button.
A key you create acts as you, so it is not held back by the review list the way the sign-in route is. Safe Mode and a client's required sign-off still apply. Tick only what the job needs, for example posts:write to save posts.
What can MCP Server do with Bolta?
- Add Bolta to an AI app that has no page of its own here, using one address
- Draft a week of posts in your brand voice from inside your app's chat
- Check what is waiting for approval without opening Bolta
- Compare how recent posts performed before you plan the next ones
- Set up a repeating routine from chat, with the plan shown first
- Keep one connection per organization and choose brands at sign-in
What to ask once Bolta is connected
Sample replies are illustrative. Your real brands and posts will differ.
Which Bolta brands can you see? List them only.
I can reach two brands on this connection: Harbor Coffee and Harbor Roasters. I have not changed anything. Which one do you want to work on?
list-workspaces, list-accounts
For Harbor Coffee, write one LinkedIn post about our new autumn menu and save it for my review.
I saved a LinkedIn draft in your brand voice. It is not scheduled and it will not post until you approve it. Want to change the wording first?
save-post
Show me what is on my Bolta review list.
Five items are waiting: three drafts from a routine and two from this chat. I can read out the full text of any of them. I will not approve any until you tell me which ones.
list-inbox-items
Plan a weekly Friday post for Harbor Coffee and show me the plan first.
Proposed plan: a draft each Friday at 9:00, brand time, sent to review before anything goes out. Bolta would run it, so it repeats with this app closed. If you agree I save it switched off, and turning it on is a separate yes from you.
plan, confirm-plan
How did my last five posts do, and what should I try next?
Here is what Bolta shows for the last five posts, with the numbers it holds. Where a number is missing I will say so and not guess. From the pattern I can suggest two angles to try as drafts. I will not save anything yet.
list-workspace-posts, get-account-analytics
I want to post to Bluesky too, but it is not connected. What now?
Bluesky is not connected to this brand yet. I can give you a link to connect it in Bolta. Once it is connected, tell me and I will check that it shows up on the account list.
get-connect-link, list-accounts
Which of my connected accounts is growing fastest?
Here is what Bolta shows per account for the window, with followers, engagement and growth. If an account has no data yet I will say so and not estimate it. I have not changed anything.
list-account-insights
Bolta publishes to, including
- X
- Threads
- Bluesky
Which networks you can post to depends on the accounts you connect in Bolta.
What keeps running without your MCP app open
A chat in your app only works while the app is open. Work that Bolta holds does not depend on it.
- A routine saved in Bolta repeats on its schedule even with your app closed. It is created from chat, but Bolta runs it.
- Drafts and review items already saved stay in Bolta until you act on them. A plan you have not saved is only text in the chat.
- Needs the app open: asking questions, revising wording in conversation and talking through a plan.
- Bolta's MCP docs say a routine's drafts wait for review, so what it writes does not go straight out.
A routine runs only after you separately confirm it and switch it on. Saving a plan does not start it.
What MCP means for a social media user
MCP stands for Model Context Protocol. It is an open standard that lets an AI app talk to another service the same way, a bit like one port that fits many devices. The AI app is the host. It opens one client for each server it connects to.
Bolta's side is a hosted remote server, so nothing is installed or run on your computer. Your app calls the address, Bolta checks who you are, and the AI is handed tools for drafting, review, plans, routines and results.
The same server in the shapes different apps use
The address and the HTTP type never change. Apps differ in what they call the keys. Check your app's own MCP docs for the exact names.
Those shapes come from Bolta's own skills repository and guides. Other apps may use serverUrl or another name. If your app is not listed, look for the setting that takes a remote server address.
| Where | Shape |
|---|---|
| VS Code, .vscode/mcp.json | servers, then bolta with type http and url |
| Cursor, mcp.json | mcpServers, then bolta with url |
| Gemini CLI, gemini-extension.json | httpUrl |
| Codex CLI, ~/.codex/config.toml | [mcp_servers.bolta] with url |
| Grok Build | grok mcp add --transport http bolta https://mcp.bolta.ai/mcp |
What if my app only supports local servers?
Bolta's server is remote, so the app must support remote MCP servers over HTTP. Some apps only run local servers started by a command (stdio). Check whether yours has a Remote, HTTP or URL option in its MCP settings.
If it does not, Bolta cannot connect directly. Update the app first, then look again. Another route is the Bolta REST API, or an automation tool that supports Bolta.
One connection is one organization, with the brands you tick
- The connection reaches the brands you ticked when signing in, within one organization.
- To add a brand later, remove Bolta in your app, add it again and tick the new one.
- With several brands, say which one you mean. Calls carry a workspace_id once more than one brand is reachable.
- Bolta's rules still apply: your role, Safe Mode and approval. The AI cannot work around a refusal.
The kinds of tool a connected app can call
Once connected, your app lists Bolta's tools by name. The kinds are brands and accounts, drafts, the review list, voice and brand details, plans and routines, campaigns, results and replies. Which tools an app is offered can differ by client, so compare your app's list with the full one in the MCP docs.
Your role and the key's permissions decide what each call may do. Anything that changes what goes out, such as approving, scheduling or publishing, needs your yes to that task, and Safe Mode applies on top.
The Bolta skill, and when it is worth adding
A skill is a folder of written instructions your app can load so it uses Bolta's tools in a sensible order. It is optional. The connection works without it, and the skill only helps in apps that read a skills folder.
The command is npx skills add boltaai/bolta-skills --skill bolta. By hand, copy skills/bolta from the repository, and keep the folder name.
Where apps differ, and what is untested
- Key names differ: url, serverUrl, httpUrl, and servers versus mcpServers. The address does not.
- Sign-in differs: some apps open a browser window for a remote server, others only take a header.
- Bolta's skills repository lists every client except the Claude Code plugin as not tested, and the plugin row runs against a mock Bolta.
- Tool lists differ too. Per that README, batch approval, rejecting with a reason and campaign set-up from chat reach Claude and Cursor today. Elsewhere you may approve one post at a time or be sent to Bolta. This was not tested live here.
- So treat a first run in a new app as a test: ask it to list your brands, then save one draft, and stop there.
What MCP Server cannot do without you
MCP Server connects as: Remote server address, Streamable HTTP.
Drafts are free, finals need your yes
MCP Server can write, edit and save drafts at any time. Approving, scheduling, publishing, sending a reply, activating a routine or campaign and deleting each wait for your yes, shown against the exact text.
One connection, one organization
When you connect MCP Server you tick the brands it may reach. It reaches only those, and when that is more than one brand, every call names the brand it is for.
Your role is the ceiling
Each call MCP Server makes is checked like a normal request from you. Owners and admins can act on any post, creators on Bolta's drafts and on posts they are a named reviewer on, and viewers never approve or publish.
Where MCP Server can publish through Bolta
11 social networks, plus WordPress for articles. Bolta holds the connected accounts. Each card opens the MCP Server guide for that network.
- Threadstext posts, image posts, polls
- LinkedIntext posts, articles, carousels
- X (Twitter)tweets, threads, polls
- Instagramposts, stories, reels
- Facebookposts, stories, reels
- Blueskyposts, threads, quote posts
- Mastodontoots, polls, threads
- Reddittext posts, link posts, image posts
- TikTokvideos, stories, photo posts
- YouTubevideos, Shorts, community postsTeam plan, beta
- Pinterestpins, idea pins, video pinsTeam plan, beta
The words behind MCP Server and Bolta
For MCP Server: Remote server address, Streamable HTTP, signing in with Sign in (OAuth), or a Bearer API key.
- MCP
- The Model Context Protocol, an open standard that lets an AI app call tools in another product. Bolta's hosted server is at https://mcp.bolta.ai/mcp, and MCP Server reaches Bolta through a connection like it.
- Skill
- A folder of instructions an AI app reads so it knows how to use Bolta well. It does not connect by itself: install it with
npx skills add boltaai/bolta-skills --skill boltanext to the connection. - Plugin
- A bundle that brings the connection and the skill in one install, where the app supports plugins. Claude Code has one, added with its plugin marketplace commands.
- API key
- A
bolta_sk_key you create in Settings, sent as a Bearer header. It carries the permissions you choose, which suits apps you configure by hand or anything that runs unattended.
Setup for MCP Server is only partly confirmed. See what is and is not confirmed. Last checked 2026-11-21.
MCP server, REST API and BoltaClaw are three routes
The MCP server lets an AI app call Bolta for you, with sign-in and brand ticking. The Bolta REST API is for code you write yourself. BoltaClaw is a separate runtime. If your app has its own page here, such as Claude, Cursor or Codex, use that page for exact steps.
Other AI agents that post through Bolta
Every agent below connects to the same Bolta workspace and follows the same approval rules.
- ChatGPTOpen Bolta in ChatGPT, sign in
- OpenAI dotsAlways-on ChatGPT agents
- ClaudeCustom connector, one sign-in
- Claude DuetCarries your Claude connectors over
- Claude CoworkPlugin and connector on your desktop
- Claude CodeTwo plugin commands
- Codexcodex mcp add, then sign in
- CursorOne mcp.json entry
- GeminiGemini CLI extension
- OpenClawSkills and MCP for your gateway
- Hermes AgentMCP server in the Hermes config
- Grok BotCustom connector in xAI's agent
- Grok Buildgrok mcp add
- DeepSeekThrough the Bolta MCP link
- Kimi K3Kimi Code with the Bolta MCP server
- MuseMeta's agent, Muse Code and connectors
- ManusConnector with an API key
- CueA personal agent that posts for you
- PerplexityResearch there, draft in Bolta
- Perplexity ComputerRemote MCP connector
- nanoclawRun it from WhatsApp or Telegram
- PaperclipConnector for your agent company
What MCP Server can do through Bolta
The jobs Bolta's agents cover, each with its own page. Your AI app can ask for drafts, plans and reports in the same areas. Every post still waits for your yes.
Frequently asked questions
Short answers about using MCP Server with Bolta.
- What is an MCP server, and do I need one to use Bolta with an AI app?
- An MCP server is how an AI app calls another service in a standard way. You do not run one yourself. Bolta hosts it, and you only add its address to your AI app.
- What is Bolta's MCP server address?
- It is https://mcp.bolta.ai/mcp. It is a remote server over Streamable HTTP. If your app asks for a type, choose HTTP.
- Do I need an API key, or can I just sign in?
- Sign in if your app offers it, because the browser route lets you tick brands and keeps posts on your review list. Fall back to a key when the app has no connect button but accepts a header.
- Which AI apps can connect to Bolta over MCP?
- Any app that supports remote MCP servers over HTTP can try it. Bolta has setup pages for Claude, ChatGPT, Cursor, Codex, Gemini, Grok Build and others. Bolta has not tested every app end to end, so those pages say what is confirmed.
- My app only supports local (stdio) MCP servers. Can I still use Bolta?
- Not directly, since Bolta's server is remote. Update the app and look for a Remote, HTTP or URL option. If there is none, the REST API or an automation tool such as Zapier, Make or n8n is the other way in.
- Why can my AI only see some of my brands?
- Bolta gives a connection the brands you ticked when you signed in, within a single organization. To add another brand, remove Bolta from your app, connect again and tick it this time.
- Can the AI post without asking me?
- It should not. Drafts save freely, while approving, scheduling and publishing wait for your yes to that exact post. Your role and Safe Mode apply on top. An API key you create acts as you, so give it only the permissions it needs.
- How is the MCP server different from the Bolta REST API or the BoltaClaw CLI?
- The MCP server lets an AI app call Bolta on your behalf. The REST API is for code you write yourself. BoltaClaw is a separate runtime with its own page.
- How long does a sign-in last?
- About 60 days per Bolta's guides, and they usually renew without you doing anything. If a call says Invalid or expired, disconnect Bolta in your app and sign in again.
- Is it free, and what does it cost to use?
- The connection is Bolta's hosted server, and this page cannot confirm what applies to your plan. Check Bolta's pricing page for your plan and for what drafts and posts use.
- Do I need the Bolta skill as well as the server?
- No. The skill is optional written guidance on using Bolta's tools in a sensible order. The tools are available without it, and it only helps in apps that read a skills folder.
- Which social networks can the AI post to through MCP?
- Whichever networks you have connected in Bolta, including LinkedIn, X, Instagram, Facebook, Threads and Bluesky. If one is not connected, get-connect-link returns a link for you to connect it in the browser. Posting still waits for your yes.
If something does not work
Quick fixes for the common snags.
- My app never opens a sign-in window, or the sign-in loops.
- Your app may not support OAuth for this kind of server. Create an API key in Settings, API Keys, and use the Bearer header instead. If it loops, remove Bolta from the app, add it again and sign in again.
- Bolta connects, but one of my brands is missing.
- A connection reaches only the brands ticked at sign-in. Remove the Bolta server in your app, add it again and tick the missing brand. A new brand always needs a reconnect.
- The AI asks which brand to use, or a call asks for a workspace_id.
- You have several brands on one connection. Name the brand in your prompt, for example: for Acme, show my review list. Bolta then passes that brand's workspace_id on each call.
- I see Invalid or expired API key, API key inactive or Not authenticated.
- These point to a lapsed connection, and repeating the call will not fix it. Reconnect Bolta from your app's server list. With a key, make a new one under Settings, API Keys and swap it into your config.
- A tool fails with 403 or Approval required.
- A 403 means your role or the key's permissions rule that action out, such as saving posts with a key that lacks posts:write. Approval required is a refusal by design, and nothing goes out until you say yes to the exact post. Do not ask the AI to route around it.
- The config file is ignored, or the server never starts.
- Check that the JSON is valid with no trailing commas and that the type is http. The top key is servers in VS Code and mcpServers in many other apps. Check your app's MCP log for the real error.
Ready to schedule social media posts with MCP Server?
Connect MCP Server and ask for your first draft. Nothing goes out until you say yes.