Dropbox MCP connector
StorageThe Compify Dropbox connector is an MCP server for Dropbox. Find, read, and manage files in your Dropbox.
What you can do
- Search files and folders
- Read and download file contents
- Upload and move files
- Create shareable links
- Auth
- OAuth (Dropbox)
- Type
- MCP server
- Category
- Storage
- Access
- Scoped per step
How do I connect Dropbox to Claude or ChatGPT?
Add your Compify gateway URL as an MCP server in Claude, ChatGPT, or any MCP client, then sign in to Dropbox once (OAuth (Dropbox)). Compify stores the credential and reuses it across every workflow, with Dropbox tool access scoped per step — no per-workflow re-authentication.
More Storage connectors
Ship at lightspeed
Frequently asked questions
Compify is an MCP gateway that connects AI agents — Claude, ChatGPT, Gemini, Copilot, or any MCP client — to 200+ tools through one URL and one login per vendor. Workflows serialize to versioned YAML specs, so every run is deterministic.
Add your Compify gateway URL as an MCP server in Claude, ChatGPT, or any MCP client, then sign in to each vendor once. Every workflow can then reach those tools, with access scoped per step and credentials reused across runs.
Any client that speaks the Model Context Protocol: Claude (Desktop, Code, and claude.ai), ChatGPT, Gemini, Microsoft Copilot, Perplexity, Ollama, and custom agents you build yourself.
Yes. Both connect AI agents to external tools. Compify focuses on deterministic, versioned workflows you run from any MCP client; Composio focuses on an SDK-first tool catalog for custom agent code. See the full comparison at /compare/compify-vs-composio.
Each workflow serializes to a versioned YAML spec — the same Kit, Connector, and reference set on every run. Same inputs produce the same run, so behavior never drifts between today and next quarter.
A Kit bundles an AI skill with the exact reference docs, images, and examples it needs. The model reads identical context every time, so you never re-explain the task.
Connectors are MCP servers. You bring your own login and OAuth once per vendor — the credential is reused across every workflow, with tool access scoped per step.
Yes. Enterprise plans run the Compify connector gateway inside your own infrastructure with audit logging and scoped access.
No. You compose Kits and Connectors into ordered steps on a visual board. The YAML spec is generated for you and can be edited or version-controlled if you want.