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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。