Data Mesa

What Data Mesa MCP server does

Data Mesa gives MCP-compatible agents access to the Mesa Open Data catalog at citydata.mesaaz.gov. The catalog is backed by Socrata, so agents can discover datasets and then work with their structured records through MCP tools.

The datasets tool searches the catalog by keyword and returns identifiers, names, descriptions, categories, and update dates. Those identifiers are used with the other tools. metadata reports a dataset’s columns, data types, row count, category, and last-update information. query runs a Socrata SoQL request and returns matching rows as JSON.

This is a fit for questions involving public Mesa datasets, such as finding a relevant catalog resource, checking its available fields, or retrieving a filtered set of records for analysis.

How it works

The hosted MCP endpoint is:

https://gateway.pipeworx.io/data-mesa/mcp

An MCP client connects to that URL and invokes the catalog tools. A typical workflow is to search with datasets, inspect the chosen resource with metadata, and then pass its resource_id to query.

Queries accept SoQL clauses through where, select, group, and order; these values are supplied without the leading $. limit and offset support result sizing and pagination. The gateway also exposes shared Pipeworx meta-tools on the hosted pack endpoint, including ask_pipeworx, discover_tools, search_within, and remember/recall. Setups that need only the pack’s direct tools can use the local bridge’s default behavior.

Setup and configuration

Add the hosted URL to an MCP client configuration, or run the npm package as a local stdio process:

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

The npm bridge forwards requests to the hosted gateway and therefore requires network access; it has no offline mode. Anonymous use is limited to 50 calls per day. A free Pipeworx account increases the allowance to 200 calls per day. Supply the account key as PIPEWORX_API_KEY in the MCP server environment when using authenticated access.

Set PIPEWORX_META_TOOLS=1 if the local bridge should also list the gateway-wide meta-tools. Behind an HTTPS proxy, Node’s built-in fetch may require NODE_USE_ENV_PROXY=1 on Node versions that support that option.

The tools can also be called over HTTP. For example, the datasets operation is available at https://gateway.pipeworx.io/v1/tools/data_mesa_datasets with a JSON request body.

Tools and capabilities

• datasets: search Mesa’s open-data catalog by keyword.
• metadata: inspect schema, column types, row count, category, and update information.
• query: execute SoQL with selection, filtering, grouping, ordering, limits, and offsets.
• ask_pipeworx: ask a natural-language question through the gateway’s cross-catalog routing layer when meta-tools are enabled or when using the full gateway.

Limitations and notes

The integration is unofficial and is not affiliated with, endorsed by, or published by Mesa or the upstream data provider. Requests depend on the hosted Pipeworx gateway and network connectivity. The scoped endpoint includes shared gateway tools in addition to the three Data Mesa tools, while the full Pipeworx endpoint exposes all available packs directly. Anonymous and authenticated calls are subject to the stated daily allowances, and authenticated calls use a Bearer token and are metered according to Pipeworx’s service terms.