Connecting Beeboo to VS Code

Documentation / Agentic editing and connections

The packaged Beeboo MCP server runs locally through standard input/output and calls the Beeboo agent API. You need VS Code with MCP support, Node.js with npx, and a Beeboo account authorized for the target website. The current connection instructions identify package version 0.1.3.

Prepare a private configuration

The CMS instructions are under Settings > Advanced > Agent Access Tokens. A personal access token, or PAT, is a credential you supply to the local server. It is different from the browser-based OAuth consent used by hosted connectors. Choose read-only access for inspection; Allow changes enables read and write.

Open your user-level mcp.json, rather than a repository file that could be committed. This configuration deliberately contains no credential:

{
  "servers": {
    "beeboo": {
      "command": "npx",
      "args": ["-y", "https://r.beeboo.app/beeboo-mcp-0.1.3.tgz"],
      "env": {
        "BEEBOO_SITE_URL": "https://r.beeboo.app"
      }
    }
  }
}

This example is incomplete until BEEBOO_PAT is supplied privately to the server environment. Follow your organization's credential-storage policy. Never insert a token into a prompt, source-controlled example, screenshot, or support report.

Verify before editing

Start or restart the MCP connection in VS Code and inspect its tools. Ask it to list accessible websites without changing anything, then read the intended page and language. The gateway URL does not select a website; individual tool calls use the site domain. Do not approve a write until the read-only inventory returns the expected website and page.

If startup fails, check Node.js, package download access, the privately supplied credential, and expiry. A permission error may indicate missing site access rather than a broken installation. Revoke a lost credential in the CMS. See agentic editing and connections for approval boundaries.