# Texas Open Data [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/pipeworx-io/mcp-data-texas  
**GitHub Stars:** 0  
**npm Downloads (last month):** 1183  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/texas-open-data

## Description
Texas state open data via Socrata SoQL — agencies, health, licensing, transport, finance.

## Tools
Capabilities this server exposes over MCP:

- **datasets** — Search the Texas Open Data catalog of open datasets by keyword. Returns each dataset's resource_id, name, description, category and update date — pass the resource_id to query/metadata.
- **query** — Run a Socrata SoQL query against a Texas Open Data dataset by resource_id (e.g. "54pj-3dxy"). Filter with where/select/group/order (SoQL clauses, without the leading $) plus limit/offset. Returns matching rows as JSON.
- **metadata** — Get a Texas Open Data dataset's schema + metadata (columns, types, row count, category, last-updated) by resource_id, e.g. "54pj-3dxy".

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "texas-open-data": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-data-texas"],
    "env": {
      "PIPEWORX_API_KEY": "",
      "PIPEWORX_META_TOOLS": "",
      "NODE_USE_ENV_PROXY": ""
    }
  }
}
```

**Requires environment variables:** `PIPEWORX_API_KEY`, `PIPEWORX_META_TOOLS`, `NODE_USE_ENV_PROXY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Texas Open Data does

Texas Open Data exposes the data.texas.gov catalog to MCP clients through the Socrata SoQL API. It is intended for discovering and querying public datasets published by Texas government organizations, including agency, lottery, health, licensing, transportation, and finance data.

The server is an independent, unofficial integration. It is part of the Pipeworx gateway, which provides access to many data sources. The Texas-focused endpoint lists the pack's own tools and also includes shared Pipeworx meta-tools in its MCP tool list.

## How it works

A typical workflow starts with `datasets`, which searches the catalog by keyword and returns dataset identifiers, names, descriptions, categories, and update dates. Use the returned `resource_id` with `metadata` to inspect the available columns, their types, row count, category, and last-updated information. Then pass that identifier to `query` to retrieve rows.

Queries use Socrata SoQL clauses supplied without the leading dollar sign. Supported query controls include `where`, `select`, `group`, and `order`, along with `limit` and `offset`. Results are returned as JSON, making the server suitable for agents that need to discover a dataset before constructing a structured query.

The hosted MCP endpoint is available at `https://gateway.pipeworx.io/data-texas/mcp`. The full Pipeworx gateway is also available at `https://gateway.pipeworx.io/mcp`; both routes reach the same gateway and data sources, while the pack endpoint determines which tools are listed directly. The endpoint also supports direct HTTP tool calls under the gateway's `/v1/tools/` path.

## Setup and configuration

For a hosted connection, add the endpoint as an MCP server in a compatible client:

```json
{
  "mcpServers": {
    "data-texas": {
      "url": "https://gateway.pipeworx.io/data-texas/mcp"
    }
  }
}
```

A local npm bridge is available through `@pipeworx/mcp-data-texas`. Configure the client to start it with `npx`:

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

The bridge forwards requests to the hosted gateway and therefore requires network access. Anonymous use is available with a daily call limit. Setting `PIPEWORX_API_KEY` enables an account-backed allowance; the key is sent as a Bearer token. Set `PIPEWORX_META_TOOLS=1` if the local bridge should also list the shared gateway tools. When using an HTTPS proxy, newer Node.js releases may require `NODE_USE_ENV_PROXY=1` for the built-in `fetch` implementation to honor proxy settings.

## Tools and capabilities

- `datasets`: Search the Texas Open Data catalog by keyword.
- `metadata`: Retrieve a dataset's schema and catalog details by resource ID.
- `query`: Execute a SoQL query with filtering, selection, grouping, ordering, pagination, and JSON results.
- Shared Pipeworx meta-tools are available on the hosted pack endpoint; `ask_pipeworx` can route natural-language requests across the wider catalog.
- The tools can also be called over HTTP without an MCP client.

## Limitations and notes

The integration requires access to the network and has no offline mode. The npm bridge forwards calls to the Pipeworx gateway rather than querying Texas Open Data locally. Anonymous calls are capped at 50 per day, while a free Pipeworx account raises the allowance to 200 per day. The gateway's shared tools increase the number of tools shown by the hosted pack endpoint beyond the three Texas-specific tools. The project is unofficial and is not affiliated with, endorsed by, or published by the upstream Texas Open Data provider.

The package is released under the MIT license.

_Full upstream README: https://allmcps.com/mcp/texas-open-data/readme_