How do I install Sixflags?

Sixflags is a local plugin. Install it using npm package: sixflags-mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Sixflags safe to use?

Sixflags scored 7/10 (moderate risk) in MCP Marketplace's automated security scan. It has 1 high or critical finding to review. It's listed, but review the security report on this page before installing.

What credentials does Sixflags need?

Sixflags requires the following credentials or environment variables: SIXFLAGS_HOME_PARK. You can find setup instructions on the server detail page.

What AI apps work with Sixflags?

Sixflags uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Sixflags MCP Server

by Chris Hall

Developer ToolsModerate7.0Local

Free

Six Flags MCP for Claude — live wait times, park hours, shows, and day planning

About

Six Flags MCP for Claude — live wait times, park hours, shows, and day planning

Security Report

7.0

Moderate7.0Moderate Risk

A well-structured MCP server for querying Six Flags park data with clean code practices and proper input validation. The server consumes publicly available APIs requiring no authentication and implements appropriate access controls. Minor code quality observations exist around error handling breadth, but permissions align well with the server's stated purpose and no security vulnerabilities are present. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

7 files analyzed · 6 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

process_spawn

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Default park for tools that don't name one. A park name, themeparks.wiki slug, or park id. Defaults to Carowinds.Optional

Environment variable: SIXFLAGS_HOME_PARK

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-chrischall-sixflags-mcp": {
      "env": {
        "SIXFLAGS_HOME_PARK": "your-sixflags-home-park-here"
      },
      "args": [
        "-y",
        "sixflags-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

sixflags-mcp

MCP server for Six Flags theme parks — live ride wait times, park hours, show schedules, and day planning. Your home park (default Carowinds) is the default for every tool, so "what are the wait times?" just works. Covers the whole combined Six Flags / Cedar Fair chain: Cedar Point, Kings Island, Canada's Wonderland, Magic Mountain, the Hurricane Harbor water parks, and more.

Data comes from the public themeparks.wiki API — no account, no API key, no login.

Built and maintained by AI. This codebase is developed and maintained by Claude (Claude Code). Use at your own discretion.

Tools

Tool	What it does
`sixflags_get_wait_times`	Every ride's current standby + single-rider wait and status, sorted longest-first, with a crowd summary.
`sixflags_suggest_next`	Ranks currently-open rides by shortest wait — the "what should we ride next?" planner. Supports `exclude`, `maxWaitMinutes`, `limit`.
`sixflags_get_park_schedule`	Operating hours from today forward.
`sixflags_get_shows`	Today's live show schedule (parades, stunt shows, character meets) with showtimes.
`sixflags_list_attractions`	The full directory of a park's rides / shows / restaurants, with map coordinates.
`sixflags_list_parks`	Every Six Flags park and its id; `search` to filter.
`sixflags_healthcheck`	Confirm the upstream data source is reachable.

Every data tool takes an optional park argument (name, slug, unique substring, or id). Omit it for your home park.

Install

Via npx (published to npm):

{
  "mcpServers": {
    "sixflags": {
      "command": "npx",
      "args": ["-y", "sixflags-mcp"],
      "env": { "SIXFLAGS_HOME_PARK": "Carowinds" }
    }
  }
}

Or as a Claude Code plugin from the chrischall marketplace, or install the .mcpb bundle from a release.

Configuration

All optional — the upstream is keyless.

Env var	Default	Purpose
`SIXFLAGS_HOME_PARK`	`Carowinds`	Default park for tools that don't name one. A park name, themeparks.wiki slug, or park id.
`SIXFLAGS_REQUEST_TIMEOUT_MS`	`15000`	Per-request timeout.
`SIXFLAGS_USER_AGENT`	`sixflags-mcp (+…)`	User-Agent sent to themeparks.wiki.

Development

npm install
npm run build          # tsc → dist/, then esbuild bundle → dist/bundle.js
npm test               # vitest run
npm run test:coverage  # 100% coverage gate (CI)
npm run dev            # node --env-file=.env dist/index.js (requires a build)

Data source & accuracy

Wait times, show times, and hours are provided by themeparks.wiki, which aggregates the parks' own apps. They populate only during operating hours — off-hours every ride reads CLOSED. Treat waits as best-effort estimates, not guarantees.