Disney Parks

Provides Disney parks data via MCP for attractions, dining, and entities with caching and search.

javascript

0

GitHub Stars

javascript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "cameronsjo-mouse-mcp": {
      "command": "node",
      "args": [
        "/path/to/mouse-mcp/dist/index.js"
      ],
      "env": {
        "MOUSE_MCP_DB_PATH": "~/.cache/mouse-mcp/disney.db",
        "MOUSE_MCP_TIMEOUT": "30000",
        "MOUSE_MCP_HEADLESS": "true",
        "MOUSE_MCP_LOG_LEVEL": "INFO"
      }
    }
  }
}

You run a Disney Parks MCP Server that serves structured park data to clients. It fetches attraction, dining, and general park entity information, caches results for fast responses, and provides fuzzy search capabilities so you can discover items even when you don’t know the exact name. This server is designed to be consumed by MCP clients and integrated into Claude Code or other MCP-enabled workflows.

How to use

You access the Disney Parks MCP Server by running it as a local MCP endpoint and connecting your MCP client to it. The server exposes functions to list destinations, query attractions and dining options for a given park or destination, look up specific entities by id or name, and check server health and cache statistics.

From your MCP client, add a connection named after the Disney destination you want to query and point it at the Disney MCP server. Use the available tools to fetch destinations, filter attractions by height, lightning lane status, thrill level, or single rider availability, and retrieve dining locations with service type, meal periods, and reservation information. You can also perform fuzzy name searches to locate entities when you aren’t sure of the exact title.

How to install

Prerequisites you need on your development machine:

Node.js and npm installed on your system.

Install dependencies and build the MCP server:

npm install
npm run build

Configuration and run

To run the Disney MCP Server locally in a typical setup, you use the stdio mode to start the server with Node.js and point to the built entry file.

{
  "mcpServers": {
    "disney": {
      "command": "node",
      "args": ["/path/to/mouse-mcp/dist/index.js"]
    }
  }
}

Development

If you are actively developing, you can run in development mode with auto-reload and also run type checks or tests as you modify the code.

# Run in development mode with auto-reload
npm run dev

# Type check without building
npm run check

# Test with MCP inspector
npm run inspector

Available tools

disney_destinations

List all supported Disney destinations with their parks.

disney_attractions

Get attractions for a destination or park with optional filters for height, Lightning Lane, thrill level, and single rider.

disney_dining

Get dining locations for a destination or park with filters for service type, meal period, reservations, and character dining.

disney_entity

Look up a specific entity by ID or fuzzy name search with optional destination and entity type.

disney_status

Get server health and cache statistics, with optional detailed breakdown.