Connect your AI to Bool

Bool runs a remote MCP server — one endpoint that any Model Context Protocol client can connect to. Once it’s connected, your AI can create Bool projects, deploy websites, and check on what’s live, all on your behalf.

You only need two things:

Server URL: https://bool.com/api/mcp
Transport: Streamable HTTP (remote)

That’s it. How you add those depends on your client — pick yours below.

The fast way: just ask

Most modern AI clients can add an MCP server themselves. Before hunting through settings, try simply telling your AI:

Add the Bool MCP server at https://bool.com/api/mcp as a connector.

If your client supports it, it’ll walk you through connecting and then sign you in (see Signing in below). If that doesn’t work, use the per-client steps below.

Signing in

Bool needs to know it’s really you. There are two ways to authenticate, and you usually don’t have to think about it — the client picks one for you:

Sign in with Bool (recommended). Clients that support connectors (Claude, ChatGPT) pop open a Bool login the first time you use the server. Log in, approve access, and you’re done — no keys to copy.
Personal access token. Clients that connect by config file (Cursor, VS Code, and most others) authenticate with a token. Create one at Settings → API tokens, click New token, and copy the value (it starts with bool_live_). Treat it like a password — anyone with it has your access to that workspace. Each token is scoped to a single workspace.

Everything the AI does runs in your active workspace (or, for a token, the workspace that token is bound to) and respects the same permissions you have.

Connect your client

Claude (desktop or web)

Open Settings → Connectors and click Add custom connector.
Paste the server URL: https://bool.com/api/mcp.
Save, then click Connect — a Bool login opens. Sign in and approve.

Bool’s tools now show up in the chat’s tools menu.

ChatGPT

In a workspace that allows custom connectors, go to Settings → Connectors → Add.
Paste https://bool.com/api/mcp and choose OAuth for authentication.
Connect, sign in to Bool, and approve access.

Cursor

Add Bool to your MCP config (Settings → Tools & MCP, or edit ~/.cursor/mcp.json directly):


{
  "mcpServers": {
    "bool": {
      "url": "https://bool.com/api/mcp",
      "headers": {
        "Authorization": "Bearer bool_live_your_token_here"
      }
    }
  }
}

Replace bool_live_your_token_here with a token from Settings → API tokens.

VS Code (Copilot agent mode)

Add a server to .vscode/mcp.json in your workspace (or your global mcp.json):


{
  "servers": {
    "bool": {
      "type": "http",
      "url": "https://bool.com/api/mcp",
      "headers": {
        "Authorization": "Bearer bool_live_your_token_here"
      }
    }
  }
}

Any other MCP client

The pattern is the same everywhere — point the client at the remote server and give it your token:

URL: https://bool.com/api/mcp
Transport: Streamable HTTP (sometimes labeled “HTTP” or “remote”)
Auth: an Authorization: Bearer bool_live_… header, or the client’s OAuth flow if it has one

What your AI can do

Once connected, these tools are available:

Tool	What it does
list_projects	List the projects in your workspace, with their live URLs.
drop_project	Deploy a project by uploading it — a static site, or a Vite + React source tree that Bool builds for you in the cloud. Creates a new project, or ships a new version to an existing one (the URL stays the same).
get_drop_status	Check on a deploy that’s in progress and get the live URL once it’s ready.
get_project	Look up a project’s live URL and version history.

You don’t call these directly — you just describe what you want, and your AI runs the steps (uploading your files, then polling until the deploy is live). For example:

Deploy this folder to Bool and give me the live URL.

List my Bool projects and tell me which ones are live.

Troubleshooting

“Unauthorized” or a login loop. Your token is wrong, expired, or revoked. Create a fresh one at Settings → API tokens and update your config. For OAuth clients, disconnect and reconnect the server.
“Rate limit exceeded.” The server limits requests per minute per token. Wait the few seconds it suggests and retry; higher plans get higher limits.
A deploy fails or the site root 404s. Make sure the uploaded archive has an index.html at its root (zip the folder’s contents, not the enclosing folder). For a framework app, upload the source — Bool builds it for you; you don’t need to run the build or upload a dist/ folder yourself.
Tools don’t appear. Confirm the URL is exactly https://bool.com/api/mcp and that your client is set to a remote / HTTP server, not a local command.