Turn your repo's release notes into social drafts, from the terminal

Schedule social media posts from Claude Code

Claude Code is Anthropic's coding agent for the terminal. Install the Bolta plugin with two slash commands and it can turn a changelog, README or release note already in your repo into LinkedIn and X drafts in your brand voice. Drafts wait for you: only your yes approves, schedules or publishes anything.

  • Two slash commands and a browser sign-in. No key to copy.
  • Drafts come from the changelog and notes already in your repo.
  • Nothing posts until you approve it.

Nothing is approved, scheduled or published until you say yes.

Partly confirmed, see what is and is notChecked 2026-11-21

Two slash commands, then a browser sign-in. You tick the brands Claude Code may reach.

Claude CodeBolta connected
You

Read the top entry in CHANGELOG.md and save one LinkedIn draft and one X draft for my review

Illustration of the reply: Bolta returns a draft showing the connected account and the scheduled time, with Approve, Edit and Reject actions.

Illustration. Your drafts show your real text, account and time.
Connect, then ask

Connect Bolta to Claude Code in two steps

  1. 01

    Install the plugin

    In the Claude Code prompt, run /plugin marketplace add boltaai/bolta-skills, then /plugin install bolta@bolta-marketplace.

  2. 02

    Sign in, then ask

    Run /mcp, select Bolta and sign in in your browser. Back in the chat, type: set me up.

What is and is not confirmed

Read this before you set up Claude Code

  • Confirmed in Claude Code's official docs: remote HTTP MCP servers with browser sign-in through /mcp, skills as SKILL.md folders, and plugin marketplaces added from a GitHub repo.
  • Bolta's own plugin is the most tested path. A full real-world run on every setup is still beta (plugin v0.5.3).
  • Not confirmed here: the exact minimum Claude Code version for plugin marketplaces (the Bolta plugin README names 2.1.295 or later only as an example), and running Bolta end to end from claude -p in scripts. Claude Code's docs say headless runs cannot do the browser sign-in. The API key header route follows Claude Code's documented --header option but was not run end to end.
Behind the prompt

What Claude Code does when you ask for a post

Claude Code reads your files. Bolta supplies the voice, the rules and the places a draft can go. The tools below are the real Bolta tools it calls.

  1. 01

    Read the source in your project

    Claude Code opens the file you named, such as CHANGELOG.md or a README section. This step is Claude Code's own, and Bolta is not involved yet.

  2. 02

    Find which brand to use

    It lists the brands you ticked at sign-in. With more than one, it asks which you mean instead of picking for you.

    list-workspaces

  3. 03

    Check connected accounts

    It reads the networks connected to that brand, so it will not draft for one you have not connected.

    list-accounts

  4. 04

    Load your voice

    It pulls your saved voice and business details before writing a word.

    get-voice-context

  5. 05

    Read the network's rules

    It checks limits such as length and media needs for the network, so the draft fits.

    get-posting-rules

  6. 06

    Save the draft and show it

    Each draft is saved, free, as an AI draft and printed in the terminal in full. Nothing is scheduled.

    save-post

  7. 07

    Wait for your decision

    Say what to change, or say yes. Only a yes lets it approve or publish, and Bolta can still refuse if your role or the brand's settings do not allow it.

    approve-many-posts

Setup

Set up Claude Code

Connect once. Everything below works from Claude Code afterwards.

  1. 01

    Start Claude Code and find its prompt

    Open a terminal and start Claude Code. The next two commands are typed into the Claude Code prompt, not into the terminal itself.

  2. 02

    Add the Bolta marketplace

    Run /plugin marketplace add boltaai/bolta-skills. A marketplace is a list of plugins Claude Code can install, and boltaai/bolta-skills is the GitHub repository that holds it. Run /plugin and look for bolta-marketplace to check it worked.

  3. 03

    Install the Bolta plugin

    Run /plugin install bolta@bolta-marketplace and pick user scope unless you know you want another. The plugin brings the connection to https://mcp.bolta.ai/mcp and the Bolta skill together. If the summary says to run /reload-plugins, run it.

  4. 04

    Sign in from /mcp

    Run /mcp, select Bolta and choose sign in. Your browser opens on bolta.ai. Sign in, pick your organization and tick the brands this connection may reach. There is no key to copy.

  5. 05

    Paste the address if the browser errors

    If the browser shows a connection error at the end, copy the full address from the address bar and paste it into the prompt Claude Code shows. Then go back to the terminal.

  6. 06

    Confirm Bolta is connected

    Run /mcp again. Bolta should show as connected. If it still asks you to sign in, repeat the sign-in step and finish the browser page before returning.

  7. 07

    Say set me up

    Type set me up in the chat, or run /bolta:bolta. Claude reads your brands and asks for your site, your voice or which accounts to connect. Drafts save freely. Nothing goes out until you say yes.

  8. 08

    Check it works without changing anything

    Ask: Which Bolta brands can you see, and which social accounts are connected to each? Do not change anything. Claude should list the brands you ticked and their networks, and draft nothing.

  9. 09

    Already connected Bolta yourself? Add only the skill

    If you added Bolta earlier with claude mcp add or a connector, skip the plugin. Run npx skills add boltaai/bolta-skills --skill bolta in a terminal to add just the skill. Optionally run /plugin install bolta-checks@bolta-marketplace for a check before anything public.

