Dropbox MCP Server Cursor IDE Setup 2026: Dash Remote Server & OAuth Config
Connect Dropbox Dash's official hosted MCP server to Cursor IDE. The mcp.dropbox.com/dash endpoint, OAuth setup, manual app registration for non-Cursor clients, and the Dash subscription requirement most tutorials skip.
How do you connect Dropbox to Cursor IDE? Add a Dropbox Dash MCP entry to mcp.json pointing at the hosted endpoint https://mcp.dropbox.com/dash, click connect in Cursor's Tools and MCP settings, and authorize through Dropbox's OAuth flow in your browser. There's no package to install and no local process to run — Dropbox operates the server itself, the same way Box and GitLab host theirs.
The detail that trips people up is the name: this isn't "Dropbox MCP," it's Dropbox Dash MCP — Dash is Dropbox's separate AI search and organization product, and the MCP server is Dash's integration point, not a generic file-storage connector bolted onto your regular Dropbox account. If your team doesn't have Dash, the setup below still mostly works, but what Cursor can actually search and return is scoped to whatever Dash has indexed, not your entire Dropbox.
What the Dropbox Dash MCP Server Can Do
Once connected, Cursor can call tools that:
This is narrower than a general-purpose Dropbox file-management API. There's no tool here for uploading, moving, or reorganizing files from Cursor — Dash MCP is read-and-search oriented, built around "find and ground answers in my content," not "manage my Dropbox from chat." If you need write operations against Dropbox itself (create folders, move files, share links), that's a different, non-Dash integration path that Dropbox's Dash MCP docs don't cover.
Prerequisites
For MCP clients that don't support Dynamic Client Registration — Dropbox's docs specifically carve out an exception list that does not include Cursor, so most Cursor users can skip this — there's a manual path through the Dropbox App Console requiring account_info.read, dash/content.read, and dash/content.write permissions, plus an access token, app key, and app secret. That manual path is for older or less-standard clients; don't use it if the simple flow below works, since it adds credential management you don't need.
Step 1: Add the Dropbox Dash MCP Server to Cursor
1. In Cursor, open Settings → Cursor Settings → Tools and MCP
2. Click New MCP Server — this opens mcp.json
3. Add the Dropbox Dash entry:
{
"mcpServers": {
"Dropbox Dash MCP": {
"url": "https://mcp.dropbox.com/dash"
}
}
}
4. Save the file, return to Tools and MCP, and click connect next to the new entry
5. A browser window opens for Dropbox's OAuth login — sign in and approve the connection. Dropbox's docs describe this as using Dropbox OAuth for secure authentication, the same account-level login you'd use on dropbox.com
That's the entire config for the common case: one URL, no API key, no environment variables. Restart Cursor if the entry doesn't show a green connected status within a few seconds of approving in the browser.
Step 2: Verify the Connection
Ask Cursor something that requires a live call rather than trusting the green status indicator alone:
Search Dash for anything related to "Q3 roadmap" and summarize what you find
A response referencing real file names or content confirms the connection is live. If you get an authorization prompt again instead of a search result, the OAuth handshake likely didn't fully complete — redo Step 1's connect flow rather than assuming the server is broken.
Manual Setup for Non-Dynamic-Client-Registration Clients
Skip this section if the Step 1 flow worked — it's documented here because some readers land on this guide from a non-Cursor client and the manual path is easy to get wrong. Dropbox names Dynamic Client Registration support explicitly for ChatGPT Codex, ChatGPT Web, Claude Code, Claude Web/Desktop, and Cursor. Clients outside that list need a Dropbox app created manually:
1. Go to the Dropbox App Console and create a new app
2. Enable these scopes: account_info.read, dash/content.read, dash/content.write
3. Record the app's access token, App key, and App secret
4. Configure your MCP client with those three credentials according to its own auth-block syntax — this varies by client and Dropbox's docs don't publish a universal JSON shape for it, so consult your specific client's documentation for how it expects a manual OAuth app's credentials to be supplied
Because Cursor has built-in Dynamic Client Registration support, you should not need this path. If Step 1's connect button doesn't open a browser OAuth prompt at all, that's more likely a Cursor version or network issue than a signal you need the manual flow.
Practical Workflows
Ground a spec in the source document instead of your memory of it
Find the Dash-indexed doc "2026 API Migration Plan" and pull the
section on backward compatibility so I can check my implementation
against what was actually agreed, not what I remember from the meeting
Cross-reference a design or brand asset while coding
Search Dash for the latest brand guidelines and tell me the approved
hex codes for primary and secondary colors, then check them against
what's currently in our CSS variables file
Pull context before writing a PR description
Search Dash for any doc related to "checkout redesign" and summarize
the stated goals, so I can reference them accurately in this PR description
When Not to Use This
If your organization hasn't adopted Dash and only uses plain Dropbox for file storage, this specific integration won't give Cursor access to your files — you'd be setting up an endpoint that authenticates fine but has nothing indexed to search. Check with whoever administers your Dropbox account about Dash availability before spending time on this setup, since the symptom of "no Dash subscription" and "OAuth misconfigured" can look identical from inside Cursor: a connected server that returns nothing useful.
Also worth flagging: because this is a read/search-oriented integration without file-management tools, don't expect it to replace a workflow where you need Cursor to actually create, move, or share files in Dropbox. For that kind of write-heavy file operation, you're better off doing it directly in Dropbox and using this connection purely for retrieval and grounding.
Troubleshooting
Connect button doesn't open a browser window
Restart Cursor completely and retry. If it still doesn't trigger an OAuth prompt, confirm you're on a recent Cursor build — older versions have had inconsistent behavior with newly added remote MCP entries that use bare url config (no command, no headers).
Connected, but searches return nothing
This is almost always a Dash indexing or subscription issue, not a broken MCP connection. Confirm your account actually has Dash access and that the content you're searching for has been indexed by Dash — content that exists in plain Dropbox but was never surfaced to Dash won't show up here.
Authorization prompt reappears on every request
The OAuth token isn't persisting between sessions. Check that the browser-based approval in Step 1 completed fully (landed on a success page, not an error) rather than being closed partway through.
"account not eligible" or similar error during OAuth
Your Dropbox account doesn't have Dash enabled. This isn't a Cursor-side fix — it requires whoever manages your organization's Dropbox subscription to add Dash access.
Results include content from sources you didn't expect
Dash can index more than plain Dropbox files if your org has connected other sources to it (this varies by what's been linked). If Cursor is returning content you didn't expect to be searchable, check what sources are connected to Dash in your account settings rather than assuming the MCP server is misconfigured.
Frequently Asked Questions
Q: Is this the same as a general Dropbox API integration for file management?
A: No. Dropbox Dash MCP is a search-and-read integration scoped to what Dash has indexed. It doesn't expose upload, move, or reorganize tools. If you need Cursor to manage Dropbox files directly rather than search and read them, this specific server isn't built for that.
Q: Do I need a Dropbox Business or Enterprise plan?
A: You need a Dash subscription specifically, which is a separate product from Dropbox's storage plans. A Dropbox account without Dash can still attempt the OAuth connection, but there won't be anything meaningfully indexed for Cursor to search.
Q: Does Cursor need a registered OAuth app, the way some other MCP servers require?
A: No. Dropbox names Cursor explicitly as a client with built-in Dynamic Client Registration support, so the connect flow in Step 1 handles OAuth app registration automatically. The manual App Console path is only for clients outside that supported list.
Q: Can the AI see content I don't personally have access to in Dropbox or Dash?
A: No. The OAuth grant ties the connection to your own account's permissions — the MCP server surfaces what you can already see through Dash, not an organization-wide view beyond your own access.
Q: What happens if I try this without a Dash subscription?
A: The OAuth connection may complete, but searches will return little or nothing useful since there's no Dash index behind your account. This is the most common source of "it connected but doesn't work" confusion with this particular server.