dropbox-transcripts-mcp
Related Servers
Alternatives to dropbox-transcripts-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA local MCP server that indexes and searches your Claude Code conversation history with both keyword and semantic search, fully private and running locally.MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that indexes local Claude Code transcripts and provides keyword, phrase, semantic, and date-range search, plus full context/session recall.-
- AlicenseAqualityDmaintenanceMCP server that indexes Claude.ai chats and local Claude Code sessions, enabling semantic and keyword search across all your conversations with Claude.628 PyPI5MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that indexes Markdown files into a local SQLite vector store and provides semantic search tools for Claude Code.4MIT
- AlicenseAqualityCmaintenanceAn MCP server that makes Claude Code conversation history searchable and proactively useful by indexing past sessions with hybrid BM25+TF-IDF search, extracting decisions and solutions, and auto-injecting relevant project context at session start.97 npm66MIT
- FlicenseAqualityDmaintenanceA semantic search system for Claude Code transcript history, exposed as an MCP server so Claude Code can query its own past sessions.2-
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing episodes, retrieving a specific transcript, full-text search, and triggering a sync. No overlap or ambiguity.
Most tools follow a verb_noun_tool pattern (get_episode_tool, list_episodes_tool, search_transcripts_tool, sync_tool). However, there is inconsistency in pluralization: 'get_episode' (singular) vs. 'list_episodes' and 'search_transcripts' (plural).
Four tools is well-scoped for a server focused on podcast transcripts. Each tool serves a necessary function without redundancy or deficiency.
The tool set covers all core operations for a transcript reader: listing available episodes, retrieving a specific transcript, searching across content, and syncing the index. No obvious gaps for the intended use case.