Model Context Protocol

Run your social media operation from the AI tools you already use.

Connect ChatGPT, Claude, Cursor, or your own agent to Bolta. Create, review, schedule, publish, and analyze content without rebuilding your workflow in every interface.

ChatGPTClaude DesktopCursorContinueCustom agents
MCP client configuration
Live
{
  "mcpServers": {
    "bolta": {
      "url": "https://mcp.bolta.ai/mcp",
      "headers": {
        "Authorization": "Bearer bolta_sk_your_api_key"
      }
    }
  }
}
Streamable HTTP · https://mcp.bolta.ai/mcp
58
MCP tools
2
authentication paths
One workspace
shared context and permissions
The full operating surface

One protocol. Your entire content system.

MCP gives your AI client the same governed building blocks available inside Bolta. The interface changes; your brand context, connected accounts, review rules, and history stay together.

12 post tools

Create and publish

Draft, update, schedule, publish, and inspect social posts across your connected accounts.

10 brand tools

Use your brand voice

Generate copy with the same Voice Profiles and Business DNA your Bolta workspace already uses.

16 agent tools

Run your AI team

Hire specialized agents, configure recurring jobs, trigger runs, and inspect the work they produce.

6 review tools

Keep approval in the loop

Submit drafts, list reviews, approve work, or reject it before anything moves into publishing.

6 analytics tools

Read performance

Pull cross-platform analytics, account insights, inbox items, and the signals that guide the next action.

8 workspace tools

Operate the workspace

Discover workspaces, accounts, capabilities, social buckets, and the boundaries available to the caller.

Natural-language workflows

Ask for the outcome. Bolta handles the operations.

Your client discovers the right tools and calls them in sequence. You stay in the conversation while Bolta keeps the workspace, permissions, review state, and publishing destinations coherent.

Repurpose + review

Turn this article into a week of posts, then submit every draft for review.

Sent from your MCP client
Schedule audit

Show me what is scheduled this week and flag anything that is still waiting for approval.

Sent from your MCP client
Agent operation

Run my Content Agent now, then summarize the drafts it created.

Sent from your MCP client
Analytics loop

Compare performance across our accounts and suggest the next three posts.

Sent from your MCP client
Connect your way

OAuth when you want simplicity. API keys when you want control.

Bolta supports interactive sign-in and permission-scoped credentials, so the same MCP server works for a personal ChatGPT connection, a desktop client, or an unattended custom agent.

ChatGPT + OAuth clients

Sign in and choose a workspace

No key to paste. Bolta uses OAuth with PKCE, then limits the connection to the workspace and role you authorize.

Claude, Cursor + custom agents

Create a permission-scoped API key

Add the server URL and a Bolta key to your MCP configuration. Choose only the permissions that client actually needs.

Governed by design

Give agents useful access, not unlimited access.

MCP should make your system easier to operate without making it harder to trust. Bolta applies the same workspace boundaries and permissions whether an action begins in the dashboard or an AI conversation.

  • OAuth connections are scoped to the workspace you choose and limited by your Bolta role.
  • API keys use explicit permissions, so each client receives only the access it needs.
  • The MCP server is stateless between calls and authorizes every action like a normal API request.
  • Approve-first workflows let your AI client prepare the work without publishing it automatically.
Straight answers

Before you connect an AI client.

What is the Bolta MCP server?

The Bolta MCP server connects MCP-compatible AI clients to your Bolta workspace. It exposes tools for posts, accounts, brand voice, agents, reviews, analytics, and workspace operations.

Which AI clients work with Bolta MCP?

Bolta supports ChatGPT, Claude Desktop, Cursor, Continue, and custom agents that speak MCP over Streamable HTTP with Bearer authentication.

Do I need an API key?

Not always. ChatGPT and other connector-style clients can use OAuth. Hand-configured clients such as Claude Desktop or Cursor can connect with a permission-scoped Bolta API key.

Can an AI client publish without my approval?

Only if you grant the required permissions and configure that workflow. You can keep work approve-first so drafts must be reviewed before scheduling or publishing.

Where are the setup instructions and tool reference?

The complete connection guide, authentication options, client configuration, and current tool list are available in the Bolta MCP documentation.

Open the complete MCP documentation
Bolta, wherever you work

Put your content operation one conversation away.

Connect your preferred AI client, keep Bolta as the system of record, and move from idea to reviewed, published work without context switching.

Bolta MCP Server — Run Social Media from Your AI Client | Bolta