Dropbox MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DROPBOX_ACCESS_TOKEN | Yes | Your Dropbox access token for authentication |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_filesB | Search for files in Dropbox by name or content. Args: query: Search query (searches file names and content) file_types: File types to search ("all", "pdf", "docx", "txt", or comma-separated list) max_results: Maximum number of results to return |
| list_filesB | List files and folders in a Dropbox directory. Args: folder_path: Path to the folder (empty string for root) max_files: Maximum number of items to return |
| read_fileA | Read and return the full content of a file. Args: file_path: Full path to the file in Dropbox max_length: Maximum characters to return (0 for no limit) |
| get_file_infoC | Get detailed information about a specific file. Args: file_path: Full path to the file in Dropbox |
| search_file_contentC | Search for text within specific files. Args: file_paths: List of file paths to search in query: Text to search for context_chars: Number of characters of context around matches |
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 5 tools
Most tools have distinct purposes, but 'search_file_content' and 'search_files' could cause confusion as both involve searching. 'search_file_content' searches within specific files for text, while 'search_files' searches across files by name or content, but the naming similarity might lead to misselection without careful reading of descriptions.
All tool names follow a consistent verb_noun pattern (e.g., get_file_info, list_files, read_file, search_file_content, search_files). The naming is uniform and predictable, making it easy for agents to understand the action and target resource.
With 5 tools, the count is reasonable for a Dropbox file management server, covering core operations like listing, reading, and searching. However, it feels slightly thin as it lacks tools for creating, updating, or deleting files, which are common in file management domains.
The tool set covers basic read and search operations well, but there are notable gaps in CRUD coverage. For a Dropbox server, missing tools for uploading, updating, moving, or deleting files could lead to agent failures when trying to perform full file lifecycle management, limiting its utility for broader workflows.