---
title: "MCP workflows"
description: "Example prompts for Claude, ChatGPT, Cursor, and other assistants connected to Bucky — and the tools each one calls."
last_updated: "2026-10-04"
---

Once Bucky is [connected](/docs/mcp/connect), ask in plain language. Your assistant
chooses the tools. These are the common workflows, with prompts you can copy and the
tools you'll see it call.

## Check whether Bucky covers a place

> Does Bucky cover Minneapolis? What does it have there?

> Can Bucky tell me anything about 4170 Sophia St, Vancouver?

**Tools:** `cityInventory`, `previewSiteCoverage`. Neither needs sign-in. The preview
says whether Bucky has the parcel and zoning for that address, without showing the
values. Sign in to see them.

## What can I build here?

> What can I build at 1541 W 12th Ave, Vancouver? Cite the bylaw for every number.

**Tools:** `getFeasibilitySnapshot`, then `getBylawSection` for each cited number.

The snapshot returns the lot (area, width, depth), the zone and permitted uses, and the
building envelope (height, storeys, coverage, density, setbacks). Each value carries a
status. An assistant should report "not extracted" as unknown, never as "no limit" — see
[result statuses](/docs/mcp/integrations#result-statuses). The built-in
**What can I build here?** prompt runs this workflow with those rules.

## Compare two sites

> Compare 2225 W 6th Ave and 2636 Ontario St in Vancouver: lot, zoning, and envelope,
> side by side.

**Tools:** `getFeasibilitySnapshot` once per address. Only values that are cited on both
sites should be compared; a missing value is unknown, not a worse number. The built-in
**Compare two sites** prompt does this.

## Find lots that match a buy box

> Find lots in Vancouver over 6,000 sf, zoned R1-1, built before 1950, land title only.
> How many match, and which are the biggest?

> Save that as "Pre-1950 R1-1 lots" and give me the CSV.

**Tools:** `cityInventory` (to pick the city), then `screenLots`.

`screenLots` returns:

- how many stored lots match, out of how many Bucky has for that city;
- up to 25 lots (10 by default), largest first among the first 50 matches, each with a
  pass / fail / not available verdict per filter;
- every filter the city's data can't apply, so the count is never silently wider than
  you think.

Saving needs the `mcp:write` permission. A saved box appears in **My Searches** in the
web app, and the result includes a CSV export link (up to 1,000 lots). See
[Saved searches](/docs/platform/saved-searches).

## From a site to a project

> Save 1541 W 12th Ave as a new project called "W 12th duplex", run the analysis, and
> tell me when it's done.

> Add the three largest lots from that search to a new project called "Kits assembly".

**Tools:** `saveToProject` (with `preview=true` first), `runFeasibilityAnalysis`, then
`getProjectContext` until the analysis reads `current`.

`saveToProject` can create a project and attach parcels in one call, using the
`parcelExternalId` values from `screenLots`. In clients with
[interactive views](/docs/mcp/views-and-prompts), the project card updates while the
analysis runs.

## Work on an existing project

> What's the status of my Main Street project? Anything I should look at?

> Rename it to "Main Street Infill".

**Tools:** `getProjectContext`, `updateProject`. If you don't name the project, your
assistant asks which one. `updateProject` changes the name, lifecycle status, and import
reference, and can be undone from its receipt. Other edits (tasks, costs, members) are in
the [CLI](/docs/cli) or the web app.

## Produce a report

> Draft an investor report for Main Street. Show me the outline before you export it.

**Tools:** `getProjectContext`, `runFeasibilityAnalysis` if the analysis is stale, then
`produceProjectReport` with `preview`, and with `confirm` once you agree. Only the
confirmed export uses one of your plan's monthly exports. The built-in **Draft an
investor report** prompt follows this order.

## Put a project on the public map

> List Main Street on the public map. Show me exactly what will be public first.

**Tools:** `setProjectMapListing` with `preview=true`, then without. Listing publishes the
build lot's location, the project name, its zone category, type, and status to anyone.
Only list sites you are free to make public.

## Tell the Bucky team something

> Tell Bucky the setback for this lot looks wrong — the bylaw says 7.5 m.

**Tool:** `submitBuckyFeedback`. Your assistant shows you a form with the feedback, and
nothing is sent unless you approve it.

## Tips

- **Name the city.** Many street names repeat across cities. "1541 W 12th Ave,
  Vancouver" resolves faster and more reliably than "1541 W 12th Ave".
- **Ask for sources.** Every value has a status and a citation. Ask your assistant to
  quote them.
- **Ask for a preview before a change.** All project writes support it.
- **Start a new chat for a new site.** Long conversations make assistants more likely to
  mix up two addresses.


## Sitemap

See the full [sitemap](/sitemap.md) for all pages.