Views, prompts, and resources
The interactive cards Bucky shows in supporting MCP clients, the project picker and feedback forms, built-in prompts, and resources you can attach to a conversation.
Besides tools, Bucky's MCP server offers interactive views, forms, prompts, and resources. Each is optional. A client that doesn't support one still gets the same information as text.
Interactive views
In clients that support MCP Apps, Bucky results appear as interactive cards instead of plain text. Nine tools have a card:
| Card | Shown for | What it adds |
|---|---|---|
| Site snapshot | getFeasibilitySnapshot | The lot, zone, and envelope, with each value's status and source |
| Project | getProjectContext, runFeasibilityAnalysis | Live analysis status that updates until the run finishes |
| Change review | saveToProject, updateProject | The field-by-field change before and after it is applied |
| Map listing | setProjectMapListing | A preview of the exact pin that would be public |
| Report | produceProjectReport | The report outline, then an Export button |
| City inventory | cityInventory | What Bucky holds for the city, grouped |
| Coverage preview | previewSiteCoverage | What Bucky has for one address, without values |
| Status | explainFeasibilityStatus | The status, what it means, and the next step |
| Guide | getBuckyMcpGuide | Setup, first steps, and what to do elsewhere |
Bucky declares fullscreen-only display support so compatible clients can open results in a side panel. The client controls the actual display mode. If a client shows an inline card, snapshot and project cards retain an Expand button.
On clients that support model context updates, panels share their visible result with the assistant. Project, coverage preview, listing, report, status, guide and change panels also refresh that context when their visible content changes. These updates are bounded and omit hidden fields and link targets. Snapshot and city inventory panels share their own summaries. Cards make no network requests of their own and load no outside content.
Project picker
Project tools take a projectId or a project name. If you give neither, Bucky asks
which project you mean. Clients that support forms show a picker with up to 25 of your
projects; other clients get the list as text and ask you to choose. With more than 25
projects, name the one you mean.
Feedback form
submitBuckyFeedback always shows you a form with the feedback before anything is
sent. If you decline or cancel, nothing is stored. Bucky removes common personal data
and credentials from accepted feedback before storing it.
Built-in prompts
Clients that list MCP prompts (often as slash commands) show four Bucky prompts. Each runs a workflow with the rules for reading Bucky's results.
| Prompt | Arguments | What it does |
|---|---|---|
| What can I build here? | address | Snapshot, then the bylaw text for each cited number |
| Compare two sites | addressA, addressB | Side-by-side table, comparing only values cited on both sites |
| Draft an investor report | projectId, audience | Checks the analysis is current, previews the report, exports on confirmation |
| Explain a zoning result | status | What a result status means and what to do next |
Resources
Resources are documents a client can attach to a conversation, often with @.
| Resource | Sign-in | Contents |
|---|---|---|
bucky://guide | no | The same guide as getBuckyMcpGuide |
bucky://status/{status} | no | What one result status means |
bucky://project/{projectId}/context | mcp:read | A project's context, as getProjectContext returns it |
The project Prompt button in the web app copies a short brief with the project's id
and its bucky://project/…/context resource, so you can hand a project to any assistant.
Autocomplete
Prompt arguments and resource templates support autocomplete. In clients that offer
it, typing not in a status field suggests not_extracted.
Last updated on