Connect

Connect Claude Code to Bolta

Two slash commands, then a browser sign-in. You tick the brands Claude Code may reach.

Connection methods

Which Bolta connection methods work in Claude Code

Based on Claude Code's own documentation and Bolta's guide. Not confirmed means we have not run it end to end.

Which Bolta connection methods work in Claude Code
MethodWith Claude CodeHow
Plugin from the bolta-skills marketplaceWorks/plugin marketplace add boltaai/bolta-skills, then /plugin install bolta@bolta-marketplace. It brings the connection and the skill. Still beta (plugin v0.5.3).
Hosted MCP with browser sign-inWorksAdd https://mcp.bolta.ai/mcp with claude mcp add --transport http, then sign in from /mcp. Claude Code documents this route for remote servers.
Skill only via npx skills addWorksnpx skills add boltaai/bolta-skills --skill bolta. Use it when Bolta is already connected, so you keep one entry.
MCP with an API key headerNot confirmedClaude Code documents --header and .mcp.json headers, and Bolta accepts keys starting with bolta_sk_. We have not run it end to end. A pasted key skips the AI-draft hold.
Headless runs with claude -pNot confirmedClaude Code's docs say these runs cannot do the browser sign-in, so sign in from an interactive session first. Bolta is untested from claude -p or CI.
Bolta REST API called from scriptsNot confirmedThe REST API exists and uses the same keys. We have not tested driving it from inside a Claude Code session.
Capabilities

What you can run in Bolta from Claude Code

Each row is an area of Bolta, with the real tools behind it.

  • Draft from your repo

    Changelog, README and release notes become drafts in your voice and the network's rules, saved without publishing.

    get-voice-contextget-posting-rulessave-post

  • Write a batch of drafts

    Ask for several posts at once, such as a week of build-in-public notes, and review them together.

    bulk-create-postslist-workspace-posts

  • Review without a browser tab

    See what is waiting, approve after you say yes, or reject with your own reason so Bolta learns your taste.

    list-inbox-itemsapprove-many-postsreject-post

  • Send to a teammate for sign-off

    Route drafts to a named reviewer on the brand instead of approving them yourself.

    list-workspace-memberssubmit-for-review

  • Plan repeating work

    Describe a routine in words, read the plan back, and save it switched off until you say yes to turn it on.

    planconfirm-planactivate-routine

  • Read results

    Check how recent posts and accounts performed so the next draft is informed by it. Read only.

    list-account-insightsget-account-analytics

A realistic session

A release note becomes two drafts in the terminal

An illustration of how a session can run. The wording and results are invented.

IllustrationNot real output
  1. You

    We just cut v2.4. Read the top entry in CHANGELOG.md and draft a LinkedIn post and an X post. Brand: our main one.

  2. Claude Code

    I read the v2.4 entry. I will check the brand and your voice first.

  3. Tool call
    list-workspaces

    Finds the brands this sign-in reaches.

  4. Tool call
    list-accounts

    Confirms LinkedIn and X are connected to the brand.

  5. Tool call
    get-voice-context

    Loads the saved voice for the brand.

  6. Tool call
    get-posting-rules

    Reads the limits for LinkedIn and X.

  7. Claude Code

    The entry lists two fixes and one new export option. I will not claim the export works for every plan, since the changelog does not say so. Saving both as drafts now.

  8. Tool call
    save-post

    Saves the LinkedIn draft. Nothing scheduled.

  9. Tool call
    save-post

    Saves the X draft. Nothing scheduled.

  10. Claude Code

    Both are saved as drafts. The X version is shorter and leads with the export option. Here is the exact text of each. Do you want changes, or a different angle?

  11. You

    Make the LinkedIn one less salesy and mention the fix that took us a month.

  12. Claude Code

    I am editing the LinkedIn draft in place.

  13. Tool call
    save-post

    Edits the existing LinkedIn draft. It stays a draft.

  14. Claude Code

    Updated the LinkedIn draft. It is still only a draft. Tell me when you are ready, and I will show the final text and account before asking for your yes.

