Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Your AI's DFW guide: events, appraisals, Dallas 311, crime, floods, schools, utilities, districts.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
DFW_TICKETMASTER_API_KEY, DFW_SODA_APP_TOKENValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"local-dfw": {
"command": "npx",
"args": [
"-y",
"local-dfw-mcp"
],
"env": {
"DFW_TICKETMASTER_API_KEY": "your-value",
"DFW_SODA_APP_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add local-dfw --env DFW_TICKETMASTER_API_KEY=your-value --env DFW_SODA_APP_TOKEN=your-value -- npx -y local-dfw-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"local-dfw": {
"command": "npx",
"args": [
"-y",
"local-dfw-mcp"
],
"env": {
"DFW_TICKETMASTER_API_KEY": "your-value",
"DFW_SODA_APP_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"local-dfw": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"local-dfw-mcp"
],
"env": {
"DFW_TICKETMASTER_API_KEY": "your-value",
"DFW_SODA_APP_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account LizzleChen, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: DFW_TICKETMASTER_API_KEY, DFW_SODA_APP_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.4) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Tethered Trust
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Your AI's local guide to Dallas–Fort Worth. An open-source MCP server that connects Claude (or any MCP client) to official city, county, state, and federal data — so you can ask things like:
Every answer comes from an authoritative public source and includes a link to the official record. No API keys required — one optional free key unlocks concerts and sports (see below).
Add this to your MCP client config (Claude Desktop, Claude Code, etc.):
{
"mcpServers": { "local-dfw": { "command": "npx", "args": ["-y", "local-dfw-mcp"] } } }
Requires Node ≥ 20. That's it — restart your client and start asking.
| Tool | Coverage | What it answers |
|---|---|---|
dfw_events | see below | What's happening: official city calendars, plus concerts/sports/theater with a free Ticketmaster key |
dfw_311 | City of Dallas only | 311 service requests by address/type/status |
dfw_crime | City of Dallas (default), Fort Worth (city: "fortworth"), or Denton (city: "denton") | Police incidents by (block-level) address / offense |
dfw_permits | Fort Worth (default), McKinney (city: "mckinney", requires address), or Arlington (city: "arlington") | Building/development permits by street name (+ house number) or address, type, or status |
dfw_code_cases | Fort Worth (default), McKinney (city: "mckinney"), or Arlington (city: "arlington") | Code-compliance violations (property maintenance, high grass, zoning, etc.) by address or complaint type |
dfw_traffic | see below | Real-time incidents (Fort Worth), street/lane closures (Dallas + Arlington, merged and labeled by city), TxDOT annual traffic counts + construction projects (4 core counties) |
dfw_fema_flood | national | FEMA flood zone + plain-English insurance interpretation |
dfw_tea_schools | Texas | Public schools + TEA A–F ratings (2022-23) by campus/district/county |
dfw_nws_alerts | national | Active NWS weather alerts for a DFW point |
dfw_utility_providers | Texas | Who provides water/sewer at an address (PUC CCN) |
dfw_district_lookup | DFW | County, City-of-Dallas council district + member, ISD for an address |
dfw_appraisal | Texas (4 core counties verified) | County appraisal record for an address: owner, land/improvement/market value (2025 certified roll), year built, land use, acreage |
dfw_health | — | Pings every upstream, reports per-source status |
about | — | Version, coverage, license, provenance |
| Source | Cities / scope | Key needed |
|---|---|---|
| Official city calendars | Dallas (Parks & Recreation calendar only — no citywide Dallas feed exists), Garland, Frisco, Mesquite, McKinney | none |
| Ticketmaster (concerts, sports, theater) | whole metroplex | free key, see below |
Plano, Arlington, Fort Worth, Irving, and other suburbs don't publish a usable calendar feed today — the tool says "not covered" instead of guessing.
There's no composed "property report" tool (yet) — there doesn't need to be. The tools share natural join keys: address, lat/lon, parcel, council district, and ISD, so your AI can chase a question across them:
dfw_appraisal (what's it worth, who owns it) → dfw_fema_flood (flood zone + insurance) → dfw_district_lookup (county, council district, ISD) → dfw_tea_schools (rate that ISD's campuses) → dfw_crime (incidents nearby) → dfw_utility_providers (who to call for water/sewer).dfw_permits (what's being built) → dfw_code_cases (violations on the same address) → dfw_311 (what neighbors are reporting).dfw_events (what's on) → dfw_traffic (incidents and closures on the way) → dfw_nws_alerts (weather worth knowing about).Ask the composite question ("we're thinking about buying near Frisco — check schools, flood risk, and what it's appraised at") and a capable client walks the chain itself.
Everything works out of the box. Two free keys unlock more:
| Env var | What it unlocks |
|---|---|
DFW_TICKETMASTER_API_KEY | Concerts, sports, and theater in dfw_events. Free (5000 calls/day): https://developer.ticketmaster.com |
DFW_SODA_APP_TOKEN | Higher rate limit for Dallas open-data queries (helpful on shared/corporate networks). Free: https://dev.socrata.com/register |
Advanced knobs
| Env var | Purpose |
|---|---|
DFW_LIMIT_ | Per-upstream concurrency cap override (SODA, ARCGIS, FEMA, CENSUS, NWS) |
LOCAL_DFW_MCP_TIER | core or all — trims the tool list for clients with tool caps |
DFW_CACHE_DISABLED | 1 disables the in-process cache (used by tests) |
No telemetry. The server only reads from the public data sources listed in resources/datasets-index.md and writes to nothing.
dfw_permits and dfw_code_cases are Fort Worth + McKinney + Arlington only: every current Dallas permit feed is ~20 months stale and Dallas's code-case publication stalled 2025-01-31, so Dallas isn't wired for either. Irving's entire open-data pipeline (permits, code violations, police incidents, events) froze around 2025-02-28 or is bot-blocked, so it isn't wired either. Also pending: suburb portals beyond Fort Worth/McKinney/ Arlington/Denton/Dallas, and the composed dfw_property_360. Details in resources/datasets-index.md.source_url to the official record.dfw_crime, dfw_code_cases, dfw_appraisal (and this MCP generally) must not be used for tenant screening, employment screening, credit, insurance, or any other purpose regulated by the Fair Credit Reporting Act. Crime addresses are block-level, privacy-rounded upstream. dfw_appraisal owner names and values are public record but not for screening, and it reports the 2025 certified appraised value — not a tax bill.Apache-2.0. See LICENSE and NOTICE.
Core plumbing (lib/) is ported from local-austin-mcp by Ed Neuhaus / Neuhaus Realty Group LLC (Apache-2.0) — an excellent template for city-scale civic MCPs. Each ported file carries an attribution header listing the changes. All DFW data sources, the metro router, and the tools themselves are new.