dbx-mcp-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is dbx-mcp-server?

The dbx-mcp-server is a Model Context Protocol (MCP) server that enables integration with Dropbox, allowing MCP-compatible clients to interact with Dropbox through a set of powerful tools.

how to use dbx-mcp-server?

To use dbx-mcp-server, clone the repository, install dependencies, register a Dropbox app, and configure your MCP client to use the server.

key features of dbx-mcp-server?

  • Integration with Dropbox's public API
  • Supports various file operations (list, upload, download, delete)
  • Account information retrieval
  • Search functionality for files and folders

use cases of dbx-mcp-server?

  1. Automating file management tasks in Dropbox.
  2. Building applications that require Dropbox file interactions.
  3. Enhancing MCP-compatible clients with Dropbox capabilities.

FAQ from dbx-mcp-server?

  • Is dbx-mcp-server affiliated with Dropbox?

No, it is an independent integration that works with Dropbox's public API.

  • What programming language is used?

The server is built with TypeScript.

  • How do I authenticate with Dropbox?

The server uses OAuth 2.0 with PKCE for secure authentication.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago