Bolt.new
Bolt already connects to Notion, Linear, and GitHub. The Vibe Coding Plan server is a custom connector: a URL, HTTP transport, and your API token, used while Bolt is building.
What changes in a Bolt project
Bolt's agent writes the app in the project chat. A connector adds tools to that chat. It does not add a dependency to the generated package, and it does not run when a visitor opens the deployed site. Use it to decide scope, then let Bolt implement one slice.
Bolt turns every tool on a connector on by default, and that tool list is account-wide. You cannot enable create_project in one Bolt project and hide it in another. You can turn the whole connector off per project, which is the control you should use. Leave Vibe Coding Plan off on experiments that are a single landing page. Turn it on when the chat is about to invent a product.
Bolt also warns that many connectors at once add context and token use. If Notion, GitHub, and this server are all enabled, Bolt spends part of the message looking at tools you did not need. For a planning turn, enable Vibe Coding Plan and leave the others off. Turn them back on when you are wiring those products.
Bolt's help center does not publish the HTTP header used by the API key field. This server accepts the token in Authorization (with or without the Bearer prefix) and in X-API-Key. Paste the raw token into Bolt's API key field. Do not prefix it yourself unless a later Bolt form shows a header name and a header value.
Server URL and token
App builders such as Lovable talk to a public HTTPS address. They cannot launch the local npx vibe-coding-plan-mcp process used by Claude Desktop and Cursor. Point them at the hosted server and send the personal token from your account.
Server URL · streamable HTTP · not SSE
https://vibecoderplanner.com/mcp
Create the token at API Tokens after you sign in. Copy it once. The dashboard will not show the secret again.
The token lasts 30 days. When calls start returning unauthorized, create a new token and paste it into the connector again. Revoke the old one.
Do not choose OAuth, MCP OAuth, or "Add & authorize" for this server. That sign-in path is set up for ChatGPT. These builders need the API token.
Paste the token alone when the field is labeled bearer token or API key. If the form asks for a header, set the name to Authorization and the value to Bearer plus the token, with one space between them.
The connection lets the builder chat read and create your projects. It does not put the token into the app you publish. If the shipped app must call Vibe Coding Plan, that is a separate server-side integration, and the token stays in an environment variable.
What the server can do from chat
These are the tools on the hosted server at https://vibecoderplanner.com/mcp. The builder calls them when your message needs a plan, an estimate, a stack, or a saved project. You do not run them by hand.
plan_coding_project
Breaks a named idea into tasks. Each task comes back with a title, a description, estimated hours, and the titles of tasks that should happen first. The reply also includes total hours. A free account receives a short demo plan and is_demo is true. A paid account receives a generated breakdown of the description you sent.
estimate_project
Same planning pass, summarized as total hours, a complexity label (Low, Medium, High, or Very High), and the task titles as phases. Use this when you want a size check before you ask the builder to start coding.
suggest_tech_stack
Returns one recommendation each for frontend, backend, database, and hosting, plus a short reason. It uses your description and any preferences you pass, such as "Laravel" or "mobile".
list_projects
Lists up to 20 projects on the signed-in account: id, name, description, and task count. Pass query when you want a name filter.
get_project_tasks
Loads one project you own. You pass project_id from list_projects. The reply includes each task id, title, description, status, and estimated hours.
create_project
Creates a project on your account. name is required. description is optional. Set generate_plan to true to save a task list on that project in the same call. Saved tasks store the title, description, hours, and dependencies. The long coding prompt for a task is filled when you generate the plan in the Vibe Coding Plan app.
Add the custom connector
Open connector settings
From the Bolt homepage chat box, click the plus icon, then Connectors, then Manage connectors. That opens the Connectors (MCP) page.
Create a custom server
Click Custom MCP server. Name: Vibe Coding Plan. URL: the HTTPS address above. Transport type: HTTP. Do not choose SSE. This server answers JSON-RPC over POST.
Authenticate with the API key
Authentication: API key. Paste the token from API Tokens. Do not choose MCP OAuth. Click Connect. Bolt shows Connected in the upper right when the handshake works.
Review the six tools
Open the connector, click the three dots, then Edit. All six tools start enabled. Leave them on unless you want Bolt blocked from creating projects. Click Save changes. This list applies to every Bolt project.
Skip auto-enable
Leave Auto-enable for all projects off. Existing projects stay disconnected until you opt in. New throwaway prompts stay lighter.
Turn it on inside the project
Open the project. In the chat box, click plus, then Connectors, and enable Vibe Coding Plan. You can disable it again later in the same menu without deleting the connector.
Example: a used camera marketplace
The product is a marketplace where people list a camera, buyers message the seller, and nobody pays inside the app yet. Bolt will otherwise jump to a full auth system, image uploads, and chat in one prompt. Split it.
Estimate first. "Use the Vibe Coding Plan connector. Estimate a project: a used camera marketplace with accounts, photo listings, and a simple message thread. No checkout. Reply with the hours, complexity, and phase titles, and do not write code yet." That calls estimate_project. If the hours are larger than the weekend you have, cut messaging before any files exist.
Save the plan. "Use Vibe Coding Plan. Create a project named Camera Market. Description: sellers list a camera with photos and a price, buyers browse and send a message. Features: accounts, listings, messages. generate_plan true. Then show me the task titles in order." Check is_demo. On a free account, stop and either upgrade or write the real task list yourself. Building the demo titles would produce a generic app with the camera words pasted on top.
Implement in slices. "Load Camera Market tasks. Build only the listing model and the public browse page. Leave messages for a later message." When the preview matches that task, send the next title from the list. If Bolt starts a second feature, tell it to revert that part and stay on the named task.
Refresh the connector from the three-dot Edit menu if Bolt says the server is offline after you changed the token. Delete is on that same menu if you want the key removed from Bolt.
When Connect fails
Transport is SSE. Switch it to HTTP and connect again. A GET on this URL is empty. The session is POST.
Authentication is MCP OAuth. Bolt opens a sign-in that this server will not finish for Bolt. Edit the connector and use the API key.
The status never reaches Connected. Create a fresh token, paste only the secret, and confirm the URL ends in /mcp. A homepage URL will not speak MCP.
Bolt builds without calling the tool. The connector is saved but the project toggle is off, or the prompt never names Vibe Coding Plan. Enable it in the chat plus menu and repeat the prompt.
Questions
Does the deployed Bolt app keep the connector? No. Turn the connector off when you are done planning. The deployed app needs its own database and secrets.
Can I share the connector with a Bolt teammate? They add the same URL with their own API token. Do not send them yours.
Should I leave it enabled on every project? No. Bolt applies connector context to the chat that has the toggle on. Enable it for the build that needs a plan.
Turn any idea into a fully planned, code-ready project in minutes. Vibe Planner uses AI to break your concept into tasks, generate developer prompts, and execute them automatically.
Start Building FreeNo credit card required
Describe your idea and get a structured plan with tasks, milestones, and technical decisions in seconds.
Each task comes with optimized prompts for Cursor, Copilot, or any AI coding tool you use.
AI agents write code, create branches, and open Pull Requests on your GitHub repo — hands-free.
Track progress with a visual board. Drag tasks between columns, edit details, and stay organized.
React, Next.js, Laravel, Django, Flutter, and more. AI plans are tailored to your stack.
Turn any idea into a fully planned, code-ready project in minutes. Vibe Planner uses AI to break your concept into tasks, generate developer prompts, and execute them automatically.
Start Building FreeNo credit card required
Describe your idea and get a structured plan with tasks, milestones, and technical decisions in seconds.
Each task comes with optimized prompts for Cursor, Copilot, or any AI coding tool you use.
AI agents write code, create branches, and open Pull Requests on your GitHub repo — hands-free.
Track progress with a visual board. Drag tasks between columns, edit details, and stay organized.
React, Next.js, Laravel, Django, Flutter, and more. AI plans are tailored to your stack.