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 mostly read-only subset of tools over MCP, plus one bounded feedback write that always requires human review and acceptance. The tools share core registries with BuckyAssist but omit map exploration, project mutations, and marketplace render tools.
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, project
mutations, and marketplace rendering remain product-only.
Follow the verified HTTP integration workflow to exercise the current
transport. Regenerate the tool reference with pnpm generate-mcp-reference
when the registry changes.
Last updated on