Local MCP server/Development

B12 Website Generator MCP server

Local MCP server

The B12 Website Generator is an AI-powered website generator from B12 that needs no external data files. The README documents a local stdio server started with npx -y @b12/website-generator-mcp-server and does not publish a hosted URL, transport, or authentication model. Use the documented local command rather than a hosted endpoint.

Not verified Source checked Nov 12, 2026 Local install path Reviewed 2026-11-16
About

Where it fits

Developers and small teams that want to generate a website locally through the B12 stdio server.

  • Run the documented npx stdio server.
  • Generate a website without supplying data files.
  • Use the B12 generator locally in development.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local stdio server

The provider documents the npm package as a local stdio server.

npx -y @b12/website-generator-mcp-server

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

B12 Website Generator repositoryhttps://github.com/b12io/website-generator-mcp-server