Which route

Plugin, skill only, or plain MCP

All three reach the same Bolta. The difference is what Claude Code installs for you.

Plugin (recommended)

Choose this if you have not connected Bolta before.

Two slash commands add the connection and the Bolta skill together, then /mcp signs you in. It is the path Bolta tests most.

Skill only

Choose this if Bolta is already connected in Claude Code.

Run npx skills add boltaai/bolta-skills --skill bolta. It adds the skill without a second connection, so /mcp keeps one Bolta entry.

Plain MCP

Choose this if you manage connections by hand or in a team file.

Claude Code adds remote servers with claude mcp add --transport http and the address https://mcp.bolta.ai/mcp, then /mcp signs you in. You get the connection without the skill, so add the skill too.

Use cases

What can Claude Code do with Bolta?

  • Turn the newest CHANGELOG.md entry into a LinkedIn and an X draft
  • Draft launch posts from a README section before you push a release
  • Summarise what a merged pull request changed in plain words for customers
  • Draft a week of build-in-public posts in your own voice between coding sessions
  • Review what Bolta has queued without leaving the terminal
  • Set up a weekly routine that drafts posts from your product updates for your review
The connection

What is the Bolta MCP?

The server Claude Code talks to when it works with Bolta.

MCP, the Model Context Protocol, is the open standard that lets an AI app call tools in another product. Bolta runs a hosted MCP server at https://mcp.bolta.ai/mcp. Your AI app discovers its 67 tools and calls them for you: list your brands, save a draft, plan a routine, read results.

One connection is one organization. You tick the brands the app may reach, and every call is checked against your role, so the app can never do more in Bolta than you can. Approving, scheduling and publishing need your yes.

  • Brands & accounts6 tools

    The brands this connection reaches, who works on them and who can approve, their approval settings, connected social accounts, and each platform's posting rules.

    list-workspaces, list-workspace-members, set-brand-approval, list-accounts, get-connect-link, get-posting-rules

  • Posts9 tools

    Save a draft or edit a post with save-post, then publish it now or at a time with publish-post after the user says yes.

    list-workspace-posts, get-post, save-post, publish-post, delete-post, bulk-create-posts, create-wordpress-blog-post, list-recently-deleted, restore-deleted

  • Review4 tools

    Everything waiting for a yes: submit drafts to the team or send them to a named person for approval, approve one or many, reject with a reason, and work the inbox of routine and campaign drafts.

    list-inbox-items, submit-for-review, approve-many-posts, reject-post

  • Plans6 tools

    Have Bolta plan a routine or a campaign the way its own chat does, change it, then save it on the user's yes.

    plan, plan-routine, plan-campaign, recommend-routines, revise-plan, confirm-plan

  • Routines10 tools

    Work that repeats and runs in Bolta even with the app closed.

    list-routine-templates, list-routines, get-routine, create-routine, update-routine, activate-routine, pause-routine, archive-routine, run-routine-now, list-routine-runs

  • Campaigns6 tools

    One to four weeks of posts about one thing: a launch, an event, a season.

    list-content-campaigns, get-content-campaign, create-content-campaign, update-content-campaign, analyze-content-campaign-source, set-content-campaign-status

  • Team versions4 tools

    One idea written as one post per person on the team, each in their own voice.

    plan-team-posts, update-team-post-plan, generate-team-post-drafts, get-team-post-plan

  • Voice & business8 tools

    The brand's voice and business facts, and writing in that voice.

    get-voice-context, get-voice-profile, create-voice-profile, update-voice-profile, list-business-dna, extract-business-dna, update-business-dna, voice-generate

  • Suggestions2 tools

    What Bolta suggests changing, for a routine or the whole brand, from what people approved, edited and rejected.

    list-suggestions, decide-suggestion

  • Replies10 tools

    Find conversations worth joining, draft replies in the brand voice, and send them once the user says yes.

    search-engagement-opportunities, list-engagements, get-social-content, draft-engagement-reply, draft-inbound-reply, publish-engagement-reply, reply-to-social-content, react-to-social-content, send-outreach-reply, update-outreach-reply

  • Results2 tools

    How posts and accounts are performing.

    list-account-insights, get-account-analytics

