Voyager Commerce
Prototype AI-driven ticket discovery and purchase flows for attractions using a hosted Voyager commerce MCP remote.
Overview
Voyager Commerce is an MCP server for the Build phase that lets AI agents interact with attraction ticket commerce via a streamable-http Voyager storefront remote.
What is this MCP server?
- MCP commerce surface for theme parks, zoos, museums, and aquariums
- Streamable-http remote aimed at Gateway Ticketing Voyager storefronts
- Lets any MCP-capable agent participate in ticket-oriented workflows
- Example remote URL includes storefrontId query parameter
- Version 1.0.0 from blathrop07/voyager-commerce on GitHub
- Server version 1.0.0
- Transport: streamable-http remote
- Targets theme parks, zoos, museums, and aquariums
What problem does it solve?
You want an agent to help visitors find and buy venue tickets but building commerce API glue for Gateway Ticketing from scratch is slow and error-prone.
Who is it for?
Solo builders shipping AI concierge or booking experiments for parks, zoos, museums, or aquariums on Voyager commerce.
Skip if: Generic SaaS checkout projects, digital-only products, or teams without a Voyager storefront and approved remote endpoint.
What do I get? / Deliverables
You register the Voyager commerce MCP remote so your agent can drive ticket-oriented flows against a configured storefront without custom REST wiring for every tool call.
- Agent-accessible ticket commerce tools against a Voyager storefront
- Integration prototype for AI-led attraction booking flows
Recommended MCP Servers
Journey fit
Build is where you integrate third-party commerce APIs into your agent or app; ticket sales for venues are a concrete integration slice, not a marketing-only task. Integrations is the shelf because the server exposes storefront commerce capabilities over MCP rather than generic PM or docs work.
How it compares
Venue-specific commerce MCP integration, not a general ecommerce skill or payment processor plugin.
Common Questions / FAQ
Who is Voyager Commerce for?
Developers and indie operators building AI agents that need ticket catalog and commerce actions for Gateway Ticketing Voyager storefronts at attractions.
When should I use Voyager Commerce?
During Build when you integrate agent-driven ticket discovery or purchase flows for a specific storefrontId on a Voyager-hosted environment.
How do I add Voyager Commerce to my agent?
Add a streamable-http MCP remote using your venue’s Voyager MCP URL (including storefrontId), following Gateway Ticketing hosting docs, then test tool calls from Claude Code or Cursor.