# Oyez

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/pipeworx-io/mcp-oyez  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/oyez

## Description
Oyez SCOTUS MCP.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "oyez": {
    "command": "npx",
    "args": ["-y","oyez"]
  }
}
```

## Documentation & README

# mcp-oyez

Oyez SCOTUS MCP.

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.

## Tools

| Tool | Description |
|------|-------------|
| `search_cases` | Search US Supreme Court (SCOTUS) cases from Oyez by term year and/or case-name substring. Returns compact summaries with the question presented, description, and IDs for get_case. If neither term nor name is given, defaults to the most recent term. Keyless. |
| `get_case` | Get a full SCOTUS case from Oyez by term and docket number — question presented, facts, conclusion, decision (winning party, vote split, decision type), which justices were in the majority vs. dissent, advocates, and whether oral-argument audio exists. Keyless. |
| `cases_by_term` | List the SCOTUS cases for a given term year from Oyez — compact summaries (name, docket, citation, short question, oyez_url). Use to browse a full term. Keyless. |

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "mcpServers": {
    "oyez": {
      "url": "https://gateway.pipeworx.io/oyez/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/oyez/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:

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

Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.

## Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:

```
ask_pipeworx({ question: "your question about Oyez data" })
```

The gateway picks the right tool and fills the arguments automatically.

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT