The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Iowa DOT Driver Licensing listing page.
Iowa DOT Motor Vehicle Division driver license stations — hours, CDL testing, and the live queue cameras Iowa points at its own waiting rooms. Keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
This came out of splitting a single multiplexed us-dmv tool into one pack per state agency.
Iowa's motor-vehicle surface is a small, unusually rich station layer: 18 stations, but each one
ships live camera image URLs and a wait-time widget, which no other state publishes. Nothing
about that shape generalises across a union schema, so Iowa gets its own tool.
| Tool | What it returns |
|---|---|
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 |
Filters: city, name, cdl_only, limit.
url_cam1..url_cam4 are live JPEG snapshots of the station lobby, refreshed by Iowa DOT — e.g.
https://mvdphotos.iowadot.gov/MasonCityDL.jpg. Returned as queue_camera_urls, they let a
caller see the queue rather than guess at it. wait_times_url is Iowa's own per-station wait
widget. 17 of the 18 stations do CDL testing.
None. The layer is a public ArcGIS Online feature service owned by Iowa DOT.
state column is dirty. It contains the literal ", IA" — with a leading
comma — on every row. It is not passed through; state is normalised to IA.outSR=4326) and reads coordinates from there.url_cam4 points at
MasonCityClosed.jpg. All non-empty slots are returned as published rather than guessed at.hours_* carries the literal Closed for the rest; a day
absent from hours is a closed day.county is null by
design; filter by city, or use the coordinates.Iowa's richest motor-vehicle data — county-level vehicle registrations and fleet summaries —
lives on data.iowa.gov, which migrated off Socrata. Every old API path
(/resource/<id>.json, /api/views/...) now answers with an HTML 404 page from the new portal
front end rather than JSON, so a registration tool would be building on a dead endpoint.
Recheck when the new Iowa Data Hub exposes an API; until then this pack is stations only,
deliberately.
DLSv2_View/FeatureServer/0
— verified live 2026-07-30Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
tools/list at https://gateway.pipeworx.io/ia-dmv/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
The gateway picks the right tool and fills the arguments automatically.
MIT