Data Montgomery

What Data Montgomery MCP server does

Data Montgomery exposes Montgomery County, Maryland open data from data.montgomerycountymd.gov through MCP. The underlying portal uses Socrata's SODA API, so agents can retrieve records from common county datasets or construct queries against other catalogue resources.

The server is suited to questions involving recent crime records, 311 requests, building permits, and other datasets published in the county catalogue. It can also locate datasets by keyword and return the Socrata resource identifiers needed for more specific queries.

How it works

A hosted MCP connection is available at https://gateway.pipeworx.io/data-montgomery/mcp. An MCP client can connect to that URL directly. The same gateway also exposes a broader endpoint at https://gateway.pipeworx.io/mcp; either endpoint can reach the gateway's wider routing capability through ask_pipeworx.

For local MCP configurations, @pipeworx/mcp-data-montgomery runs through npx as a stdio process and forwards requests to the hosted gateway. This mode still needs network access and does not provide offline operation. The gateway also offers HTTP tool calls, such as a POST request to /v1/tools/montgomery_recent.

Pack endpoints include shared Pipeworx meta-tools in addition to the pack-specific tools. The local npm bridge lists the Montgomery tools by default; setting PIPEWORX_META_TOOLS=1 adds the gateway-wide tools.

Setup and configuration

For a hosted connection, add the endpoint to an MCP client configuration:

{
  "mcpServers": {
    "data-montgomery": {
      "url": "https://gateway.pipeworx.io/data-montgomery/mcp"
    }
  }
}

The npm-based stdio option uses:

{
  "mcpServers": {
    "data-montgomery": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-data-montgomery"]
    }
  }
}

Anonymous calls are available with a daily limit of 50 calls. A free Pipeworx account increases the limit to 200 calls per day. Add the account key as PIPEWORX_API_KEY in the MCP server's environment when using authenticated access. The key is transmitted as a Bearer token.

Tools and capabilities

• montgomery_recent retrieves newest-first rows from the common 311, crime, or permits datasets. It accepts a friendly dataset name and can apply a SoQL where filter.
• montgomery_datasets searches the Montgomery County catalogue by keyword and returns matching dataset names, descriptions, and Socrata resource IDs.
• montgomery_query runs SoQL against any Montgomery County resource identified by its eight-character Socrata ID. Supported query controls include select, where, group, order, limit, and offset.

Use the catalogue search before a raw query when the relevant resource ID is unknown. For the common datasets, the recent-record tool avoids requiring an ID.

Limitations and notes

The integration is unofficial and is not affiliated with, endorsed by, or published by Montgomery County's upstream data provider. Results depend on the county's live Socrata data and network availability. The local bridge is a network forwarder rather than a local data store.

A scoped gateway connection exposes shared Pipeworx meta-tools alongside the Montgomery-specific tools, so the tool list can contain more entries than the three data tools described here. Calls made with an API key are metered and billed under the hosted gateway's terms.