The Bunstation MCP Server Is Live

What launched

The Bunstation MCP server is available at https://api.bunstation.com/mcp. It uses the recommended remote Streamable HTTP transport and signs you in through OAuth, so there is no API key to copy into a chat or configuration file.

MCP is an open standard that lets AI applications connect to external tools and data. In practical terms, it gives an agent a typed, discoverable set of Bunstation actions instead of forcing it to guess at a website interface or ask you to move code back and forth manually.

What your agent can do

• Start from a template

  Browse the same public template library available in the Bunstation app, filter it by category, and copy a selected template into a new project.

• Create

  Turn a written brief into a new Vite or Next.js project and follow its generation status.

• Understand

  List your projects, inspect project details, read files, search the codebase, and review recent project chat.

• Change

  Create, replace, or delete files as staged changes. Review the pending file list before committing.

• Ship

  Check build history and logs, then publish the latest successful build to a bunstation.app address.

• Manage

  Rename a project, change the model used for later work, or stop a generation that is still running.

• Check your account

  Read your credit balance and plan, inspect token usage, and retrieve invoices from the same conversation.

Use templates without leaving your AI agent

The MCP server exposes the Bunstation template library directly to your assistant. It can list public templates, filter them by categories such as restaurant or landing page, and show you each option's name, technology stack, preview, and template ID.

Once you choose an option, the agent can use that template to create a project in your account. This is the same remix flow as clicking Use template in the Bunstation app: the existing repository is copied into a new project without running a fresh AI generation. You can then ask the agent to inspect the files, replace the content, adjust the design, commit a build, and publish.

A safer edit-and-review workflow

Giving an agent access to a project should not mean every edit becomes permanent immediately. Bunstation file tools use a staged workflow: creates, updates, and deletions remain uncommitted until the agent lists the pending changes and commits them. A single unwanted draft can be discarded while the committed version stays intact.

Publishing is also separate from editing. The server only publishes a successful build, and your MCP client can show tool calls and ask for confirmation before actions that change a project. You remain in control of what is changed and when it goes live.

Connect Bunstation to Cursor

Cursor supports remote MCP servers from its Customize page or through an mcp.json file. To connect manually:

1. Open Cursor's MCP settings and add a new remote server named Bunstation.
2. Use https://api.bunstation.com/mcp as the server URL.
3. Start the connection and complete the Bunstation OAuth sign-in in your browser.
4. Return to Cursor and ask the agent to list your Bunstation projects or check your credits to confirm the connection.

If you prefer configuration, add a server named bunstation with the URL above to your project-level .cursor/mcp.json or global ~/.cursor/mcp.json. No authorization header or secret is required in the file; Cursor starts the OAuth flow when the server connects.

Try these first prompts

• "List my Bunstation projects and tell me which one was updated most recently."
• "Show me the available restaurant templates, recommend the best three, and wait for me to choose one."
• "Use the pizza restaurant template, then inspect its files and tell me what I should customize before publishing."
• "Create a responsive landing page for a neighborhood bakery with online ordering, warm colors, and a clear catering call to action."
• "Find the pricing section in my project, update the monthly price to $29, show me the pending changes, and wait before committing."
• "Check the latest build. If it succeeded, publish it and give me the live URL."
• "Show my Bunstation credit balance and token usage for this month."

Specific prompts work best. Name the project, describe the outcome, and say where you want the agent to pause for review. The agent can discover the available Bunstation tools itself, so you do not need to memorize tool names.

Why this matters

AI coding agents are good at reasoning about a request, but they become much more useful when they can safely reach the system where the work actually lives. Bunstation MCP closes that gap. The agent can move from understanding your intent to inspecting the real project, making reviewable changes, checking the build, and publishing the working result.

Because MCP is an open standard rather than a one-off integration, the same remote server can work with other compatible clients that support Streamable HTTP and OAuth. We are starting with the complete project lifecycle and will keep improving the tools around real workflows.

Build from the conversation you are already in

Connect the server at https://api.bunstation.com/mcp, sign in to Bunstation, and ask your agent to list your projects. From there you can create something new, improve an existing site, review every staged change, and publish when the build is ready.

New to Bunstation? Create your account and start building. If you want to see what the builder handles before connecting an agent, explore Bunstation features.