Data Mo

What Data Mo does

Data Mo connects MCP-compatible AI clients to Missouri Open Data at data.mo.gov, which uses the Socrata platform. It provides three dataset-focused tools:

• datasets searches the Missouri catalog by keyword and returns each match’s resource ID, name, description, category, and update date.
• metadata retrieves a dataset’s schema and related information, including columns, data types, row count, category, and last-updated value.
• query runs a Socrata SoQL query against a dataset identified by its resource ID and returns matching rows as JSON.

A typical workflow starts with datasets, continues with metadata to understand available fields, and then uses query to retrieve the needed records. Example resource IDs include gfq7-aa86.

How it works

The hosted MCP endpoint is available at https://gateway.pipeworx.io/data-mo/mcp. A client can connect to that URL directly and invoke the Data Mo tools. The endpoint also exposes shared Pipeworx meta-tools, including ask_pipeworx, discover_tools, search_within, and memory-related tools. These shared tools are listed alongside the pack’s own tools and can route requests across Pipeworx’s broader catalog.

The query tool accepts SoQL clauses without their leading dollar signs. Supported query inputs include where, select, group, and order, along with limit and offset. The full Pipeworx gateway is also available at https://gateway.pipeworx.io/mcp; both endpoints use the same gateway and data sources, while the pack endpoint lists Data Mo tools directly.

Setup and configuration

Add the hosted endpoint to an MCP client using a server entry like this:

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

A local stdio option is available through the @pipeworx/mcp-data-mo npm package. The client starts it with npx, and the bridge forwards requests to the hosted Data Mo endpoint. It requires network access and has no offline mode:

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

Calls can also be made without an MCP client. For example, the datasets tool is available through the Pipeworx HTTP API at /v1/tools/data_mo_datasets.

Tools and capabilities

• Search Missouri’s open-data catalog by keyword.
• Retrieve dataset identifiers and descriptive catalog fields.
• Inspect schemas, column types, row counts, categories, and update timestamps.
• Run SoQL selections, filters, grouping, and ordering.
• Page through query results with limits and offsets.
• Ask ask_pipeworx to select and populate a relevant tool across the Pipeworx catalog.

Limitations and notes

The integration is independent and unofficial; it is not affiliated with, endorsed by, or published by the upstream Missouri Open Data provider. Anonymous npm-bridge usage is capped at 50 calls per day. A free Pipeworx account and API key increase that allowance to 200 calls per day; authenticated calls use a Bearer token and are metered and billed in the same way as hosted calls.

The npm bridge lists only Data Mo’s tools by default. Set PIPEWORX_META_TOOLS=1 to include the shared gateway tools as well. The hosted pack endpoint includes those shared tools automatically, so its total tool listing is larger than the three Data Mo tools. If an HTTPS proxy is required, Node’s built-in fetch does not use HTTPS_PROXY by default; newer Node versions can honor it when NODE_USE_ENV_PROXY=1 is set.