Data Baltimore

What Data Baltimore does

Data Baltimore exposes Baltimore city open data through MCP, using the ArcGIS REST API behind data.baltimorecity.gov. It is intended for questions that require structured records rather than general web results, including recent crime reports and Baltimore 311 service requests.

The server has three pack-specific tools:

• baltimore_recent retrieves newest-first records from common datasets using friendly names such as crime and 311.
• baltimore_layers discovers the layers available in a known Baltimore service or in a supplied ArcGIS service path.
• baltimore_query runs a query against a selected ArcGIS service and layer.

Date values returned as ArcGIS epoch timestamps are converted to ISO format.

How it works

For common datasets, call baltimore_recent with a friendly dataset name and an optional limit. The tool also accepts an ArcGIS where filter. When the required data is in another service, first use baltimore_layers to identify the service and layer ID, then pass those values to baltimore_query.

baltimore_query supports the main parts of an ArcGIS query: where, out_fields, order_by, and limit. The layer discovery tool accepts short names such as crime, service_requests, and permits, or a full path such as 311_Customer_Service_Requests_current/FeatureServer. Leaving its service argument empty lists known Baltimore services.

Setup and configuration

The package can run as a local stdio MCP server with no Pipeworx account:

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

Run npx -y @pipeworx/mcp-data-baltimore directly to start the local process. The standalone process communicates over stdin and stdout and exposes only this pack's tools.

For a hosted connection, configure the streamable HTTP endpoint:

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

The same gateway also offers a full endpoint at https://gateway.pipeworx.io/mcp. HTTP callers can invoke tools through endpoints such as /v1/tools/baltimore_recent using a JSON POST request.

Tools and capabilities

• Retrieve recent crime or 311 records by friendly dataset name.
• Apply an ArcGIS where clause to recent-record requests.
• Enumerate known Baltimore services and their layer IDs and names.
• Discover layers from a supplied ArcGIS FeatureServer path.
• Query any selected Baltimore ArcGIS layer.
• Select returned fields, sort results, and cap result counts.
• Convert epoch date fields to ISO-formatted dates.

Limitations and notes

The gateway pack endpoint lists the Baltimore tools alongside shared Pipeworx meta-tools, so its tool list is larger than the three pack-specific tools. The local stdio mode exposes only the Baltimore pack. The gateway's ask_pipeworx tool can route plain-language questions to tools across the wider Pipeworx catalog.

This is an independent, unofficial integration and is not affiliated with, endorsed by, or published by the upstream Baltimore data provider. The project is licensed under MIT.