
Gives you access to Disney character data through a remote MCP gateway hosted by Pipeworx. The source doesn't list specific tools, but it's designed to work with Pipeworx's ask_pipeworx interface where you ask questions in plain English rather than calling individual tools. You can connect to just the Disney endpoint or hook into the full Pipeworx gateway for 780+ data sources. Runs over streamable HTTP, so no local installation needed. Useful if you're building something that needs Disney character information and want a quick integration without managing your own API client or scraping anything yourself.
Disney character database MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
search_characters | Search the Disney character database by name (e.g. "Mickey Mouse", "Elsa", "Stitch"). Returns matching characters with their film, TV-show, video-game and theme-park-attraction appearances plus an image URL. Matching is exact-ish on the name field. |
get_character | Fetch a single Disney character by numeric id (_id). Returns the full record: films, short films, TV shows, video games, park attractions, allies, enemies, image URL and source URL. |
list_characters | List/paginate the Disney character database. Returns a page of characters (id, name, image URL) plus total count and total page count. Useful for browsing the full catalog. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"disney": {
"url": "https://gateway.pipeworx.io/disney/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/disney/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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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 Disney data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
curl -X POST https://gateway.pipeworx.io/v1/tools/disney_search_characters \
-H 'Content-Type: application/json' \
-d '{"name":"Mickey Mouse"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/disney_search_characters. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.