tldv
by tldv
Search Google Meet, Zoom and Teams meeting transcripts and notes from an AI agent. Anthropic lists 5 read-only tools; tl;dv publishes no list for this server, and its one OAuth scope names no verb at all. Read the agent's other connectors, not this one, for outbound risk.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect tldv via MCP
https://mcp.tldv.io/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
tldv Tools & Capabilities (5)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- tl;dv publishes no tool list for this server. Its official MCP documentation names no tools and no endpoint. The five names come from Anthropic's directory, and no vendor enumeration exists to diff them against. That is weaker than a clean result.
- The one OAuth scope makes the scope diff vacuous.
mcp:toolsnames no verb, so it can neither confirm nor contradict the read-only census. It also means a future write tool needs no new scope and would produce no change at the consent screen. - The documented use case pairs this connector with an outbound one. tl;dv's own example prompts send emails, post to Slack and publish to Confluence via other connectors. A verb census of this server alone will not surface that, and blanket auto-approval across such a session is the risk worth declining.
- We could not read tool schemas or safety annotations. The endpoint returned HTTP 401 to an anonymous request, so no parameter-level detail or vendor annotation is published here. Schema detail on this page comes from tl;dv's own API documentation and open source, and describes the API the hosted server sits on rather than the hosted tools themselves.
- Scoping to your own meetings is not enforced. tl;dv's guidance is to widen the scope by changing your prompt, and the published participation filter is an optional boolean. We found no way to constrain the grant itself to meetings you attended.
- Access depends on someone else's billing. A meeting organised by a free tl;dv user is invisible to the API even when it is shared with you and visible in the web app.
get-user-profilehas no documented counterpart. tl;dv's public API publishes eight endpoints and none returns a user profile. We could not establish what this tool returns.- Free-tier retention is three months. tl;dv's privacy policy sets recordings and transcriptions at three months for free users; paying users' data is kept until account deletion, with no time-based expiry published.
- Participant emails outlive the meeting by years. Email addresses of non-subscribers who attend a recorded meeting are retained for five years or until a deletion request.
- Plan requirements are stated inconsistently. The MCP documentation says Pro or higher; the API documentation's access table starts at Pro/Business; the launch blog and repository README for the self-hosted server say Business or Enterprise. Confirm your tier before buying.
- The API is alpha and says so. tl;dv labels it
v1alpha1, warns the production endpoint "may choose to change", and marks the highlights endpoint deprecated. - No published rate limits. tl;dv documents no request ceiling for MCP or its REST API. Its open-source client retries on HTTP 429, so a limit exists in practice without being published.
- The resource descriptor is labelled "MCP Demo Server". Cosmetic, but it is the production descriptor for a partner-tier connector.
Frequently asked questions
Not by itself. All five tools read. But tl;dv's own documentation advertises exactly that outcome, with example prompts asking the assistant to send a follow-up email, publish a report to Confluence and send a Slack message. Those actions run through your other connectors, so the outbound risk lives in the session, not in this server.
In bot mode, yes. tl;dv sends a visible bot carrying a name and avatar into the call, which it argues is notice by default rather than something the recorder must remember. tl;dv also now ships a bot-free desktop recorder with no visible participant, and states that in that mode disclosure sits entirely with you.
It depends on the plan. tl;dv's privacy policy sets recordings and transcriptions at three months for free users and until account deletion for paying users. The same table keeps email addresses of non-customer meeting participants for five years, collected to gather their consent before the meeting.
One, and it names no verb. The server's RFC 9728 descriptor advertised scopes_supported of exactly mcp:tools on 2026-08-23. That grants the tool surface as a unit, so nothing at the OAuth consent screen separates reading a transcript from any future write the server might add.
Anthropic lists five and tl;dv publishes no list for this server at all. Its official MCP documentation is capability prose with no tool names in it. The only tl;dv enumeration that exists describes a different, self-hosted server whose four tool names share just one string with the directory's five.
Yes, if they were shared with you and the organizer pays. tl;dv documents that the connector focuses on meetings you participated in by default, and tells you to widen it by asking for meetings you were not part of. Its API filter for participation is optional rather than enforced.
A paid tl;dv plan and a paid Claude plan. tl;dv's MCP documentation requires a Pro plan or higher on its side, and Claude Pro, Max, Team or Enterprise with Connectors access on yours. Meetings organised by a free tl;dv user stay unreadable regardless of what you pay.
No. No tool among the five carries a write, delete or import verb, and the underlying REST API publishes exactly one non-read operation across eight endpoints — importing a meeting from a URL — which has no counterpart in the tool listing. There is no delete endpoint at all.
Sources
- tl;dv MCP official documentation (retrieved 2026-08-23). This is a Notion-hosted page; see the extraction note below. · retrieved 2026-08-23
- tl;dv developer API documentation, including the inlined OpenAPI paths, the UI-versus-API access table and the webhook triggers (retrieved 2026-08-23) · retrieved 2026-08-23
- tl;dv self-hosted MCP server source, read at
main— ·src/index.ts·src/api/tldv-api.ts·src/api/schemas.ts·README.MD(retrieved 2026-08-23) · retrieved 2026-08-23 - tl;dv launch blog, "tl;dv + MCP: Elevating Meeting Intelligence with AI-Driven Contextualization" (retrieved 2026-08-23), source of the "Import Meetings (Coming Soon)" claim · retrieved 2026-08-23
- tl;dv, "Is Bot-Free Recording Legal?" (updated August 2026) (retrieved 2026-08-23), source of the visible-bot disclosure position and tl;dv's own bot-free recorder · retrieved 2026-08-23
- tl;dv privacy policy, retention table (retrieved 2026-08-23) · retrieved 2026-08-23
- tl;dv security commitment (retrieved 2026-08-23) · retrieved 2026-08-23
- tl;dv product index,
llms.txt(retrieved 2026-08-23).tldv.io/robots.txtcarries noContent-Signaldirective and does not disallow the paths used here. · retrieved 2026-08-23 - Live OAuth posture check: an anonymous initialize returned HTTP 401 with a
www-authenticateBearer challenge naminghttps://mcp.tldv.io/.well-known/oauth-protected-resource; that descriptor and the authorization server metadata athttps://mcp.tldv.io/.well-known/oauth-authorization-serverandhttps://keycloak.tldv.io/realms/mcp.tldv.io/.well-known/openid-configurationwere all read (2026-08-23). A nonsense sibling path under the same prefix returned 404, so the 200 is genuine rather than a catch-all. · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- tl;dv support — <mailto:support@tldv.io> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- tldv
- Tools
- 5
- Domain
- mcp.tldv.io
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.