# Buildability MCP server

> Score any US parcel on nine cited factors, including zoning, flood, seismic, soil, radon and wildfire, to see what can be built.

- Listing: https://mcp.tc/i/buildability
- Connect: use the server's own URL `https://buildability.us/api/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Data & Analytics](https://mcp.tc/c/analytics)
- Vendor: Buildability
- Homepage: <https://buildability.us/>

## About

Connects to the Buildability service, which scores US addresses and parcels from 0 to 100 using cited public data: zoning, FEMA flood, USGS seismic, USDA soil, EPA radon, USFS wildfire, utilities, terrain and lot shape. Tools cover live address scoring, parcel search, factor breakdowns, buildable envelopes, what-if scenarios, pro-formas and city market rankings.

It runs as a hosted streamable HTTP endpoint. Scoring a new address takes roughly 10 to 20 seconds. No sign-in or API key is needed for the main tools; the lot\_surface tool requires a Buildability API key.

## What it can do

- Score any US street address with live federal data
- Search scored parcels by text, score and Opportunity Zone
- Explain a score factor by factor
- Get buildable envelope: units, FAR, height, setbacks
- Run what-if scenarios such as upzoning or flood mitigation
- Pencil a development pro-forma for a parcel
- Rank metros on the City Buildability Index
- Read permit outcomes for a zoning district

## Tools (16)

- `score_address`: Live-score a US street address using federal data and return the Buildability Score.
- `search_parcels`: Search scored parcels by text and filters, returning ranked matches.
- `explain_score`: Factor-by-factor breakdown of a parcel's score with plain-English notes.
- `parcel_details`: Zoning standards, valuation, comps, hazards, ownership and lot size for a parcel.
- `feasibility`: Buildable envelope and score for a parcel: max units, FAR, height, coverage.
- `run_scenario`: Re-score a parcel under upzone, flood, utilities or hazard levers and show the delta.
- `pencil_proforma`: Development pro-forma with zoning fit, cost stack, value band and margin band.
- `market_index`: Rank metros on the City Buildability Index with component breakdowns.
- `envelope`: What a lot can hold by right from its zoning code, with citations.
- `outcomes`: Permit outcome counts and time to issue for a zoning district.
- `lot_surface`: Slope and relief across a lot from USGS 3DEP elevation; needs an API key.
- `analyze_property`: Full Buildability analysis for a US address (alias of score\_address).
- `get_buildability_score`: Quick 0 to 100 score for a US address (alias of score\_address).
- `lookup_zoning`: Zoning context for a US address with the scored breakdown (alias of score\_address).
- `check_flood_zone`: FEMA flood context for a US address (alias of score\_address).
- `check_environmental_risks`: Hazard screening for a US address (alias of score\_address).

## Example prompts

- "Score 1444 Tennyson St, Denver for buildability."
- "What can I build on this lot? Show max units, height and setbacks."
- "Find scored parcels in Austin with a score above 70."
- "Compare Austin and Denver on the City Buildability Index."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http buildability https://buildability.us/api/mcp
```

2. Start Claude Code and type `/mcp`. **buildability** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Buildability** and paste this URL:

```url
https://buildability.us/api/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Buildability&connectorUrl=https%3A%2F%2Fbuildability.us%2Fapi%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://buildability.us/api/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://buildability.us/api/mcp` as the server URL and choose **No authentication**.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=buildability&config=eyJ1cmwiOiJodHRwczovL2J1aWxkYWJpbGl0eS51cy9hcGkvbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "buildability": {
      "url": "https://buildability.us/api/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=buildability&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fbuildability.us%2Fapi%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"buildability","type":"http","url":"https://buildability.us/api/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "buildability": {
      "type": "http",
      "url": "https://buildability.us/api/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "buildability": {
      "serverUrl": "https://buildability.us/api/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add buildability --url https://buildability.us/api/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.buildability]
url = "https://buildability.us/api/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http buildability https://buildability.us/api/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "buildability": {
      "type": "http",
      "url": "https://buildability.us/api/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://buildability.us/api/mcp`.

## Recent changes

- 2026-10-08 04:20 UTC: Tracking started: 16 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/buildability#history (Atom feed: https://mcp.tc/i/buildability/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 2.0.0
- MCP protocol version: 2025-03-26
- Last checked: 2026-10-08 (reachable)
- Listed: 2026-10-08
- Updated: 2026-10-08

---
Source: https://mcp.tc/i/buildability (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report