---
title: "Connect Bucky to your AI"
description: "Add Bucky to Claude, Claude Code, Cursor, VS Code, Codex, ChatGPT, Grok, or the CLI."
last_updated: "2026-09-21"
---

Bucky runs an MCP server, so an AI assistant can look up zoning, parcels, and
feasibility for a street address without you leaving the conversation.

You need one thing:

```
https://buckybuild.com/api/mcp
```

Everything below is a different way of handing that URL to a client. Pick yours.

## Claude

Claude web and Claude Desktop both support remote MCP servers as **custom
connectors**. There is no install link — Anthropic does not offer one — so this
is a paste.

1. Open **Settings → Connectors**.
2. Choose **Add custom connector**.
3. Paste `https://buckybuild.com/api/mcp` and save.
4. Ask Claude something that needs Bucky — "what can I build at 412 Main St?" —
   and approve the sign-in page it opens.

<Callout type="info">
  Custom connectors need a paid Claude plan (Pro, Max, or Team). If you are on the free plan, use
  Cursor or the CLI below instead.
</Callout>

## Cursor

Cursor supports one-click install:

<a href="cursor://anysphere.cursor-deeplink/mcp/install?name=bucky&config=eyJ0eXBlIjogImh0dHAiLCAidXJsIjogImh0dHBzOi8vYnVja3lidWlsZC5jb20vYXBpL21jcCJ9">Add Bucky to Cursor</a>

Or add it by hand in **Settings → MCP → Add new MCP server**, with
`https://buckybuild.com/api/mcp` as the URL. Cursor registers itself
automatically; you do not need to create anything on the Bucky side first.

## VS Code

<a href="vscode:mcp/install?%7B%22name%22%3A%20%22bucky%22%2C%20%22type%22%3A%20%22http%22%2C%20%22url%22%3A%20%22https%3A//buckybuild.com/api/mcp%22%7D">Add Bucky to VS Code</a>

## Claude Code

```bash
claude mcp add --transport http bucky https://buckybuild.com/api/mcp
```

Claude Code opens the sign-in page the first time a tool needs your account.

## Codex

Codex reads `~/.codex/config.toml`. A `url` key rather than a `command` is what
selects the Streamable HTTP transport:

```toml
[mcp_servers.bucky]
url = "https://buckybuild.com/api/mcp"
```

Then run the OAuth leg once:

```bash
codex mcp login bucky
```

## ChatGPT

ChatGPT reaches custom MCP servers through **Settings → Connectors** in
developer mode. Add `https://buckybuild.com/api/mcp` and approve the sign-in
page. This needs a paid ChatGPT plan.

## Grok

Open [grok.com/connectors](https://grok.com/connectors), choose **New
Connector**, then **Custom**, and paste `https://buckybuild.com/api/mcp`. Grok
reads the tool list from the server. Custom connectors are on Grok's paid tiers.

Grok Build, the terminal CLI, reads MCP configuration you already have — nothing
extra to do there.

## Windsurf, Zed, Cline, and everything else

Any client that speaks Streamable HTTP takes the same object in its own MCP
config file:

```json
{ "type": "http", "url": "https://buckybuild.com/api/mcp" }
```

## Bucky CLI

```bash
bucky auth login
```

This opens a browser, signs you in, and stores the token locally. No connector
configuration needed.

## Signing in

The first time your assistant calls a tool that needs your account, it opens a
Bucky sign-in page. You will see:

1. **Which app is connecting** — named at the top of the sign-in form.
2. **What it will be able to do** — the exact permissions, listed before you
   approve. Reading your projects, creating and updating them, and exporting
   report PDFs are separate permissions, because exporting spends your export
   credits.

Approve once and the connection persists. You never paste a token, and the
assistant never sees your password.

Two tools work with no account at all, so you can check the connection is live
before signing in: `getBuckyMcpGuide` and `explainFeasibilityStatus`.

## Managing and disconnecting

Connected apps are listed at **Settings → Connected apps** in Bucky, with what
each one can do and when it was last used. Disconnecting takes effect
immediately — the next request that app makes is refused, rather than working
until its token happens to expire.

## If it does not connect

- **"Invalid client"** — your client registered but could not be resolved. This
  was a bug fixed on 2026-08-17; make sure the client is not caching an old
  registration, and try removing and re-adding the connector.
- **Signed in but nothing happened** — the connector flow needs to return you to
  Bucky's authorization page after login. If you land on the Bucky dashboard
  instead, the flow was interrupted; start it again from your assistant.
- **"New Bucky accounts are paused"** — self-serve signup is currently closed.
  Join the waitlist, and connect once your account exists.

## For developers

Protocol details — transport, discovery documents, verifying the endpoint with
`curl` — are in [MCP integrations](/docs/mcp/integrations). The tool catalog is
in [MCP tools](/docs/mcp/tools).


## Sitemap

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