---
title: "VS Code integration with Bolta"
description: "Add Bolta's MCP server to VS Code and its AI chat can draft posts in your brand voice, check what is waiting for review, and read analytics. The same address works in other apps that support MCP. Nothing goes out until you approve the exact text."
canonical_url: "https://bolta.ai/integrations/vscode"
markdown_url: "https://bolta.ai/integrations/vscode.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# VS Code integration with Bolta

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

Add Bolta's MCP server to VS Code and its AI chat can draft posts in your brand voice, check what is waiting for review, and read analytics. The same address works in other apps that support MCP. Nothing goes out until you approve the exact text.

## Summary

Draft and queue social posts from VS Code's AI chat

## Who this is for

- Developers
- Automation teams
- AI-assisted marketing teams

## Core capabilities

- Turn a release or changelog entry into a LinkedIn or X draft
- Explain a technical change to customers in plain words
- Draft a week of developer-focused posts in your brand voice
- Review and approve what Bolta has queued without leaving the editor
- Check how recent posts performed before you plan the next one

## Limitations and boundaries

- The config and sign-in steps follow Bolta's own guide and VS Code's MCP format. Nobody has run a full draft, review and schedule through VS Code yet.
- Menu names and file locations change between VS Code versions, so check VS Code's MCP docs if a label does not match.
- Bolta's skills repository lists VS Code as not tested.
- 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.

## Check that VS Code can use MCP servers

Use a recent version of VS Code with its AI chat switched on. A workplace policy can limit MCP servers, so ask your admin if the option is missing. Menu names and file locations change between versions, so check VS Code's own MCP docs if a label here does not match.

## Add Bolta to .vscode/mcp.json

In your project folder, create .vscode/mcp.json and add a server named bolta with type http and the URL https://mcp.bolta.ai/mcp. The JSON on the Bolta MCP docs page can be pasted as is. Newer VS Code versions may point new setups at other locations, so the file path can differ for you. The address and the http type stay the same.

## Start the server and sign in

Save the file, then run MCP: List Servers from the Command Palette and start Bolta if it is stopped. If VS Code offers sign-in for remote servers, a browser window opens on Bolta. Sign in and tick the brands this app may reach. If there is no sign-in, create an API key in Bolta under Settings, API Keys, and have VS Code prompt for it as a Bearer header so it never sits in the file. Keep keys out of git.

## Check that Bolta's tools are listed

Open VS Code's chat in agent mode and look for Bolta in the tools list. If it is listed and not switched off, the connection works. Ask which Bolta brands it can see, and it should name the ones you ticked.

## Ask for a draft

Ask the chat for a post. It saves a draft in Bolta and shows you the text. Approve it in Bolta or tell the chat yes.

## What goes in mcp.json

The Bolta entry is small: a key named bolta, a type of http and the address https://mcp.bolta.ai/mcp, all under a top-level servers key. In VS Code, http means Streamable HTTP, which is what Bolta speaks. Other apps name these keys differently (url, serverUrl or httpUrl) and some use mcpServers as the top key. If you copy the entry to another editor, check that editor's docs instead of pasting it unchanged.

## Keeping an API key out of your repo

A key pasted into a committed file is a key shared with everyone who can read the repo. Use VS Code's inputs block so the key is typed once and held outside the file. Create the key in Settings, API Keys. It starts with bolta\_sk\_. Give it only the permissions you need. A key without posts:write cannot save posts. Add an inputs entry with type promptString and password set to true. Reference it as Bearer followed by the input id in the Authorization header. If a key ever lands in git, create a new one and replace the old.

## From changelog to reviewed post

A routine way to use the editor for release communication. 1. Write the changelog first: The chat drafts from text it can read, so a clear entry gives a better post than a vague one. 2. Ask for a draft per audience: Name the audience and network, for example customers on LinkedIn or developers on Bluesky. 3. Check every claim: Compare the draft with the entry. Remove anything the changelog does not say. 4. Approve in Bolta or say yes in chat: Only your yes moves a draft forward. Viewers cannot approve, and client brands may need sign-off.

## Does Bolta publish without my approval?

Not by default. A connected AI app cannot schedule or publish a post that has not been approved. Bolta refuses it or sends it to review, and the chat should show you the exact text first. An API key you create yourself acts as you, so the same care is then up to you and the app. Safe Mode and required client sign-off still apply.

## Is this tested end to end?

Not yet. Nobody has run a full draft, review and schedule through VS Code. Claude Code is the most tested path, and our skills repository lists VS Code and other apps as not tested.

## Will it work in other apps?

Likely, if the app can talk to an MCP server over HTTP. The address is the same, but each app names its config keys differently (url, serverUrl or httpUrl), so check that app's docs. We have not tested every app.

## What can it not do?

Its reach is capped by your Bolta role, and a viewer connection is read-only. In some apps batch approval and campaign setup from chat are not offered, so it works one post at a time and links you to Bolta. It also cannot post to a social account you have not connected in Bolta.

## Which brands can VS Code reach?

Only the brands you ticked at sign-in. With several ticked, put the brand name in the request so the draft lands under the right one. To change the list, remove the Bolta server from mcp.json, add it again and sign in again.

## Where does the Bolta config file go in VS Code?

For one project it is .vscode/mcp.json inside the project folder, with a top-level servers key. VS Code's guided MCP: Add Server command can also write it for you. Newer VS Code versions may point new setups at other locations, so check VS Code's MCP docs if the file seems ignored.

## Should I use sign-in or an API key?

Use sign-in if VS Code offers it for remote servers, because it follows your Bolta role and only the brands you ticked. An API key acts as you with whatever permissions you gave it, so give it only what you need. Safe Mode and required client sign-off still apply either way. Neither route has been run end to end in VS Code.

## How do I keep the API key out of git?

Do not paste it into mcp.json. Add an inputs entry of type promptString with password set to true, and reference it in the Authorization header as Bearer followed by the input id. VS Code then asks for the key when the server starts. Keys begin with bolta\_sk\_.

## Can it read my changelog and write a post from it?

Yes, in agent mode the chat can read files in your workspace, such as CHANGELOG.md, and then call Bolta to save a draft from what it read. It writes only from text in front of it, so check the draft for claims the changelog does not support. Nothing is scheduled until you say yes.

## Do I need the Bolta skill as well?

It is optional but useful. Run npx skills add boltaai/bolta-skills --skill bolta, or copy the skills/bolta folder from the bolta-skills repository to where your app reads skills. The skill teaches the chat to draft in your voice and to ask before anything is approved. Node.js is needed for the command.

## How long does the sign-in last?

Sign-ins last about 60 days and normally renew themselves. If Bolta reports an expired or inactive connection, do not retry in a loop. Sign in again from VS Code's server list, or create a new API key and replace the old one.

## Can it run a weekly post routine when VS Code is closed?

A routine is saved in Bolta and runs there, so it does not need the editor open. Creating one takes your confirmation of what it will do, and switching it on takes a separate yes. Routines draft for your review. They do not publish unattended for client brands.

## Relevant links

- [Related page: /integrations](https://bolta.ai/integrations)
- [Bolta pricing](https://bolta.ai/pricing)

## Supporting sources

- [VS Code official website](https://code.visualstudio.com/)