Try it

What you can ask from the terminal

Replies are illustrative. Real ones depend on your brands and your repo.

You in Claude Code

Read the top entry in CHANGELOG.md and save a LinkedIn draft and an X draft for my review.

Bolta

I read the v2.4 entry and checked your posting rules. I saved two drafts in Bolta, one for LinkedIn and one for X, both marked as AI drafts. Nothing is scheduled. Here is the exact text of each. Tell me what to change, or say yes to approve.

Drafts saved. Waits for your yes.

get-voice-context, get-posting-rules, save-post

You in Claude Code

What is waiting for my approval in Bolta right now?

Bolta

You have drafts waiting in your inbox, with the account and text for each. I have not approved or changed any of them. Tell me which to approve, and I will show you the exact text first.

Read only. Nothing changed.

list-inbox-items

You in Claude Code

Which Bolta brands can you see, and which accounts are connected to each? Do not change anything.

Bolta

These are the brands you ticked when you signed in, with their connected networks listed under each. If a brand is missing, run /mcp, pick Bolta and sign in again to tick it.

Read only. Nothing changed.

list-workspaces, list-accounts

You in Claude Code

Set up a routine that drafts a post from our product updates every Monday, and show me the plan first.

Bolta

Here is the plan: what it will draft, how often, and where the drafts go. A routine runs in Bolta, so it cannot read files on your machine. Tell me where the updates are published and I will show whether Bolta can use that source. The routine saves switched off. Say yes to confirm the plan, and say yes again separately to turn it on.

Plan shown. Waits for your yes.

plan, confirm-plan

You in Claude Code

Summarise what the last merged pull request changed in two plain sentences for customers, then save it as a LinkedIn draft.

Bolta

I read the pull request description and the changed files, using git or the GitHub CLI if it is installed here, then wrote a short customer-facing summary. It is saved in Bolta as a draft and shown below in full. If a detail in the summary is a guess on my part, I flag it so you can correct it before anything moves.

Draft saved. Waits for your yes.

get-voice-context, get-posting-rules, save-post

You in Claude Code

Which of my recent posts got the most engagement, and what should I write about next? Read only.

Bolta

I looked at your recent posts and account results and ranked them from what Bolta has recorded. I suggest topics from the top performers and save nothing. Numbers are only as fresh as Bolta's latest sync, so a very new post may show little.

Read only. Nothing changed.

list-workspace-posts, list-account-insights, get-account-analytics

You in Claude Code

Send the three drafts you just saved to our reviewer for approval, and do not publish anything.

Bolta

I looked up who on the brand can receive approval requests and listed them for you. Tell me which person, and I will send the drafts to them for review. Sending for review does not publish. The reviewer decides.

Waiting on you to pick a reviewer.

list-workspace-members, submit-for-review

Networks Bolta publishes to

  • LinkedIn
  • X
  • Instagram
  • Facebook
  • Threads
  • Bluesky
  • Mastodon
  • Reddit
  • TikTok
  • YouTube
  • Pinterest

YouTube and Pinterest are in beta on the Team plan. A draft can only go to a network you have connected in Bolta.

When the terminal is closed

What keeps running without Claude Code open

Claude Code works while a session is open. Routines live in Bolta, so they do not depend on it.

  • A routine you confirm and switch on runs in Bolta on its schedule, even with Claude Code closed.
  • Reading the repo, drafting from it and chatting happen only while a Claude Code session is open.
  • Routine output lands in Bolta's inbox for review. Open Claude Code later and list it with list-inbox-items.
  • You can check what a routine did with list-routine-runs, or switch it off with pause-routine.

A routine is saved switched off, and turning it on is a separate yes. Post routines default to asking you first, so their drafts wait for review. A routine can be set to post without asking only where the brand's automation settings allow it, so check the setting before you switch one on.

What is different here

Turn your repo into posts

Claude Code already reads your files, so the source for a post is often sitting in the project.

Point it at a changelog, a README section, release notes or a diff summary and ask for drafts. It uses your Bolta voice and your posting rules, saves the drafts to Bolta and waits.

Claude Code reads the files itself, so there is no copy and paste between your editor and a scheduling tool.

  • Name the file, for example CHANGELOG.md, so it does not guess.
  • Say which brand when you ticked more than one.
  • Ask for drafts only. Approval stays a separate yes.

