Does Peek have an MCP server?
Peek maintains an official MCP server.
Consumer trip-planning search over Peek's bookable activities; it does not manage a Peek Pro operator account.
- Access
- Remote server
- Endpoint
- https://mcp.peek.com
- Category
- Other Tools and Integrations
A remote server run by Peek itself — nothing to install. Documented at www.peek.com.
Hosted by the vendor — no install, connect over HTTP with OAuth or a token.
Add it from the terminal, then restart your session:
claude mcp add --transport http peek https://mcp.peek.comAdd --scope user to make it available in every project.
- Open Settings → Connectors
- Click Add custom connector
- Paste
https://mcp.peek.com - Finish the sign-in prompt, then enable it in the chat's tools menu
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for
every project:
{
"mcpServers": {
"peek": {
"url": "https://mcp.peek.com"
}
}
}A green dot in Settings → MCP means it connected.
Add to .vscode/mcp.json:
{
"servers": {
"peek": {
"type": "http",
"url": "https://mcp.peek.com"
}
}
}Then pick the server from the tools menu in Copilot's agent mode.
- Enable Developer mode under Settings → Apps & Connectors → Advanced
- Choose Create and paste
https://mcp.peek.com - Complete sign-in, then enable the connector in a new chat
Does Peek have an official MCP server?
Yes. Peek maintains an official MCP server, hosted at https://mcp.peek.com.
How do I connect Peek to Claude?
Add https://mcp.peek.com as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http peek https://mcp.peek.com" in Claude Code.
Do I need to install anything to use the Peek MCP server?
No. It is a remote server hosted by Peek, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.
How is this verdict verified?
Published to the MCP Registry under Peek's verified namespace com.peek (listing repo peek-travel/mcp-intro in Peek's GitHub org); peek.com/mcp documents the free remote server at mcp.peek.com, which answers MCP initialize without auth as "Experiences MCP". GitHub metadata is refreshed every six hours.
Published to the MCP Registry under Peek's verified namespace com.peek (listing repo peek-travel/mcp-intro in Peek's GitHub org); peek.com/mcp documents the free remote server at mcp.peek.com, which answers MCP initialize without auth as "Experiences MCP".
- github data refreshed 2026-09-29, then every 6 hours
- vendor docs verified on 2026-09-29
Spotted something out of date? Tell us — corrections ship same-day.