Connect Claude to TripWorks and you can ask about your guests, activities, locations, and phone calls in plain English, and have Claude make changes for you after showing a preview. This works in Claude.ai and Claude Desktop. The connection uses MCP, an open standard for linking AI assistants to the tools you already use. For the full picture of what MCP is and how it compares with the REST API, Zapier, and webhooks, see Connect TripWorks to your AI assistant (MCP).

What you need

• MCP turned on for your account. Someone with the Setup integrations catalog permission does this once, in step 1 below.
• Your own TripWorks login on a live account. You approve the connection by signing in as yourself.
• A Claude account on a plan that supports custom connectors.
• The TripWorks server URL: https://mcp.tripworks.com/mcp. It's the same for every account.

Connect Claude to TripWorks

1. In TripWorks, go to Setup Integrations, open the MCP card, switch on Enable MCP, and select Save. (Skip this if MCP is already on.)
2. Select Copy URL next to the MCP Server URL.
3. In Claude.ai or Claude Desktop, go to Settings Connectors.
4. Select Add custom connector and paste the URL.
5. Claude opens a TripWorks page in your browser. Sign in if asked, then choose the account to connect.
6. Choose Read access, Write access, or both, then select Approve.
7. Start a new chat in Claude and ask, "List my experiences." If Claude answers with your real activities, you're connected.

Connect Claude Desktop with a local bridge

Claude Desktop can also run a small local bridge instead of using the cloud connector. Add this to your claude_desktop_config.json file, then restart Claude Desktop:

{
  "mcpServers": {
    "tripworks": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.tripworks.com/mcp"]
    }
  }
}

You'll still approve the connection with your TripWorks login the first time. This route needs Node.js installed on your computer, so most people should use the connector steps above.

What Claude can do once it's connected

With Read access, Claude can look up your experiences, locations, customers, booking restrictions, promo codes, trip sources, team members, phone calls, and audit log, and search across trips, bookings, customers, gift cards, payments, resellers, and voucher codes. With Write access, it can also create and edit experiences, locations, and booking restrictions, and edit customers. Every change is shown as a preview first. See everything your assistant can do.

Example requests

Try these in a new chat once you're connected:

• Find guests named Rivera. Claude searches trips, bookings, and customers and lists the matches with their contact details.
• Find customers with a gmail address and count them. Claude filters your customer list by email and gives you the total.
• Find the phone calls from last week. Claude lists recent calls, including AI callbot calls, with what TripWorks recorded.
• Find who changed our zoo's family-pass experience yesterday. Claude reads your audit log and shows what changed, when, and which team member made the change.
• Do add a location called Riverside Kayak Launch. Claude shows a preview of the new location and creates it only after you say yes.

Security and permissions

Claude runs as you. It can see and do only what your permission group already lets you see and do, and never more. On the approval screen you choose Read access, Write access, or both, which narrows what that one connection can do. Turn Enable MCP off under Setup Integrations MCP and every connected assistant stops working right away. Learn more in how security and permissions work and the User permissions reference.

Frequently asked questions