{
  "markdown": "# @pipeworx/ia-dmv\n\nIowa DOT Motor Vehicle Division driver license stations — hours, CDL testing, and the live\nqueue cameras Iowa points at its own waiting rooms. Keyless.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Why Iowa gets its own pack\n\nThis came out of splitting a single multiplexed `us-dmv` tool into one pack per state agency.\nIowa's motor-vehicle surface is a small, unusually rich station layer: 18 stations, but each one\nships **live camera image URLs and a wait-time widget**, which no other state publishes. Nothing\nabout that shape generalises across a union schema, so Iowa gets its own tool.\n\n## Tools\n\n| Tool | What it returns |\n|---|---|\n| `ia_dmv_driver_license_stations` | Address, per-day hours, phone, coordinates, CDL testing flag, station page, wait-time widget URL and up to four live queue-camera image URLs |\n\nFilters: `city`, `name`, `cdl_only`, `limit`.\n\n## The distinctive field\n\n`url_cam1..url_cam4` are live JPEG snapshots of the station lobby, refreshed by Iowa DOT — e.g.\n`https://mvdphotos.iowadot.gov/MasonCityDL.jpg`. Returned as `queue_camera_urls`, they let a\ncaller *see* the queue rather than guess at it. `wait_times_url` is Iowa's own per-station wait\nwidget. 17 of the 18 stations do CDL testing.\n\n## Auth\n\nNone. The layer is a public ArcGIS Online feature service owned by Iowa DOT.\n\n## Gotchas worth knowing\n\n- **The upstream `state` column is dirty.** It contains the literal `\", IA\"` — with a leading\n  comma — on every row. It is not passed through; `state` is normalised to `IA`.\n- **No latitude/longitude columns exist** on this layer, so the query requests WGS84 geometry\n  (`outSR=4326`) and reads coordinates from there.\n- **A second camera slot is often a \"closed\" placeholder.** Mason City's `url_cam4` points at\n  `MasonCityClosed.jpg`. All non-empty slots are returned as published rather than guessed at.\n- **Hours list open days only.** `hours_*` carries the literal `Closed` for the rest; a day\n  absent from `hours` is a closed day.\n- **There is no county column.** Iowa DOT keys these stations by city. `county` is null by\n  design; filter by `city`, or use the coordinates.\n- **18 stations for the whole state**, so most Iowa towns have none. The not-found hint says so\n  and points the caller at the full list plus coordinates rather than implying a data gap.\n\n## What is *not* buildable for Iowa today\n\nIowa's richest motor-vehicle data — county-level vehicle registrations and fleet summaries —\nlives on `data.iowa.gov`, which **migrated off Socrata**. Every old API path\n(`/resource/<id>.json`, `/api/views/...`) now answers with an HTML 404 page from the new portal\nfront end rather than JSON, so a registration tool would be building on a dead endpoint.\nRecheck when the new Iowa Data Hub exposes an API; until then this pack is stations only,\ndeliberately.\n\n## Data source\n\n- [Iowa DOT ArcGIS `DLSv2_View/FeatureServer/0`](https://services.arcgis.com/8lRhdTsQyJpO52F1/arcgis/rest/services/DLSv2_View/FeatureServer/0)\n  — verified live 2026-07-30\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"ia-dmv\": {\n      \"url\": \"https://gateway.pipeworx.io/ia-dmv/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/ia-dmv/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Ia Dmv data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 5112,
  "sha": "e3f58c13fbbcba14a2bdb18f0cd28390cfc619ecad1f56925400c39268cac26e",
  "repo_slug": "pipeworx-io/mcp-ia-dmv",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_ia_dmv_b9738f36/readme"
}