# Cataas [Health: Active]

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

## Description
CATAAS MCP — Cat as a Service (free, no auth)

## Tools
Capabilities this server exposes over MCP:

- **random_cat** — Get a random cat image. Returns image URL, cat ID, and associated tags.
- **cat_by_tag** — Get a random cat image matching a specific tag (e.g., 'orange', 'cute', 'sleepy'). Returns image URL, cat ID, and tags.
- **list_tags** — List all available cat tags for filtering. Use tag names with cat_by_tag to find cats by appearance or behavior.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

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

## Documentation & README

# mcp-cataas

CATAAS MCP — Cat as a Service (free, no auth)

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

## Tools

| Tool | Description |
|------|-------------|
| `random_cat` | Get a random cat image. Returns image URL, cat ID, and associated tags. |
| `cat_by_tag` | Get a random cat image matching a specific tag (e.g., 'orange', 'cute', 'sleepy'). Returns image URL, cat ID, and tags. |
| `list_tags` | List all available cat tags for filtering. Use tag names with cat_by_tag to find cats by appearance or behavior. |

## Quick Start

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

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

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/cataas/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 Cataas 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