Permits

co.addressintelPublished by addressintel.cov1.1.2Updated Oct 24, 2026

SF Peninsula building permits and parcel buildability: SB 9, ADU and redevelopment leads.

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

Read-only access to SF Peninsula building permit records and parcel buildability data, including SB 9, ADU and redevelopment leads.

What you can do
A read-only MCP server that queries the public AddressIntel API for SF Peninsula construction permits and parcel-level buildability. Tools cover permit search by city, keyword and minimum valuation, SB 9 split or duplex eligibility, ADU capacity, underbuilt redevelopment leads, teardown or flip market signals, and full scores with comparable sales for a single property id. Every tool is a GET and nothing can write.
When to use it
Useful when an assistant needs permit-level detail or parcel buildability for the SF Peninsula rather than a nationwide owner list, for example answering which demolition permits were issued in a city or which listings are SB 9 eligible.
Requirements
Runs locally over stdio, normally launched with npx addressintel-mcp, so Node.js and network access to the AddressIntel API are needed. An ADDRESSINTEL_API_KEY is optional; without it the public demo tier applies at 10 requests per minute and 5 rows per call. The API base can be overridden with ADDRESSINTEL_API_BASE.
Before you install
The server is read-only and cannot write, send or delete data. The optional ADDRESSINTEL_API_KEY is passed as an environment variable and should be kept out of shared configuration files. Queries and results go to the third-party AddressIntel API, and the demo tier caps requests and rows.

Installation

In SourceWeft

  1. Open Permits in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

AddressIntel MCP server

A read-only Model Context Protocol server that puts SF Peninsula building-permit and parcel-buildability data inside Claude, ChatGPT, or any other MCP-capable agent.

It is a thin client over the public AddressIntel API, so it inherits that API's auth, rate limits and tier ceilings. Every tool is a GET. Nothing here can write.

Tools

ToolWhat it answers
search_permitsWhat construction has actually been permitted at an address or in a city? Filters on city, keyword (address, project type, scope description, contractor, architect, permit number) and minimum valuation.
list_sb9_inventoryWhich active listings can be split or duplexed under SB 9, and what blocks the ones that can't?
list_adu_leadsWhich parcels have room for an ADU, and how many units / how much square footage?
list_redevelopment_leadsWhich parcels are underbuilt against their allowable envelope (scrape-and-rebuild or expansion)?
list_market_signalsWhich listings score highest for teardown or flip potential?
get_property_intelligenceFull scores and comparable sales for one property id.

The permit and parcel tools are the differentiated half: permit-level detail and parcel-level buildability for the Peninsula, rather than a nationwide owner list.

Install

No install step: npx fetches it on demand.

Claude Code

bash
claude mcp add addressintel \  -e ADDRESSINTEL_API_KEY=your_key \  -- npx -y addressintel-mcp

Claude Desktop

Add to claude_desktop_config.json:

json
{  "mcpServers": {    "addressintel": {      "command": "npx",      "args": ["-y", "addressintel-mcp"],      "env": {        "ADDRESSINTEL_API_KEY": "your_key"      }    }  }}

From source

For working on the server itself:

bash
git clone https://github.com/RantumBits/addressintel-mcp.gitcd addressintel-mcpnpm installnpm run build     # emits dist/index.js

Then point the client at node /absolute/path/to/addressintel-mcp/dist/index.js instead of the npx command above.

Restart the client, then ask it something like "what demolition permits were issued in Menlo Park this year?" or "which Palo Alto listings are SB 9 eligible?"

Configuration

VariableDefaultNotes
ADDRESSINTEL_API_KEYdemoWithout a key the server uses the public demo tier: 10 requests/minute, 5 rows per call. Grab a free key at https://addressintel.co/developers for 30/min and 25 rows; the key is emailed to the address you enter.
ADDRESSINTEL_API_BASEhttps://addressintel.co/apiPoint at a local dev server (http://localhost:3000/api) when working on the API.

Development

bash
npm run dev       # run from source over stdionode test_mcp.mjs # smoke test: connect, list tools, call one

Tools are declared in one table in src/index.ts. Each entry carries its zod schema and its advertised JSON Schema side by side, so adding a tool means adding one entry, and the two shapes cannot drift apart.

Source: README.md at commit e714e14

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts