MCP Tools

Bucky's MCP server exposes a deliberately narrow subset of the canonical Bucky tool registry. Most tools are read-only. The one write is explicit product feedback: it requires authentication, client-native human review, and acceptance before anything is saved.

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 submitBuckyFeedback only 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. Use tools/list as the runtime authority whenever client state and documentation disagree.

Boundary

The MCP surface does not expose project writes, planning orchestration, map UI interactions, or full chat transcript semantics. Its feedback write cannot modify product state and is idempotent when retried with the same submission UUID. Use the Bucky product or CLI for other write workflows.