Claude + Tripdocks

Tripdocks works with Claude through the Model Context Protocol (MCP). Add Tripdocks as a custom connector in Claude, approve the consent screen, and Claude can read your leads, quotes, reservations and tasks — and, if you allow it, act on them. It acts as you: it sees only what your role can see and does only what your role allows.

How it works

1. In Claude, open Settings → Connectors → Add custom connector.
2. Name it Tripdocks and paste the connector URL: https://app.tripdocks.com/mcp.
3. Sign in to Tripdocks on the consent screen, review the requested access, and allow it.
4. Claude Desktop users can add the same URL to claude_desktop_config.json through mcp-remote.

What you need

• A Claude plan that supports custom connectors (remote MCP servers), or Claude Desktop.
• The Connect AI permission on your Tripdocks role.

What your team gets

• Read access to leads, contacts, pipeline, quotes and itineraries, reservations, tasks, and invoice and payment status.
• Optional write access: create or update leads, add or complete tasks, send quotes, log payments.
• OAuth 2.1 with PKCE — Claude never sees your password.
• Every tool call logged, and one-click revocation in Settings → Intelligence.

Step-by-step instructions are in the AI assistants guide. Leads from every connected channel land in the same queue — see lead management.

Related integrations

• ChatGPT — Bring your travel CRM into ChatGPT, with the same permissions you have in Tripdocks.
• WhatsApp Cloud API — Use Meta's WhatsApp Cloud API directly, and handle every traveller chat inside your travel CRM.
• Facebook & Instagram lead ads — Stop downloading CSVs from Meta. Lead ad submissions land in your travel CRM in real time.
• All integrations