Meetings

tl;dv with Claude & ChatGPT—tl;dv MCP server

Meeting recordings, transcripts, and AI notes on the unified contact timeline, identity-resolved with your CRM, email, and support, read-only. Works in Claude, ChatGPT, Cursor, and any MCP-compatible agent.

What it looks like

What does tl;dv data look like in Claude?

Connect tl;dv once. Your agent reads call transcripts and notes on the unified profile—identity-resolved with your CRM, email, and support—through one MCP server.

MCP

tl;dv, exposed as MCP tools.

Claude · pathbound MCP connected
you
What did we commit to on the last call with acme.com?
get_contact_conversations { domain: "acme.com" } 4 sources · 460ms
tldv call 6d ago · 38 min · AI notes
gmail recap email · 5d ago
get_contact_timeline { contact_id: "ctc_01H..." } 7 events · 360ms
tldv action item: “send security docs”
hubspot deal_stage = security review
claude
On the call 6 days ago you committed to sending security docs and a SOC 2 timeline. The recap email went out 5 days ago, but HubSpot still shows the deal in security review—the docs may not have landed.
signal Open action item from the call + stalled stage. Close the loop before it slips.
claude_desktop_config.json
{
  "mcpServers": {
    "pathbound": {
      "url": "https://mcp.pathbound.ai/mcp"
    }
  }
}
tl;dv tools out of the box · read
get_contact_conversations tl;dv transcripts and notes on the unified profile
get_contact_timeline calls alongside CRM, email, and support
get_contact unified profile across tl;dv + your other sources
list_contacts find contacts with recent meetings
aggregate_data meeting and topic breakdowns across accounts
create_contact_note log follow-ups and action items on the contact

…plus 20 more—26 MCP tools total, across contacts, companies, events, and conversations.

Setup

How do I connect tl;dv to Claude?

Paste an API key. Drop a snippet into your MCP client. Ask a question.

  1. 01

    Sign up for Pathbound

    Create an account at pathbound.ai. Free during public alpha.

  2. 02

    Connect tl;dv

    In the dashboard, go to Integrations → tl;dv → Connect. Paste your tl;dv API key. Pathbound syncs recordings, transcripts, and AI notes and matches each meeting to the right contact.

  3. 03

    Add Pathbound to your MCP client

    Drop the snippet below into your Claude Desktop config (or in Claude.ai web: Settings → Connected Apps → Add custom MCP → enter https://mcp.pathbound.ai/mcp). The same URL works for ChatGPT, Cursor, Cline, and any MCP client that supports OAuth.

    claude_desktop_config.json
    {
      "mcpServers": {
        "pathbound": {
          "url": "https://mcp.pathbound.ai/mcp"
        }
      }
    }
  4. 04

    Run a test prompt

    Ask the agent: “Summarise our last call with acme.com.” The agent calls get_contact_conversations via MCP and returns the transcript notes.

Why Pathbound

What was said on the call shouldn’t die in a recording folder.

A direct tl;dv connector shows your agent meetings. Pathbound shows your agent the customer—tl;dv transcripts and AI notes stitched together with your CRM, email, and support—through one unified profile served over the Model Context Protocol.

Calls in context

Transcripts and AI notes land on the same timeline as deal stage and emails. The agent reads what was promised on the call before it drafts the follow-up.

Identity-resolved

Meeting participants resolve to the unified contact by email—so the call joins the same profile as their CRM record, conversations, and web activity.

Read-only by design

Pathbound only reads from tl;dv—recordings, transcripts, and notes. It never writes back, so connecting it can’t change your meeting data.

Built for LLMs

Token-efficient summaries and key moments instead of a 60-minute raw transcript that blows the context window.

FAQ

Common questions.

Is this an official tl;dv MCP server?

Pathbound is an independent platform. We connect to tl;dv via its API using a key you provide, and expose your data through one Model Context Protocol server alongside your other sources. Not affiliated with tl;dv.

Does Pathbound write to tl;dv?

No. The tl;dv integration is read-only—it pulls recordings, transcripts, and AI notes into the unified profile and never writes anything back.

What data does it sync?

Meeting recordings metadata, transcripts, and AI-generated notes, matched onto the unified contact by participant email so the call sits on the same timeline as everything else.

Which MCP clients does this work with?

Claude.ai, Claude Desktop, Claude Code, ChatGPT (with custom connectors), Cursor, Cline, Continue—any client that supports the Model Context Protocol with OAuth.

Is my customer data secure?

Tenant-isolated and OAuth-scoped per user, with encryption at rest via our infrastructure provider’s default configuration. GDPR-aligned; SOC 2 readiness in progress. Pathbound does not sell customer data, and we don’t call AI providers on your behalf—your MCP client does, under your account and the AI provider’s terms.

What about Gmail, HubSpot, Intercom?

Same MCP server, same tools—just connect a different source. See the integrations directory.

Try it on your own data

Within five minutes, your agent is querying real customer context.

Sign up, connect one CRM or drop the events snippet, and point your MCP client at mcp.pathbound.ai/mcp.