Plugin, skill or raw MCP: avoid two Bolta entries

The plugin installs the connection and the skill. If you already added Bolta yourself, installing the plugin on top leaves two Bolta entries on one organization. In that case add only the skill with npx skills add boltaai/bolta-skills --skill bolta.

The optional bolta-checks plugin shows a check before anything public or final, such as posting, replying, approving, scheduling, running a routine now or starting a campaign. Saving drafts needs no check. On Windows it needs Git for Windows, because the checks use sh and awk and every Bolta save is blocked without them.

API keys, scripts and team files

Claude Code's docs describe adding a static key with --header "Authorization: Bearer <token>", or putting it under headers in .mcp.json with ${VAR} expansion. Bolta supports API keys, so that route should work, but it was not run end to end for this page.

Prefer sign-in. Posts from a sign-in are held as AI drafts for review, and a pasted Bolta API key skips that hold.

For scripts, Claude Code's docs say claude -p runs cannot perform the browser sign-in, so sign in first from an interactive session with /mcp. We have not run Bolta end to end from claude -p or CI, so test it yourself and keep a person in the loop for approval.

Scopes: user, project and local

Claude Code adds servers at local scope by default, which is just you in the current project. User scope follows you across all your projects. Project scope writes a .mcp.json file in the project that can be committed so a team shares a setup, and Claude Code asks each person to approve it in an interactive session. Plugins install at user, project or local scope too. Each person still signs in to Bolta as themselves, and the sign-in follows their own Bolta role.

One connection is one organization. Agencies tick their client brands in the same connection. Several organizations need one connection each.

Optional guard

The bolta-checks plugin: a pause before anything public

Saving a draft is harmless. Posting, replying, approving or scheduling is not, so some people want a second stop in the terminal.

bolta-checks is a separate plugin in the same marketplace. Install it with /plugin install bolta-checks@bolta-marketplace. It shows a check before the public or final Bolta actions: posting, replying, approving, scheduling, running a routine now or starting a campaign. Plain draft saves pass through without a prompt.

It is optional and it sits on top of Bolta's own rules, which already refuse an action your role does not allow. If you are on Windows, install Git for Windows first. The checks need sh and awk, and without them every Bolta save is blocked.

  • Install it only after the main plugin works.
  • Remove it with the plugin manager if saves start failing on Windows.
  • It adds a pause. It does not change who is allowed to approve.
For developers

Build in public without leaving your editor session

Most developers skip posting because writing it means switching context. Here the context is already in front of the agent.

Between tasks, ask Claude Code to describe what you shipped since your last post and draft it in your voice. It can read the commit messages, the changelog and the files you touched. It does not know why a change mattered to a customer unless you tell it, so add one line of intent to the prompt.

Ask for two or three angles on the same change, for example the problem, the fix and a lesson, and pick one. Saving drafts is free, so keep all of them until you choose and delete the angles you do not use.

  • Give the intent in one sentence: who benefits and why.
  • Ask it to flag any claim it cannot back from the repo.
  • Name the brand and the network so the right rules apply.
A worked routine

A release-day habit that takes five minutes

This is a suggested sequence, not a built-in feature. Every step stays a draft until you say yes.

Before you tag the release, ask Claude Code to read the top CHANGELOG.md entry and save one draft per network you use. Read each draft in the terminal. If a draft overstates what shipped, say what to cut and ask again.

When the release is live, come back and say yes to the draft you like. Claude should show the exact text and the account first. If you would rather a teammate signs off on it, send it for review instead of approving it yourself.

  • Draft before the release, approve after you have checked the release is real.
  • Keep screenshots as public links, since media goes in by link.
  • Never let a draft name a feature the changelog does not mention.
Safety

What Claude Code cannot do without you

Claude Code connects as: Plugin from the bolta-skills marketplace, or claude mcp add.

  • Drafts are free, finals need your yes

    Claude Code 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 Claude Code 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 Claude Code 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.

Terms

The words behind Claude Code and Bolta

For Claude Code: Plugin from the bolta-skills marketplace, or claude mcp add, signing in with Sign in (OAuth) from /mcp.

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 Claude Code 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 bolta next 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.
Read the MCP docs

Setup for Claude Code is only partly confirmed. See what is and is not confirmed. Last checked 2026-11-21.

Not the same thing

Claude Code is not Claude, Claude Cowork or Claude Duet

