mcp-disney
Disney character database MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1878+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Potencia tu agente
La URL propia del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
https://gateway.pipeworx.io/disney/mcpEl botón de Claude de arriba abre Claude con el nombre y la URL ya rellenados. Aún tienes que confirmarlo allí.
claude mcp add --transport http io.github.pipeworx-io-disney https://gateway.pipeworx.io/disney/mcpRun in a terminal.
{ "mcpServers": { "io.github.pipeworx-io-disney": { "command": "npx", "args": [ "-y", "mcp-remote", "https://gateway.pipeworx.io/disney/mcp" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
Disney character database MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1878+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Disney character database MCP.
| 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 1878+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"disney": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-disney"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-disney
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.
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
{ "mcpServers": { "io.github.pipeworx-io-disney": { "url": "https://gateway.pipeworx.io/disney/mcp", "headers": {} } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración http para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
El publicador indica estas variables de entorno: PIPEWORX_API_KEY.
Se accede a Disney por HTTP.
Última comprobación: 2026-11-10. Disney character database MCP.