About Bool
Bool is an official plugin for connecting AI assistants to Bool, a hosted service for building and publishing web apps from descriptions. It provides Bool's MCP tools and usage guidance across supported plugin clients, with sign-in through a Bool account.
Key features
- 01Connects to Bool's hosted MCP server
- 02Bool tool-use skill included
- 03Plugin manifests for multiple clients
- 04OAuth sign-in with a Bool account
Use cases
- 01Build a web app from a description
- 02Publish a web app built with Bool
- 03Use Bool tools from an MCP client
MCP support
The plugin connects clients to Bool's hosted MCP server at `https://bool.com/api/mcp` over Streamable HTTP. Users authenticate with their Bool account through OAuth.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://bool.com/api/mcpclaude mcp add --transport http com-bool-bool https://bool.com/api/mcp{"mcpServers":{"com-bool-bool":{"type":"http","url":"https://bool.com/api/mcp"}}}Open in Cursor{"servers":{"com-bool-bool":{"type":"http","url":"https://bool.com/api/mcp"}}}Open in VS Code{"mcpServers":{"com-bool-bool":{"type":"http","url":"https://bool.com/api/mcp"}}}{"mcpServers":{"com-bool-bool":{"serverUrl":"https://bool.com/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEBool plugin
The official plugin for Bool, which builds and publishes web apps from a description. Bool is operated by CodeHS, Inc.
The plugin connects an AI assistant to Bool's hosted MCP server at https://bool.com/api/mcp and adds a skill that tells the assistant how to use Bool's tools. It runs no server of its own and holds no secrets. Users sign in with their Bool account through OAuth. The license is MIT.
Install
| Client | How |
|---|---|
| ChatGPT and Codex | Search Bool in the plugin directory once it's listed. |
| Cursor | Customize, then Marketplace, then search Bool. |
| Grok Build | Settings, then Plugins, then search Bool. |
| Any other MCP client | Add https://bool.com/api/mcp as a remote MCP server and sign in with Bool. |
Layout
One repo serves every client. The shared parts follow the Agent Plugins format, which ChatGPT, Codex, Cursor, VS Code and GitHub Copilot read directly. Each client that needs more gets a small file of its own.
| Path | Read by | Holds |
|---|---|---|
plugin.json | Agent Plugins clients | Name, version, publisher. The OpenAI listing, review cases and release notes live under extensions.com.openai. |
mcp.json | Agent Plugins clients | The bool server, over Streamable HTTP. |
skills/bool/SKILL.md | Every client | When and how to use Bool's tools. |
assets/ | Every client | Icon, logo and wordmark. |
.cursor-plugin/plugin.json | Cursor | Display name and logo. |
.claude-plugin/plugin.json, .mcp.json | Claude Code, Grok Build | The same plugin in their manifest format. |
server.json | The official MCP Registry | The registry entry, com.bool/bool. |
Keep the version the same in all four manifests. CI checks it.
Publish to the MCP Registry
mcp-publisher login http --domain bool.com --private-key "$(openssl pkey -in ~/.config/bool/mcp-registry-key.pem -noout -text | grep -A3 priv: | tail -n +2 | tr -d ' :\n')"
mcp-publisher publish
bool.com serves the matching public key at /.well-known/mcp-registry-auth. Bump version in server.json before republishing.
Release to the OpenAI plugin directory
scripts/build-openai-zip.sh
The script writes dist/bool-<version>.zip with only what OpenAI reads: plugin.json, mcp.json, skills/, assets/, README.md and LICENSE. Upload it from the Bool plugin's page in the OpenAI Platform with Upload plugin to make changes. The Upload new or existing plugin button on the Plugins list creates a separate plugin.
Support
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.