MCP

MCP lets a local AI client use Desktop’s project and authoring tools. Keep Desktop running on the same computer as your client. A remote agent or browser chat cannot reach this local connection.

Connect your client

1. Open MCP in Desktop and choose Enable MCP.
2. Choose Codex, Claude Code, Cursor or Other clients.
3. Copy the private setup into your client’s user configuration, following the instructions shown in Desktop. It includes a token: keep it out of project files and shared repositories.
4. Restart or refresh the client’s MCP connection.

Other clients need Streamable HTTP and an Authorization header. Copy the actual endpoint from Desktop; its address and token belong to this installation.

Test the selected project

Open a website in Desktop, then ask your agent:

Use the BlockBite Desktop project tool. Tell me the selected project’s name and ID, then use check to read its setup checklist.

Your client discovers the server as blockbite-desktop. Use the returned project ID for later actions. Call project again after switching sites or changing access.

Start building

Ask your agent to use the direct authoring tools and follow the saved Flow and its relevant skills. The Tools drawer contains prompts you can copy. The MCP tool reference explains the available groups.

The separate build tool starts Desktop’s own provider-backed agents and uses its configured OpenRouter model and build allowance. Use it when you want that workflow; an external agent can author directly with its own model.

Connection help

If connection fails, check Local connection and copy the latest setup. Reset connection replaces the token, so update every connected client. If the agent sees no project, open a website in Desktop and test again.