Connect VS Code and edit website content through MCP

Prepare local access

Use this guide for the local stdio MCP connection, which uses a personal access token rather than the remote connector's OAuth exchange. You need VS Code with MCP support, Node.js and npx available, and administrator access to the intended Beeboo website.

Choose one public page and a small approved correction. Record its website domain, page URL, and content language. Keep secrets outside repository files, prompts, screenshots, and commits. This guide supplies no credential and does not require sharing one with an assistant.

Configure the connection

Sign in to Beeboo and open Settings > Advanced > Agent Access Tokens. Enter a recognizable Token label, choose Expires, and review Allow changes. Unchecked creates read-only access; checked creates read and write scopes. Begin read-only if you only need inspection.
Choose Create token only when authorized to provision this credential. Copy it into your approved protected storage immediately; the CMS shows it only once. If it is lost, revoke it and create a replacement rather than trying to recover its value through chat.
Open your user-level VS Code mcp.json, not a tracked project configuration. The repository's local-client setup uses a server named beeboo, command npx, and arguments -y plus the administrator-approved Beeboo MCP package URL. Its documented release is https://r.beeboo.app/beeboo-mcp-0.1.3.tgz; confirm the workspace's current package before trusting or running it.
Supply BEEBOO_PAT through an approved protected client input or environment mechanism and set BEEBOO_SITE_URL to the approved CMS origin. Do not paste a real token into a reusable example. Start the server through VS Code's MCP controls and inspect its available tools. Restart or refresh after an approved server update if schemas remain old.

Inspect, then authorize the edit

Ask the assistant to run list_sites, select the exact website, and read list_pages and the intended page. Require it to report page identity and language before changing content. A connected client can access websites permitted to the account; do not assume it is limited to the currently open repository.
Request a proposal first: “On this selected English page, correct the opening sentence using this approved wording. Preserve the header, all other blocks, links, media, and settings. Do not save until I approve.” Review the proposed replacement.
When ready, authorize write access and the exact operation. Require a fresh page read and expectedPageModifiedAt. Native and custom page updates save directly, without relying on cloud autosave. Re-read on conflicts instead of retrying an old payload.

Verify and close access

Read the page back and open its normal public URL in a browser. Check the corrected sentence, neighboring content, and mobile layout. If authentication fails, inspect token expiry, scope, website permissions, and the configured CMS origin without exposing the token. Use Revoke when the credential is no longer needed. See assistant connections and saving and recovery.