Claude Code works in a terminal, next to your files and git history, so it suits developer-led posting. Claude is the chat app, and Cowork and Duet have their own pages with their own setup. The Bolta account and approval rules are the same in all of them.

FAQ

Frequently asked questions

Short answers about using Claude Code with Bolta.

What is Claude Code, and how is it different from Claude or Claude Cowork?
Claude Code is Anthropic's coding agent that runs in your terminal and reads your project files. Claude is the chat app, and Cowork and Duet have their own Bolta pages. Bolta behaves the same in all of them: drafts are free and nothing publishes without your yes.
How do I connect Bolta to Claude Code?
Run /plugin marketplace add boltaai/bolta-skills, then /plugin install bolta@bolta-marketplace, then /mcp and sign in. Your browser opens on bolta.ai and you tick the brands Claude Code may reach.
Do I need an API key?
No. Signing in from /mcp is the recommended route and needs no key. Posts from a sign-in are held as AI drafts on your review list, while a pasted API key skips that hold.
Plugin, skill or plain MCP: which should I use?
Use the plugin if you have not connected Bolta before, since it brings the connection and the skill together. If Bolta is already connected, add only the skill. Installing both leaves two entries on one organization.
Can Claude Code publish without my approval?
Not by design. Bolta's rule is that nothing is approved, scheduled or published until you say yes, and Claude should show you the exact text first. Posts from a sign-in are held as AI drafts on your review list, and Bolta refuses an action your role or settings do not allow.
Can I use Bolta from a script or CI with Claude Code?
Claude Code documents a --header option and .mcp.json headers for static keys, and Bolta supports API keys. Its docs also say claude -p runs cannot do the browser sign-in, so you would sign in first from an interactive session. We have not run Bolta end to end from claude -p or CI, so test it yourself and prefer sign-in for anything a person reviews.
Claude Code does not see the Bolta tools. What should I check?
Run /reload-plugins, then /mcp, and make sure Bolta shows as connected rather than needing sign-in. If you see two Bolta entries, remove one.
Which brands can Claude Code reach?
Only the brands you ticked when you signed in. If you ticked more than one, name the brand in your request. To add one later, run /mcp, pick Bolta and sign in again.
Which social platforms can it post to?
Any network connected to your Bolta brand, including LinkedIn, X, Instagram, Facebook, Threads and Bluesky. It cannot post to an account you have not connected in Bolta. Instagram and Pinterest need an image or video, and TikTok and YouTube need a video.
What can it not do?
It cannot do more than your Bolta role allows. A viewer connection is read-only and a client reviewer cannot connect at all. Media goes in as a public link, since uploading from chat is not available.
Does the bolta-checks plugin work on Windows?
It needs Git for Windows installed first, because the checks call sh and awk. Without them every Bolta save is blocked, so install Git for Windows and restart Claude Code, or uninstall bolta-checks.
Can my whole team share one Bolta setup through the repo?
Claude Code's project scope writes a .mcp.json file you can commit, and each person approves it and signs in as themselves. Their Bolta role decides what they can do, so a shared file never shares one person's permissions.
Troubleshooting

If something does not work

Quick fixes for the common snags.

The sign-in page opens again and again, or Bolta stays on not signed in.
Run /mcp, pick Bolta and sign in once more, and finish the browser page all the way before going back to the terminal. If the browser shows a connection error, paste the full address from its address bar into the prompt Claude Code shows.
Claude Code does not see the Bolta tools.
Run /reload-plugins if the install summary asked for it, then run /mcp and confirm Bolta shows as connected. A plugin installed from the terminal with claude plugin install loads the next time you start Claude Code.
I see two Bolta entries in /mcp.
You installed the plugin and also added Bolta yourself. Keep one and remove the other. If you keep your own connection, add only the skill with npx skills add boltaai/bolta-skills --skill bolta.
A brand I expect is missing.
It was not ticked at sign-in, or you added it afterwards. Run /mcp, pick Bolta, sign in again and tick it. If you ticked several brands, name the one you mean in your request.
Claude says the sign-in expired or you are not authenticated.
Run /mcp, pick Bolta and sign in again. Sign-ins last 60 days and normally renew themselves. Claude should not retry in a loop.
Every Bolta save is blocked on Windows.
You have bolta-checks installed and no sh or awk. Install Git for Windows and restart Claude Code, or uninstall bolta-checks.

Ready to schedule social media posts with Claude Code?

Connect Claude Code and ask for your first draft. Nothing goes out until you say yes.