---
title: "MCP Server integration with Bolta"
description: "Add Bolta to any AI app that supports remote MCP servers: the address is https://mcp.bolta.ai/mcp. Sign in or use an API key, then draft social posts that wait for your yes."
canonical_url: "https://bolta.ai/integrations/mcp"
markdown_url: "https://bolta.ai/integrations/mcp.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# MCP Server integration with Bolta

Source: https://bolta.ai/integrations/mcp
Last updated: 2026-11-21

Add Bolta to any AI app that supports remote MCP servers: the address is https://mcp.bolta.ai/mcp. Sign in or use an API key, then draft social posts that wait for your yes.

## Summary

One address for any MCP client: https://mcp.bolta.ai/mcp

## Who this is for

- Developers
- Automation teams
- AI-assisted marketing teams

## Core capabilities

- 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

## Limitations and boundaries

- 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.
- Integration availability depends on current APIs, authentication, scopes, and account permissions.
- Generated content can be incorrect and should be reviewed before publication.
- Availability depends on the current Bolta plan, connected network, account permissions, and integration coverage.
- Current prices and plan limits must be verified on the Bolta pricing page.

## 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.

## 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.

## 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.

## 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.

## 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.

## 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.

## 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.

## 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.

## 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.

## 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: VS Code, .vscode/mcp.json; Shape: servers, then bolta with type http and url | Where: Cursor, mcp.json; Shape: mcpServers, then bolta with url | Where: Gemini CLI, gemini-extension.json; Shape: httpUrl | Where: Codex CLI, ~/.codex/config.toml; Shape: \[mcp\_servers.bolta\] with url | Where: Grok Build; Shape: 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 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.

## 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.

## 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.

## Relevant links

- [Related page: /integrations](https://bolta.ai/integrations)
- [Related page: /integrations/claude](https://bolta.ai/integrations/claude)
- [Related page: /integrations/chatgpt](https://bolta.ai/integrations/chatgpt)
- [Related page: /integrations/cursor](https://bolta.ai/integrations/cursor)
- [Related page: /integrations/codex](https://bolta.ai/integrations/codex)
- [Related page: /integrations/gemini](https://bolta.ai/integrations/gemini)
- [Related page: /integrations/grok-build](https://bolta.ai/integrations/grok-build)
- [Related page: /integrations/vscode](https://bolta.ai/integrations/vscode)
- [Related page: /integrations/windsurf](https://bolta.ai/integrations/windsurf)
- [Related page: /integrations/openclaw](https://bolta.ai/integrations/openclaw)
- [Related page: /integrations/boltaclaw](https://bolta.ai/integrations/boltaclaw)
- [Bolta pricing](https://bolta.ai/pricing)

## Supporting sources

- [MCP Server official website](https://modelcontextprotocol.io/)
