tl;dv MCP server
tl;dv in any MCP client, through Memtro: tl;dv does not publish this server. Memtro's tl;dv connector reads tl;dv through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
tl;dv meeting recorder: meetings the connected user organised (Zoom, Meet, Teams) with time, organiser and invitees, their transcripts by speaker, tl;dv's AI notes by topic, and folders. Can import a recording from a public URL as a new meeting to be transcribed.
Reads
tldv_list_meetingsMeetings recorded by tl;dv that the connected user organised: name, when, length, organiser and invitees, link.tldv_get_meetingOne tl;dv meeting by id: name, when, length, organiser, invitees and link.tldv_get_transcriptThe transcript of a tl;dv meeting, speaker by speaker with timestamps.tldv_get_notesTl;dv's AI notes for a meeting: the topics discussed with a summary of each, and the notes as markdown.tldv_list_foldersTl;dv folders the connected user can see: id, name and how many meetings each holds.
Acts, when you ask
These change something in tl;dv. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
tldv_import_meetingImport a recording (audio or video at a public https URL: .mp3 .mp4 .wav .m4a .mkv .mov .avi .wma .flac) into tl;dv as a new meeting owned by the…
Connect it
First connect tl;dv on Dashboard → Connections, then add Memtro to your client once. The tl;dv tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared tl;dv connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What was decided in the Acme call on Thursday?
- › What exactly did Priya say about pricing in yesterday's meeting?
- › Which external meetings did I have last week?
- › Summarise the topics from the Northwind kickoff
- › Import the recording of the Globex workshop from this link so it gets a transcript
Questions
- Is this an official tl;dv MCP server?
- No. It is Memtro's MCP server with Memtro's tl;dv connector behind it: the connector reads tl;dv through its API with the credentials you connect on Dashboard → Connections, and tl;dv publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in tl;dv?
- Only when you ask, and only what it has been granted: import a recording from a public URL as a new tl;dv meeting, to be transcribed and noted (uses the daily import quota). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.