dropbox-transcripts-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_PATH | No | Local SQLite database path | ~/.dropbox-transcripts-mcp/transcripts.db |
| DROPBOX_APP_KEY | Yes | Dropbox app key | |
| DROPBOX_APP_SECRET | Yes | Dropbox app secret | |
| DROPBOX_FOLDER_PATH | No | Path to transcripts folder in Dropbox | /Podcasts/Lenny |
| SYNC_INTERVAL_HOURS | No | How often to poll Dropbox for changes | 6 |
| DROPBOX_REFRESH_TOKEN | Yes | OAuth refresh token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_episodes_toolA | List all available podcast transcript episodes. |
| get_episode_toolA | Get the full transcript for an episode by guest name. Supports partial matches: 'Fishman' will find 'Adam Fishman'. |
| search_transcripts_toolA | Full-text search across all transcript content. Returns matching episodes with highlighted snippets. Supports quoted phrases, AND/OR operators, and prefix wildcards (e.g. 'retain*'). |
| sync_toolA | Manually trigger a sync from Dropbox to update the local transcript index. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.