MCP Tools
Understand the Bucky tool groups exposed through MCP.
Bucky's MCP server exposes a deliberately narrow subset of the canonical Bucky tool registry. Two tools are anonymous and cost nothing; the rest require authentication and a scope.
| Tool | Scope | Effect |
|---|---|---|
getBuckyMcpGuide | none | Static guide to this surface |
explainFeasibilityStatus | none | Static status lookup |
getFeasibilitySnapshot | mcp:read | Site facts for an address |
getProjectContext | mcp:read | Read a project and its analysis |
saveToProject | mcp:write | Create a project; attach parcels or a reference |
updateProject | mcp:write | Update project fields |
runFeasibilityAnalysis | mcp:write | Start an analysis run on a project |
setProjectMapListing | mcp:write | List or unlist a project on the public map |
produceProjectReport | mcp:export | Render a report PDF; spends records.exports |
submitBuckyFeedback | none | Human-reviewed product feedback |
A client that requests no scopes is granted mcp, which covers all three. Export
is separate because it is the only tool that spends a metered resource.
Choose a workflow
- Projects: find a user's projects, load aggregate details, or retrieve the compact memory digest used to resume project context.
- Location: resolve an address, find its geographic division, and inspect nearby builds or sellers.
- Marketplace: search professional and service-provider records.
- Knowledge: use structured regulatory lookup when you have jurisdiction or citation context, and semantic search for broader construction knowledge.
- Feedback: call
submitBuckyFeedbackonly when the user explicitly asks to report a problem, suggest an improvement, or send praise. Never use it for silent agent self-reporting.
Tool names, parameters, return contracts, and the complete current inventory are generated in the MCP tool reference.
Product-only alternatives
Some canonical descriptions mention richer BuckyAssist tools. The generated
reference marks each such name as BuckyAssist only; unavailable over MCP.
An MCP client must not attempt to call those alternatives. Live map control
(requestMapInteraction, including set-basemap for streets vs satellite) is
Assist-only: this product MCP surface has no map chrome, and neither does the
Bucky CLI. Use tools/list as the runtime authority whenever client state and
documentation disagree.
Boundary
Authenticated MCP writes are saveToProject, updateProject, runFeasibilityAnalysis,
and produceProjectReport. They preview with preview=true (report uses preview /
confirm). A write returns a receipt. updateProject can reverse from that receipt;
create, parcel attach, knowledge attach, analysis enqueue, and report export cannot
be undone on this surface. Archive, detach, delete, development programs, cost
ledger, location repair, and chat stay on the Bucky CLI — getBuckyMcpGuide
lists each unreachable workflow with its command.
Last updated on