MCP
Connect AI agents to Bucky over the Model Context Protocol — setup, tools, and workflows.
The MCP section is for AI agents and the developers wiring them up. Bucky exposes a read-only subset of tools over MCP — generated from the same registry as BuckyAssist, but without map exploration, project mutations, or marketplace render tools.
What is available today
The MCP tool reference lists every exposed tool (currently seven): project lookup, address resolution, geo divisions, nearby builds and sellers, seller search, and semantic search over the knowledge base.
Tools such as knowledgeLookup, queryDesigns, queryMarketItemBuilds,
costEstimate, and permitChecklist are used inside BuckyAssist in the product
but are not on the MCP allowlist. Project Scout map flows (proposeExplorationPlan,
site options, and similar) are product UI only.
Planned pages
overview— what Bucky's MCP server exposes and when to use it.tools— tool categories and how they map to builder workflows.integrations— setup for Cursor, Claude Desktop, and other clients.
Setup guides are in progress. Use the generated tool reference for
parameters and behavior today. Regenerate with pnpm generate-mcp-reference when the tool
registry changes.
Last updated on