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.
{
"mcpServers": {
"pathbound": {
"url": "https://mcp.pathbound.ai/mcp"
}
}
} …plus 20 more—26 MCP tools total, across contacts, companies, events, and conversations.
Paste an API key. Drop a snippet into your MCP client. Ask a question.
Create an account at pathbound.ai. Free during public alpha.
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.
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.
{
"mcpServers": {
"pathbound": {
"url": "https://mcp.pathbound.ai/mcp"
}
}
} Ask the agent: “Summarise our last call with acme.com.” The agent calls get_contact_conversations via MCP and returns the transcript notes.
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.
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.
Meeting participants resolve to the unified contact by email—so the call joins the same profile as their CRM record, conversations, and web activity.
Pathbound only reads from tl;dv—recordings, transcripts, and notes. It never writes back, so connecting it can’t change your meeting data.
Token-efficient summaries and key moments instead of a 60-minute raw transcript that blows the context window.
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.
No. The tl;dv integration is read-only—it pulls recordings, transcripts, and AI notes into the unified profile and never writes anything back.
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.
Claude.ai, Claude Desktop, Claude Code, ChatGPT (with custom connectors), Cursor, Cline, Continue—any client that supports the Model Context Protocol with OAuth.
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.
Same MCP server, same tools—just connect a different source. See the integrations directory.
Sign up, connect one CRM or drop the events snippet, and point your MCP client at
mcp.pathbound.ai/mcp.