tl;dv MCP server for AI agents

Live

API KEY

MEETING NOTES

Transcription

tl;dv gives your agent access to your meeting recordings: list and search meetings, read AI-generated meeting notes and full transcripts, and import recordings from a public URL for transcription.

  • Per-user credentials: each call uses the actual user's API key, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
tl;dv
agent · Acme Q3
Run
What were the key points from yesterday's pipeline review?
S
tldv_get_meeting_notes
101ms
Meeting agent
The pipeline review covered 3 topics: the Q4 forecast, 2 stalled enterprise deals, and a pricing pilot. Next steps went to sales and finance.
Sources: tl;dv notes, 1 meeting
tldv
1 meeting
18:29
Message Claude...

Tools your meeting notes agent reaches for on tl;dv, scoped per user.

CALL ANY TOOL
5 tools for meeting notes in tl;dv: list and search meetings, get meeting details, read AI-generated notes and transcripts, and import recordings from a URL.
tldv_get_meeting
Get meeting
Retrieve one tl;dv meeting by id. Returns id, name, happenedAt, url, duration, organizer, invitees, template, extraProperties, plus phoneNumber and metadata when set at import. Use get_meeting for metadata about one meeting. Use list_meetings to find ids, get_transcript for the spoken text, get_meeting_notes for the AI notes.
Parameters
Name
Type
Required
Description
meetingId
string
Required
ID of the meeting, as returned by tldv_list_meetings (the id field).
tldv_get_meeting_notes
Get meeting notes
tldv_get_transcript
Get transcript
tldv_import_meeting
Import meeting
tldv_list_meetings
List meetings
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// tl;dv tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["tldv"], toolNames: [
    "tldv_list_meetings",
    "tldv_get_meeting_notes",
    "tldv_get_transcript"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Summarize the notes from my last customer call" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["tldv"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Summarize the notes from my last customer call" }],
  tools,
});

// Execute the tool call with the user's vaulted tl;dv API key
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["tldv"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Summarize the notes from my last customer call" }],
  tools,
});

// Tool call runs with the user's vaulted tl;dv API key
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["tldv"] }, pageSize: 100,
});

const agent = new Agent({
  name: "meeting_notes_agent",
  model: "gemini-2.5-pro",
  instruction: "tl;dv tools scoped to this user",
  tools,
});

await agent.run("Summarize the notes from my last customer call");
Try these prompts
Copy any prompt into your agent. Each maps directly to a tl;dv tool. Click to copy, paste into your agent, done.
Meetings
Copy the prompt
Copied
List my meetings from last week.
Copy the prompt
Copied
Find meetings with onboarding in the title from this month.
Copy the prompt
Copied
Get the organizer and invitees for this meeting.
Notes and transcripts
Copy the prompt
Copied
Summarize the notes from my last customer call.
Copy the prompt
Copied
Get the full transcript of yesterday's standup.
Copy the prompt
Copied
Which speaker talked about pricing in this meeting's transcript?
Imports
Copy the prompt
Copied
Import this recording URL into tl;dv for transcription.
Copy the prompt
Copied
Import last week's webinar recording from this link.
Copy the prompt
Copied
Import this call recording, then get its notes once it is ready.
SEE HOW AUTH WORKS
Each user connects their own tl;dv API key once, and Scalekit sends it with every call. Keys stay vaulted, every call is scope checked, and every action is logged.
1
Authorize
Your user connects
tl;dv
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
tl;dv
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
tl;dv
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
tl;dv
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other transcription and productivity connectors.
Support and Ops Teams
Meeting prep
Pulls agenda, participant context, and open action items before every meeting.
GTM and RevOps Teams
Sales call prep agent
Reads tomorrow's calls from Google Calendar, mines past Granola notes and Attio history for context, and delivers each rep a prep brief in Slack, scoped to the calls that rep actually owns.
Test other agents
See the same per-user auth pattern across other transcription and productivity connectors.
OPS
Meeting prep agent
Assemble the agenda, HubSpot attendee history, and open action items from Gmail before every meeting on the calendar.
SALES
Sales call prep agent
Read tomorrow's calls from Google Calendar, mine Granola notes and Attio history, and deliver each rep a prep brief in Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared tl;dv API key looks fine in a demo. In production every meeting import looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
tl;dv today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access tl;dv as the user or through a shared key?
As the user. Each user connects their own tl;dv API key once, and Scalekit sends it with every call. Audit logs attribute every meeting read and import to that user, not a shared service account.
Where is the tl;dv API key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new API key. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.
Can I limit what the agent does in tl;dv?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example the 4 read tools without tldv_import_meeting, the only tool that adds data. tl;dv has no delete tools. Scalekit also enforces scope checks before every API call.
What happens when a user revokes tl;dv access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Which tl;dv meetings can the agent read?
Meetings the user's tl;dv API key can access. tldv_list_meetings filters them by search text, date range, participation, or meeting type, and tldv_get_meeting_notes returns the structured notes, markdown, and topics tl;dv generated for each one.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""tldv"": {
""url"": ""https://mcp.scalekit.com/tldv"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.tldv]
url = ""https://mcp.scalekit.com/tldv""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""tldv"": {
""url"": ""https://mcp.scalekit.com/tldv"",
""type"": ""http""
}
}
}