Log inSubmit server
Sixflags MCP logo

Sixflags MCP

Query live Six Flags waits, schedules, shows, attractions, parks, and ride suggestions through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Sixflags MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "sixflags-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "sixflags-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 7 tools correctly (1d ago).

Overview

The sixflags-mcp MCP server retrieves live Six Flags and Cedar Fair park data through the public themeparks.wiki API. It provides ride wait times, next-ride recommendations, operating hours, show schedules, attraction directories, park lookup, and an upstream health check. Set a home park for default queries, or pass a park name, slug, substring, or ID to each data tool. Reach for it when an agent needs current theme-park planning data without an account or API key.

Use cases

  • Check current standby and single-rider waits at a selected park
  • Choose the next open ride under a maximum wait threshold
  • Plan a visit around park hours and today's shows
  • Find attractions and restaurants with map coordinates
  • Verify that the upstream theme-park data source is reachable

Key features

  • Live ride wait times and operating status
  • Shortest-wait ride recommendations
  • Park hours and daily show schedules
  • Park and attraction directories with coordinates
  • Configurable default park and request timeout
  • Upstream API health check

Tools7

What Sixflags MCP lets your agent do. Expand a tool for its parameters.

Verified live~935 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 40d

What it can do

From the 7 tools this server returned when we ran it; 7 declare their own safety hints.

Makes network requests · 7Read-only tools · 7
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age85 days
Maintainers1

Observed 2026-10-21 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · sixflags-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads2.6kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed7Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Sixflags MCP works

What sixflags-mcp does

The sixflags-mcp MCP server exposes theme-park information as tools for an MCP client. It covers the combined Six Flags and Cedar Fair chain, including parks such as Cedar Point, Kings Island, Canada's Wonderland, Magic Mountain, and Hurricane Harbor locations. The default home park is Carowinds, but tools can target another park by name, slug, unique substring, or ID.

Ride data includes current standby and single-rider waits, operating status, and a crowd summary. A separate planner ranks open rides by wait time. Other tools provide upcoming operating hours, the day's shows and showtimes, attraction listings with map coordinates, the complete park directory, and a connectivity check for the upstream source.

How it works

The server reads data from the public themeparks.wiki API. No account, API key, or login is needed. Wait times, showtimes, and operating hours are sourced from data aggregated from the parks' own applications.

Every data tool accepts an optional park selector. If the selector is omitted, the configured home park is used. sixflags_suggest_next can exclude attractions, apply a maximum wait threshold, and limit the number of recommendations returned. Its results focus on rides that are currently open and sorted by shorter waits.

Data is operational rather than historical. The upstream source generally populates waits during park operating hours; outside those hours, rides may appear as CLOSED. Returned wait values should therefore be treated as estimates rather than guarantees.

Setup and configuration

The sixflags-mcp MCP server can be launched from npm with npx and added as a standard stdio MCP server. A typical configuration runs npx -y sixflags-mcp and optionally sets SIXFLAGS_HOME_PARK to choose the default park. It is also available as a Claude Code plugin through the chrischall marketplace, or as an .mcpb bundle from a release.

All configuration variables are optional. SIXFLAGS_HOME_PARK defaults to Carowinds and accepts a park name, themeparks.wiki slug, or park ID. SIXFLAGS_REQUEST_TIMEOUT_MS controls the per-request timeout and defaults to 15000. SIXFLAGS_USER_AGENT sets the User-Agent sent to themeparks.wiki and has a repository-based default value.

Tools and capabilities

  • sixflags_get_wait_times: Lists ride standby and single-rider waits with status, longest waits first, plus a crowd summary.
  • sixflags_suggest_next: Recommends currently open rides using wait time, exclusions, a maximum wait, and a result limit.
  • sixflags_get_park_schedule: Returns operating hours from the current day forward.
  • sixflags_get_shows: Returns today's shows, including parades, stunt shows, character meets, and showtimes.
  • sixflags_list_attractions: Lists rides, shows, and restaurants with map coordinates.
  • sixflags_list_parks: Lists available parks and supports search filtering.
  • sixflags_healthcheck: Checks whether the upstream data source can be reached.

Limitations and notes

Live availability depends on themeparks.wiki and the data supplied by participating park applications. The server does not provide a separate guarantee that a ride is operating or that a displayed wait is exact. Off-hours responses can report rides as closed, and show or wait information may be absent when the upstream source has not populated it.

The package is described as built and maintained by AI in the project material; users should evaluate the code and data behavior for their own deployment.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Sixflags MCP

sixflags-mcp is an MCP server that connects AI clients to Six Flags and Cedar Fair park data through the public themeparks.wiki API. Its main tools return live ride waits, suggest the next ride, provide park schedules and shows, list attractions and parks, and check upstream availability without requiring an account or API key.

Install it with `npx` by configuring the server command as `npx` and the argument `-y sixflags-mcp`. You can also install the Claude Code plugin from the `chrischall` marketplace or use an `.mcpb` release bundle.

Set `SIXFLAGS_HOME_PARK` to a park name, themeparks.wiki slug, or park ID. If no park is passed to a tool, that configured value is used; the default when unset is Carowinds.

Yes, sixflags-mcp can be configured in Cursor as a standard stdio MCP server. Use the npm launch command with `npx -y sixflags-mcp`; no API key or account is required.

No, wait times are best-effort estimates from themeparks.wiki and data aggregated from park applications. Values may be unavailable outside operating hours, when rides can appear as `CLOSED`, and actual waits can differ.

Related MCP servers

All in Travel & Transportation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSixflags MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/sixflags-mcp?style=directory)](https://allmcps.com/mcp/sixflags-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/sixflags-mcp"><img src="https://allmcps.com/api/badge/sixflags-mcp?style=directory" alt="Sixflags MCP on AllMCPs" /></a>