
Disney Mcp
io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026
Disney character data from the Disney API. No key required.
Overview
A local MCP server that gives an assistant access to Disney character data from the Disney API, with no key required.
- What you can do
- Provides Disney character data sourced from the Disney API, so an assistant can look up and work with Disney character information during a conversation. The manifest lists no individual tools, so the exact operations are not documented; expect read-style lookups rather than management features. It runs as a local process over stdio and is intended for desktop use.
- When to use it
- Worth adding when you want an assistant to answer questions or build content around Disney characters using the public Disney API, and you prefer a local, keyless setup.
- Requirements
- Runs as a local process on the user's machine over stdio, installed from the npm package disney-mcp, so a Node.js runtime is needed. No API key, environment variables or headers are declared. Network access is implied because the data comes from the Disney API. Desktop only; not available as a web executable.
Installation
In SourceWeft
- Open Disney Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.1LatestSep 22, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.