MCP.so
登录
M

Mcp Server For Themeparks.wiki

@MasonMao-dev

关于 Mcp Server For Themeparks.wiki

This project provides a Model-Context-Protocol (MCP) server that interfaces with the ThemeParks.wiki API. It allows users to access real-time and static data for theme parks, including destinations, attractions, wait times, and schedules.

基本信息

分类

记忆与知识

传输方式

stdio

发布者

MasonMao-dev

提交者

91 M

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "mcp-server-theme-parks": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-theme-parks"
      ],
      "env": {
        "THEMEPARKS_API_BASE_URL": "https://api.themeparks.wiki/v1"
      }
    }
  }
}

工具

10

** Retrieves a list of all available top-level theme park destinations (e.g., Walt Disney World Resort, Universal Orlando Resort).

** None

** Fetches detailed static information for a specific entity (like a park, attraction, or restaurant) using its unique ID.

`entity_id` (string, UUID, required): The unique GUID identifier for the entity.

** Retrieves all direct child entities for a given parent entity ID (e.g., all parks within a destination, or all attractions within a park).

`entity_id` (string, UUID, required): The unique GUID identifier for the parent entity.

** Fetches live data for a specific entity and its children. This can include attraction wait times, park operating hours, and show times.

`entity_id` (string, UUID, required): The unique GUID identifier for the entity.

** Retrieves the operating schedule or calendar data for a specific entity. Can specify a year and month, or get general schedule data.

`entity_id` (string, UUID, required): The unique GUID identifier for the entity.

概览

What is MCP Server for ThemeParks.wiki?

The MCP Server for ThemeParks.wiki is a Model Context Protocol (MCP) server that integrates with the ThemeParks.wiki API. It provides AI assistants and MCP clients with real-time and static data for theme parks, including destinations, attractions, wait times, and schedules. It is designed for developers building LLM-powered applications that need park information.

How to use MCP Server for ThemeParks.wiki?

Install the package via npm (npm install mcp-server-theme-parks) and configure your MCP client to run it with npx -y mcp-server-theme-parks and set the environment variable THEMEPARKS_API_BASE_URL to https://api.themeparks.wiki/v1. Alternatively, clone the repository, build it, and run with node dist/index.js. Tools are invoked by the MCP client.

Key features of MCP Server for ThemeParks.wiki

  • List all top-level theme park destinations (e.g., Walt Disney World, Universal Orlando)
  • Fetch detailed static information for any entity by its UUID
  • Retrieve all direct child entities for a given parent entity
  • Get live data including attraction wait times and park hours
  • Access operating schedules for specific entities by year and month
  • Built-in help prompt summarizing all available tools

Use cases of MCP Server for ThemeParks.wiki

  • An AI travel assistant answering questions about current wait times at a specific park
  • A chatbot providing detailed information about a particular attraction or restaurant
  • A trip‑planning tool that retrieves park schedules and operating hours for future dates
  • An analytics dashboard that aggregates live occupancy or ride status across destinations

FAQ from MCP Server for ThemeParks.wiki

What are the runtime requirements?

Node.js version 18 or higher is required.

How do I configure the server?

Set the environment variable THEMEPARKS_API_BASE_URL to https://api.themeparks.wiki/v1 in your MCP client configuration.

What data can I access?

You can access real-time wait times, operating hours, show times, static details about parks and attractions, and schedule/calendar data for entities.

Does the server require authentication or API keys?

The README does not mention any authentication; the default API is publicly accessible via the given base URL.

Can I run this server locally for development?

Yes, clone the repository, run npm install and npm run build, then start with node dist/index.js. Use the MCP Inspector for debugging.

评论

记忆与知识 分类下的更多 MCP 服务器