tamlil-mcp
Related Servers
Alternatives to tamlil-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceProvides read-only access to what you have dictated and what was said in your recorded meetings, so coding agents like Codex, Claude Code, Pi or LM Studio can search your local transcripts and notes.MIT
- AlicenseNot gradedqualityFmaintenanceProvides read-only access to Google Drive meeting transcripts and Google Calendar events, enabling AI assistants to search, analyze, and retrieve meeting insights.12,723 npm2MIT

Roomtone MCPofficial
AlicenseAqualityCmaintenanceEnables AI agents and MCP clients to browse Roomtone meeting notes, add YouTube or pasted-text sources, generate summaries, ask questions answered from transcripts, and retrieve raw transcript text. Recording itself stays in the Roomtone app, so the server only reads and adds to existing meetings.711 npmMIT- AlicenseAqualityCmaintenanceExposes meeting transcripts to any MCP-capable AI client so it can list meetings, page through a single transcript, and search across all of them for a topic with exact timestamps. Speaker labels, emails, phone numbers, and paths are pseudonymized or redacted before anything crosses the protocol, and transcripts are read-only.3MIT
- AlicenseAqualityDmaintenanceRead-only access to your Gilbert meetings, transcripts and summaries over MCP — list, search, and fetch transcripts and summaries.569 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents to browse, search, and retrieve Meetily meeting transcripts and summaries on demand through read-only tools.1MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: list_meetings filters and lists, get_meeting fetches metadata for one meeting, get_transcript retrieves transcript content, and search_transcripts finds phrases across transcripts. No two tools overlap in purpose.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: list_meetings, get_meeting, get_transcript, search_transcripts. The naming is uniformly readable and predictable.
With 4 tools, the server is well-scoped for a meeting/transcript archive. Each tool covers a core operation, and the count is neither too sparse nor excessive.
The server provides a complete read-only lifecycle: list meetings, get metadata, get transcript, and search content. There are no obvious dead ends for the stated purpose of retrieving meeting recordings and transcripts.