Get the FREE Ultimate OpenClaw Setup Guide →

mcp -dash

Dropbox Dash MCP Server

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio dropbox-mcp-server-dash uv --directory /path/to/mcp-server-dash/ run src/mcp_server_dash.py \
  --env APP_KEY="your_dropbox_app_key"

How to use

This MCP server exposes Dropbox Dash search capabilities and file metadata via STDIO using the Python MCP server library (fastmcp). After authenticating with Dropbox, you can run searches across your company's content, retrieve detailed metadata for results, and fetch content snippets when needed. The included tools support a complete OAuth flow (dash_get_auth_url to obtain the authorization URL, followed by dash_authenticate to store the token) and then allow you to perform dash_company_search queries and dash_get_file_details lookups by UUID. Tokens are stored securely in the system keyring for subsequent requests.

How to install

Prerequisites:

  • Python 3.10 or higher
  • Dropbox Dash API credentials (App key)
  • Network access to Dropbox APIs
  1. Clone the repository and navigate to it:
git clone https://github.com/dropbox/mcp-server-dash
cd mcp-server-dash
  1. Set up the virtual environment management tool (uv) per platform:
  • macOS (Homebrew):
brew install uv
  • macOS/Linux:
curl -LsSf https://astral.sh/uv/install.sh | sh
  • Windows (PowerShell):
irm https://astral.sh/uv/install.ps1 | iex
  1. Install dependencies via uv:
uv sync
  1. Provide credentials (APP_KEY) either as an environment variable or in a .env file:
export APP_KEY=your_dropbox_app_key
# or use a .env file
cp .env.example .env
  1. Run the MCP server in STDIO mode:
uv run src/mcp_server_dash.py
  1. Authenticate when prompted:
  • Run dash_get_auth_url to obtain the authorization URL and visit it in a browser.
  • Use dash_authenticate(auth_code) with the one-time code to store the token.
  1. To clear a stored token (if needed):
uv run src/mcp_server_dash.py --clear-token

Note: In your MCP client configuration, reference the server using the provided command and ensure APP_KEY is properly set.

Additional notes

Tips and common issues:

  • Token storage: Tokens are kept in your system keyring (e.g., macOS Keychain, Windows Credential Manager, or Linux Secret Service). If you migrate hosts, ensure the keyring is accessible, or re-authenticate.
  • Ensure APP_KEY is kept secure; use environment variables or a .env file with restricted permissions rather than hard-coding credentials.
  • The search tool supports filters like file_type and connector, and timestamps in ISO 8601 format for start_time and end_time. If you encounter authentication errors, re-run dash_get_auth_url and dash_authenticate.
  • When using debugging or development flows, you can inspect traffic with the MCP Inspector: npx @modelcontextprotocol/inspector uv run src/mcp_server_dash.py
  • If you move the installation directory, update the --directory path in the MCP configuration accordingly.

Related MCP Servers

Sponsor this space

Reach thousands of developers