What are the runtime requirements?
Node.js version 18 or higher is required.
@MasonMao-dev
Basic information
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.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"mcp-server-theme-parks": {
"command": "npx",
"args": [
"-y",
"mcp-server-theme-parks"
],
"env": {
"THEMEPARKS_API_BASE_URL": "https://api.themeparks.wiki/v1"
}
}
}
}Retrieves a list of all available top-level theme park destinations (e.g., Walt Disney World Resort, Universal Orlando Resort).
Fetches detailed static information for a specific entity (like a park, attraction, or restaurant) using its unique ID.
Retrieves all direct child entities for a given parent entity ID (e.g., all parks within a destination, or all attractions within a park).
Fetches live data for a specific entity and its children. This can include attraction wait times, park operating hours, and show times.
Retrieves the operating schedule or calendar data for a specific entity. Can specify a year and month, or get general schedule data.
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.
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.
help prompt summarizing all available toolsNode.js version 18 or higher is required.
Set the environment variable `THEMEPARKS_API_BASE_URL` to `https://api.themeparks.wiki/v1` in your MCP client configuration.
You can access real-time wait times, operating hours, show times, static details about parks and attractions, and schedule/calendar data for entities.
The README does not mention any authentication; the default API is publicly accessible via the given base URL.
Yes, clone the repository, run `npm install` and `npm run build`, then start with `node dist/index.js`. Use the MCP Inspector for debugging.

Shared memory for AI coding agents. Claude Code, Cursor and Codex read your project's decisions, lessons and tasks before they act.

Mess in, magic out: pour in your D&D and TTRPG notes and LoreKeeper keeps them as a private store for your world. Ask Claude or ChatGPT about it, or build a sourcebook.

Serve your docs to AI agents over SSH and MCP. Agents use ls, cat, grep, find, and pipes against a virtual filesystem backed by your documentation. Identity-scoped access, governed writing with human approval, and portab
Local MCP server and CLI that keeps a Git-versioned, model-written index of a codebase and its database schema, so coding agents start each task with the whole system in view.
Person-owned, portable AI memory served over MCP. Your knowledge, preferences, and decisions — captured in one assistant, available in all of them.
Comments