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 deliberately narrow subset of its tool registry over MCP, spanning three
scopes: mcp:read for site and project reads, mcp:write for creating and
updating projects and running feasibility, and mcp:export for report PDFs.
Feedback is a separate, unscoped write that always requires human review and
acceptance. The tools share core registries with BuckyAssist but omit map
exploration and marketplace render tools. MCP does not mirror the CLI mutation
set; parcel attach is the one extra write so a created project can hold lots.
What is available today
The generated MCP tool reference is the source-derived inventory of everything the server exposes. The tools overview groups that inventory into builder workflows.
The allowlist includes project and project-memory reads, address and geographic
context, nearby records, seller search, and knowledge search. Authenticated
clients also receive submitBuckyFeedback, which opens a client-native form and
persists only after the human accepts it. Project Scout map flows and
marketplace rendering remain product-only. Project writes on this surface are
the four tools in the generated reference; they preview and emit receipts (see
the mutation-safety and write-scope decisions in docs/mcp/mcp-protocol-maturity.md).
saveToProject can create a project and attach parcels. Archive, programs, costs,
and location repair stay on the CLI.
Follow the HTTP integration workflow to exercise the current transport.
Regenerate the tool reference with pnpm generate-mcp-reference when the
registry changes.
Last updated on