Rick And Morty

mcp-rick-and-morty

Rick and Morty MCP — wraps the Rick and Morty API (free, no auth)

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

Tool	Description
search_characters	Search Rick and Morty characters by name with optional filters for status (alive/dead/unknown), species (Human/Alien/etc.), and gender. Returns up to 20 matching characters per page with status, species, origin, current location, and episode appearances.
get_character	Get a single Rick and Morty character by numeric ID. Returns name, status, species, origin, current location, episode appearances, and image URL.
search_episodes	Search Rick and Morty episodes by name or episode code (S01E03 style). Returns episode metadata including air date, character list, and ID.
get_episode	Get a single Rick and Morty episode by numeric ID. Returns title, code (e.g. "S01E03"), air date, and the list of characters that appear.
get_location	Get a single Rick and Morty location/planet/dimension by ID. Returns name, type, dimension, and residents.

Quick Start

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

{
  "mcpServers": {
    "rick-and-morty": {
      "url": "https://gateway.pipeworx.io/rick-and-morty/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/rick-and-morty/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:

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

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

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/rick_and_morty_search_characters \
  -H 'Content-Type: application/json' \
  -d '{"name":"rick"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/rick_and_morty_search_characters. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "rick-and-morty": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-rick-and-morty"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-rick-and-morty

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

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 Rick And Morty data" })

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

More

• Docs and guides
• pipeworx.io

License

MIT