{
  "markdown": "# AddressIntel MCP server\n\nA read-only [Model Context Protocol](https://modelcontextprotocol.io) server that puts\nSF Peninsula building-permit and parcel-buildability data inside Claude, ChatGPT, or any\nother MCP-capable agent.\n\nIt is a thin client over the public AddressIntel API, so it inherits that API's auth,\nrate limits and tier ceilings. Every tool is a `GET`. Nothing here can write.\n\n## Tools\n\n| Tool | What it answers |\n|---|---|\n| `search_permits` | What 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. |\n| `list_sb9_inventory` | Which active listings can be split or duplexed under SB 9, and what blocks the ones that can't? |\n| `list_adu_leads` | Which parcels have room for an ADU, and how many units / how much square footage? |\n| `list_redevelopment_leads` | Which parcels are underbuilt against their allowable envelope (scrape-and-rebuild or expansion)? |\n| `list_market_signals` | Which listings score highest for teardown or flip potential? |\n| `get_property_intelligence` | Full scores and comparable sales for one property id. |\n\nThe permit and parcel tools are the differentiated half: permit-level detail and\nparcel-level buildability for the Peninsula, rather than a nationwide owner list.\n\n## Install\n\nNo install step: `npx` fetches it on demand.\n\n### Claude Code\n\n```bash\nclaude mcp add addressintel \\\n  -e ADDRESSINTEL_API_KEY=your_key \\\n  -- npx -y addressintel-mcp\n```\n\n### Claude Desktop\n\nAdd to `claude_desktop_config.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"addressintel\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"addressintel-mcp\"],\n      \"env\": {\n        \"ADDRESSINTEL_API_KEY\": \"your_key\"\n      }\n    }\n  }\n}\n```\n\n### From source\n\nFor working on the server itself:\n\n```bash\ngit clone https://github.com/RantumBits/addressintel-mcp.git\ncd addressintel-mcp\nnpm install\nnpm run build     # emits dist/index.js\n```\n\nThen point the client at `node /absolute/path/to/addressintel-mcp/dist/index.js` instead of\nthe `npx` command above.\n\nRestart the client, then ask it something like *\"what demolition permits were issued in\nMenlo Park this year?\"* or *\"which Palo Alto listings are SB 9 eligible?\"*\n\n## Configuration\n\n| Variable | Default | Notes |\n|---|---|---|\n| `ADDRESSINTEL_API_KEY` | `demo` | Without 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. |\n| `ADDRESSINTEL_API_BASE` | `https://addressintel.co/api` | Point at a local dev server (`http://localhost:3000/api`) when working on the API. |\n\n## Development\n\n```bash\nnpm run dev       # run from source over stdio\nnode test_mcp.mjs # smoke test: connect, list tools, call one\n```\n\nTools are declared in one table in `src/index.ts`. Each entry carries its zod schema and\nits advertised JSON Schema side by side, so adding a tool means adding one entry, and the\ntwo shapes cannot drift apart.\n",
  "bytes": 3095,
  "sha": "1d1ac6fe8c932c43e1758c8680ac43d3063fd7da41fd84c328d9d29a46724d89",
  "repo_slug": "rantumbits/addressintel-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_co_addressintel_permits_c354022e/readme"
}