Peek.com MCP Server
Connect Peek.com to your AI agents with the Peek.com MCP server.
Updated
What is Peek.com MCP?
The Peek.com MCP server is a Model Context Protocol server that connects Peek.com to AI agents and assistants as a set of tools. With it connected, an agent can work with Peek.com (activities and tours booking) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses no authentication, so you point your client at the server URL, authorize once, and the Peek.com tools become available to the model.
Connect the Peek.com MCP server
Connect Peek.com MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Peek.com MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (no authentication) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Peek.com tool to confirm the connection is live.
Connect Peek.com MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Peek.com
Provide the Peek.com MCP server URL or command and complete authentication.
- 3
Test
Reference Peek.com from chat to confirm Cursor can reach the tools.
Using Peek.com MCP with Gamut
On Gamut, the Peek.com MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Peek.com and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What is the Peek.com MCP server?
It is a Model Context Protocol server that exposes Peek.com to AI agents as tools so they can work with it (activities and tours booking).
How do I connect the Peek.com MCP server?
Point your MCP client (Claude, Cursor, or Gamut) at the Peek.com MCP server URL and complete authentication (no authentication). See the official documentation for the exact URL and scopes.
Can I use Peek.com MCP with Gamut?
Yes — Gamut supports the Peek.com MCP server, so your agents can use it as a tool in automated, triggered workflows.