# Oregon Open Data [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/pipeworx-io/mcp-data-oregon  
**GitHub Stars:** 1  
**npm Downloads (last month):** 1195  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/oregon-open-data

## Description
Oregon state open data via Socrata SoQL — agencies, business, health, environment.

## Tools
Capabilities this server exposes over MCP:

- **datasets** — Search the Oregon 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 Oregon Open Data dataset by resource_id (e.g. "tckn-sxa6"). Filter with where/select/group/order (SoQL clauses, without the leading $) plus limit/offset. Returns matching rows as JSON.
- **metadata** — Get a Oregon Open Data dataset's schema + metadata (columns, types, row count, category, last-updated) by resource_id, e.g. "tckn-sxa6".

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

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

## Documentation

## What Oregon Open Data does

Oregon Open Data exposes Oregon's public data catalog to MCP-compatible clients. The underlying service is data.oregon.gov, accessed through the Socrata SoQL API. Its catalog includes datasets from state agencies and areas such as business, health, and the environment.

The server provides three dataset-focused tools. `datasets` finds catalog entries by keyword and returns each result's resource ID, name, description, category, and update date. `metadata` uses a resource ID to return a dataset's schema and related details, including columns, data types, row count, category, and last-updated information. `query` runs a SoQL query against a selected dataset and returns matching records as JSON.

## How it works

A typical workflow starts with `datasets`, followed by `metadata` to inspect the available fields. The resource ID can then be passed to `query`. Query arguments support the `where`, `select`, `group`, and `order` SoQL clauses, along with `limit` and `offset`. Clause values are supplied without the leading `$` used in direct URL query syntax.

The hosted MCP endpoint is:

```text
https://gateway.pipeworx.io/data-oregon/mcp
```

The endpoint also exposes shared Pipeworx gateway tools alongside the Oregon-specific tools. A full gateway connection is available at `https://gateway.pipeworx.io/mcp`; both endpoints reach the same gateway and data sources, while the scoped endpoint lists the Oregon pack directly.

For clients or scripts that do not use MCP, individual tools can be called through the gateway's HTTP API. For example, the `datasets` tool is available at `/v1/tools/data_oregon_datasets`.

## Setup and configuration

Add the hosted endpoint to an MCP client such as Claude Desktop, Cursor, or Windsurf:

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

A local npm bridge is also available. Configure the client to run `npx -y @pipeworx/mcp-data-oregon`; the bridge forwards requests to the hosted endpoint and requires network access.

Anonymous calls are supported and limited to 50 calls per day. A free Pipeworx account increases the allowance to 200 calls per day. Add `PIPEWORX_API_KEY` to the npm server's environment to authenticate with a key. Set `PIPEWORX_META_TOOLS=1` when the local bridge should also list the shared gateway tools.

## Tools and capabilities

- `datasets`: Search the Oregon Open Data catalog by keyword.
- `metadata`: Inspect a dataset's fields, types, row count, category, and update timestamp.
- `query`: Run filtered, grouped, ordered, paginated SoQL queries and receive JSON rows.
- HTTP access: Invoke tools through the Pipeworx `/v1/tools` API without an MCP client.
- Plain-language routing: Use the gateway's `ask_pipeworx` tool to have the gateway select and populate a tool call.

## Limitations and notes

The integration is unofficial and is not affiliated with, endorsed by, or published by the upstream Oregon data provider. The npm bridge is not an offline implementation; it forwards calls over the network. Hosted and authenticated calls are subject to Pipeworx usage limits and metering. Pack endpoints necessarily include shared Pipeworx meta-tools, so their tool list is larger than the three Oregon-specific tools.

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