Base44
Base44 keeps custom MCP servers on the account, so every app you can open may use them in AI chat. A Builder plan or higher is required. The connection never becomes a backend function in the published app.
Account-wide chat tools
You add the server once: workspace name at the bottom left, Account settings, Builder, MCP Connections. It is then available in AI chat for every app in every workspace that account can access. You do not paste a config file into each app. The cap is 20 custom servers. At the cap, remove one before adding this.
Base44's docs say the AI decides when a connection is relevant, and that naming it in the prompt works better. Say "Use the Vibe Coding Plan MCP" when you want a plan. A generic "continue building" will often skip it, because the server is not required to paint the next screen.
Base44 also sends the app id it is building. On MCP requests that is X-Base44-App-Id, and inside tool metadata it is base44.com/app-id plus a branch id when you are on a branch. Vibe Coding Plan does not read those fields. Your projects are still your account's projects, not one board per Base44 app. If you build two Base44 apps, create two Vibe Coding Plan projects and use the project name in the prompt so list and create do not mix them.
Builder plan or higher is a Base44 requirement, not a Vibe Coding Plan one. If Add custom MCP is missing, check the Base44 plan before you change the token. OAuth in their form is the wrong choice here. Pick a custom header.
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 connection
Open MCP Connections
Click the workspace name at the bottom left. Click Account settings. Click Builder and scroll to MCP Connections.
Start a custom server
Click Add custom MCP. If you already have servers, the button is Add MCP. Name: Vibe Coding Plan. URL: the hosted /mcp address.
Send the token as a header
Leave OAuth unselected. Under custom headers, click Add Header. Name: Authorization. Value: Bearer, a space, and the token from API Tokens. Do not also invent an X-Base44-App-Id header. Base44 sets that itself, and a custom header with the same name cannot replace it.
Test and add
Click Test & Add. Base44 checks the server and then saves it on the account. If the test returns unauthorized, the header value is the first thing to fix. Not required is the wrong authentication option. This server rejects anonymous calls.
Use it in the app chat
Open the Base44 app you are building and ask the AI chat to use Vibe Coding Plan. The connection is not called from app flows, workflows, backend functions, or invokeLLM. Those need a normal integration if the live app must reach another service.
Turn it off when you are iterating on copy
Base44 lets you disable a connection without deleting it. Disable it while you are only changing text, so the chat does not spend the turn on planning tools.
Example: bakery inventory
The app is internal. Staff mark what was baked, what sold, and what to make tomorrow. There is no public storefront. Base44 will still try to add a customer site if the first prompt says "bakery app". Pin the scope with the planner.
Stack. "Use the Vibe Coding Plan MCP. suggest_tech_stack for an internal bakery inventory app used by five staff on a tablet. Preferences: simple forms, relational database. Do not change the app yet." Read the four recommendations in the chat. If hosting is a large cloud setup and you want the app to stay on Base44's own hosting, ignore that row and say so. The advisor does not know you are already inside Base44.
Plan. "Use Vibe Coding Plan. create_project name Bakery Inventory. Description: staff record batches baked, batches sold, and a next-day bake list. No online orders. generate_plan true." On a paid Vibe Coding Plan account the tasks follow that description. On a free account, is_demo is true and the titles are the sample plan. Tell the chat "ignore demo tasks" and write the three real areas yourself: today's bake, sales count, tomorrow's list.
Build. "get_project_tasks for Bakery Inventory. Implement only the task about recording what was baked. Staff pick a product and a quantity. Stop there." Check the preview on a narrow width, because the users are on a tablet. Then ask for the sales task. The MCP list is the checklist. Base44's chat is the builder.
When you start a second Base44 app, create a second project. list_projects with query Bakery returns the inventory project so you do not attach tomorrow's menu app to the same board.
Questions
Can a backend function call plan_coding_project? No. MCP connections are editor chat only. Base44 documents that directly.
Why can every app see this server? Base44 stores the connection on the account. Name the Vibe Coding Plan project in the prompt so two apps do not share one plan by accident.
The test failed with unauthorized. The header must be Authorization and the value must start with Bearer and a space. OAuth and Not required will not authenticate.
I am on a free Base44 plan. Base44 requires Builder or higher for custom MCP servers. The Vibe Coding Plan token cannot bypass that.
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.