In Bmv MCP server

@pipeworx/in-bmv

Indiana DMV data: Bureau of Motor Vehicles (BMV) branches, self-service kiosks, BMV Connect locations, motorcycle rider-training (RSI) courses and skills-test sites. Keyless.

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

What Indiana calls its DMV

Indiana's agency is the Bureau of Motor Vehicles, universally the BMV. Hoosiers say "BMV branch" where other states say "DMV office", so the tool description names both.

Tools

Filters: city, name, zip, locationtype, kioskonly, limit.

Auth

None. The source is a plain static JSON file on in.gov — no key, no query parameters, no rate limit to negotiate. The whole file is fetched and filtered in code.

Location type is the main axis of this data

One file covers six categories, which is unusual — most states publish only their staffed offices. Live counts as of 2026-07-30:

locationtype accepts those exact labels and also plain words — "branch", "kiosk", "connect", "motorcycle", "rider training", "skills test". kioskonly: true is the separate hasKiosk flag and keeps 72 of the 160 (the 60 "Branch + Kiosk" plus the 11 BMV Connect kiosks and one more).

Gotchas worth knowing

These are live-verified behaviours, not guesses:

null so a caller can test for absence instead of comparing against the empty string.

• website is an empty string on 127 of 160 rows, not null. The tool normalises "" to

organisations (ABATE of Indiana, Harley dealers) that schedule by appointment rather than posting counter hours; the tool leaves those null rather than inventing a schedule.

• hours is null on 43 rows. RSI training courses and skills-test sites are run by partner

five-digit ZIP still matches.

• url on an RSI row points at the partner, not at in.gov.
• No county column. Indiana's branch map keys off coordinates, so county comes back null.
• ZIPs are sometimes ZIP+4 (46203-6063). The zip filter is a prefix match, so a

several are motorcycle-training sites — use location_type="branch" when the caller wants a place to renew a licence.

• RSI rows are not branches. A city filter like "Indianapolis" returns 12 locations, and

Data sources

bmv-branchmap-locations.json

• in.gov BMV branch map —

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "in-bmv": {
      "url": "https://gateway.pipeworx.io/in-bmv/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/in-bmv/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, 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.

Shortened. The full README is on GitHub.