tpapi

The ThemeParks.wiki API MCP Server exposes data from ThemeParks.wiki as MCP tools. It offers utilities to fetch park lists, individual park entities, operating hours for parks, attraction wait times, and show times. You can query a park’s children to get attractions and shows, retrieve a park’s schedule for a specific date, or look up entities by name or ID. This server is intended to be run behind an MCP Client (such as Claude Desktop) which will request tool results and present them to end users. The available tools map to the methods described in the README, such as getAllParks, getParksByName, getEntity, getEntityChildren, getEntityScheduleForDate, and getEntityLive.

To use the tools, start the MCP server (via the provided Java command) and point your MCP Client configuration to the server’s JAR-based execution. The client will invoke the tools by name and pass the required inputs (e.g., entityId or date). The client handles the orchestration, while this server returns structured data about parks, entities, schedules, and live wait/show times.

Prerequisites:

• Java 21 (or higher) installed on the host machine
• Git and a Java build tool (Gradle wrapper is used in this project)

Step-by-step installation:

1. Clone the repository: git clone <repository-url> cd <repository-directory>

2. Ensure Java is installed and accessible: java -version If you need multiple JDK versions, consider using SDKMAN! to install and manage them.

3. Build the MCP server into an executable JAR: ./gradlew build This will produce a JAR at build/libs/tpapi-mcp-server-0.0.1-SNAPSHOT.jar (as described in the README).

4. Run the server locally (for testing): java -jar build/libs/tpapi-mcp-server-0.0.1-SNAPSHOT.jar

5. Optional: Build a Docker image (if you want to containerize): ./gradlew bootBuildImage --imageName=habuma/tpapi-mcp-server

Note: The MCP Client (e.g., Claude Desktop) will orchestrate running the JAR and invoking the tools. Do not attempt to run the JAR directly via the MCP Client; the client will handle execution and wiring of inputs.

Notes and tips:

• The server requires Java 21 or newer. If you run into Java version issues, install the recommended JDK and ensure JAVA_HOME is set.
• The actual path to the JAR in production should point to the built artifact (tpapi-mcp-server-0.0.1-SNAPSHOT.jar) produced by the Gradle build.
• If you enable Docker usage, you can build the image with the provided Gradle command; however, Claude Desktop will typically manage running the server, so you may not need to run the image manually.
• If you encounter input validation errors from the MCP Client, ensure you provide the correct field names and types (e.g., entityId as a string, date in yyyy-MM-dd format).
• You can adjust JVM options by setting JAVA_TOOL_OPTIONS or by adding specific options in the command line if the server needs more heap space or other tuning.