local-city-mcp
A template and specification for building MCP servers that provide AI assistants access to official, public civic data about a metro area, including property records, permits, schools, and public safety information.
README
local-city-mcp
The home for the local-{city}-mcp family: the spec, the list of cities
built so far, and the template repo for building a new one — all in one
place.
local-{city}-mcp is an MCP server that gives an AI assistant plain-English
access to official, public, no-key data about one metro area — property
records, permits, civic data, schools, environment, public safety, and
(where the maintainer has the right) real estate listings.
Before you touch any code, read STANDARD.md. It's the spec: the hard rules, the tool contract, the testing bar, and the licensing pattern. Everything else here just tells you how to use the template mechanically; STANDARD.md tells you why it's built this way.
Reference implementation this was extracted from: local-austin-mcp (43 tools, live in production).
The list
| City | Repo | Tools | Maintainer | CI |
|---|---|---|---|---|
| Austin, TX | local-austin-mcp | 43 | Ed Neuhaus | |
| Dallas, TX | local-dallas-mcp | 3 | Ed Neuhaus | |
| Houston, TX | local-houston-mcp | 2 | Ed Neuhaus | |
| San Antonio, TX | local-san-antonio-mcp | 3 | Ed Neuhaus |
(Your city not here yet? Build one below, then open a PR adding a row.)
Using one
Add to your Claude Desktop config (or any MCP client's config):
{
"mcpServers": {
"local-austin": {
"command": "npx",
"args": ["-y", "github:mindwear-capitian/local-austin-mcp"]
}
}
}
Swap the repo for whichever city you want from the table above.
Building a new one
-
Use this template — GitHub's "Use this template" button on this repo, or:
gh repo create local-{city}-mcp --template mindwear-capitian/local-city-mcp-templateThis copies everything in this repo, including this README's list table. Replace this whole README with your own city's (see step 5) — the table above is this repo's index, not part of your city's docs.
-
Replace every placeholder. Every file that needs per-city values uses bare
{{TOKEN}}markers (no leading$— deliberate, so they never collide with${{ }}GitHub Actions expression syntax in.github/workflows/ci.yml, which you should leave untouched). Find them all with:grep -rl '{{[A-Z_]*}}' --include='*.js' --include='*.json' --include='*.md' .Token Example Where it's used {{CITY}}DenverDisplay name, in prose {{CITY_SLUG}}denverTool prefix, package name, repo name {{CITY_SLUG_UPPER}}DENVEREnv var name ( LOCAL_DENVER_MCP_TIER){{MAINTAINER_NAME}}Jane DoeAttribution, package.json author {{MAINTAINER_URL}}https://janedoe.comAttribution, homepage {{GITHUB_USER}}janedoeRepo URLs {{DEFAULT_LAT}}/{{DEFAULT_LNG}}39.74,-104.99Default map center for the example NWS tool A one-shot sed pass works fine for a first pass — just review the diff before committing, since a couple of tokens (like
{{CITY}}inside prose sentences) are case-sensitive on purpose. -
Run it:
npm install npm start # runs the MCP over stdio npm test # unit tests npm run test:contract # boots the server, calls every tool via the real MCP layer -
Build your first real tool. See CONTRIBUTING.md — copy
tools/environment/nws-alerts.js(works for any US city untouched once you fill in the placeholders) as your pattern reference, ortools/meta/about.jsfor the minimal shape. -
When it's real: replace this README with your city's own (tool table,
Sources of Truthtable, Architecture section — see local-austin-mcp's README for the shape once you have more than a couple of tools). -
Get listed: once
test:contractis green in CI and you meet STANDARD.md §2, open a PR against this repo adding one row to the table above. See CONTRIBUTING.md.
What's already built for you
| File | What it gives every tool for free |
|---|---|
lib/register.js |
Central registration: default MCP annotations, error→friendly-frame wrapping, structuredContent auto-promotion, tier gating |
lib/retry.js |
retryFetch() with jittered backoff + UpstreamError + LLM-friendly error text ("the MCP is fine, the upstream is having a problem") |
lib/request-context.js |
Propagates the MCP request's AbortSignal into every downstream fetch via AsyncLocalStorage, so client-side cancellation actually cancels in-flight calls |
lib/output-schemas.js |
Shared Zod shapes (searchShape, openObjectShape, etc.) for outputSchema |
lib/geocode.js |
U.S. Census geocoder — free, no key, works nationwide |
lib/soda.js |
Generic Socrata (SODA) open-data client — works against any city or state's Socrata portal, not just your own (proven: same client, zero changes, powers Austin's permits/311/crime data, the statewide TX TEA dataset, AND Dallas's 311) |
lib/arcgis.js |
Generic ArcGIS FeatureServer/MapServer client — many cities publish 311, GIS, and property layers this way when they aren't on Socrata (proven: powers Austin's county appraisal + FEMA flood tools AND San Antonio's 311) |
lib/semaphore.js |
Named per-source concurrency caps (withLimit) so a fan-out composed tool doesn't hammer one upstream |
lib/logger.js |
stderr + MCP logging-notification logger |
lib/tiers.js |
Optional core/all tool-tier gating for once you have 20+ tools |
tools/meta/about.js |
Minimal tool example + the required about capability tool |
tools/environment/nws-alerts.js |
A real, working example tool (National Weather Service alerts) — copy its shape |
test/mcp-all-tools.js |
The required contract test (STANDARD.md §6) |
.github/workflows/ci.yml |
Unit tests on Node 20 + 22 on every push. Skips cleanly (not a failure) when run against the raw, unfilled template. |
.github/workflows/contract.yml |
The live-upstream contract test, on a daily schedule + manual dispatch — deliberately NOT on every push (would make PRs flaky on third-party uptime). |
None of this is speculative — it's copied from a production server that
shipped 40+ tools. Read lib/register.js and lib/retry.js top-of-file
comments for the reasoning if you're wondering why a piece exists.
License
The template code (lib/, tools/, index.js, tests, CI) is Apache
License 2.0 (see LICENSE) — use it, fork it, build a commercial
product on it. Fill in NOTICE and TRADEMARK.md with your own name/marks
before you ship; the placeholders in those files are examples, not defaults
you inherit. This README's list-curation text is not separately licensed —
it's not code, do with it what you like.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.