dragdropdo

Hochleistungsfähige und unbegrenzte Dateikonvertierung MCP

Dokumentation

MCP clients (Claude, Claude Code, Cursor)

Connect AI assistants to DragDropDo with the Model Context Protocol (MCP): add the server, sign in to DragDropDo, and allow access.

DragDropDo MCP server

The DragDropDo MCP server exposes the same capabilities as the Business API—upload, convert, compress, merge, zip, PDF password tools, and status polling—as MCP tools. Clients connect over Streamable HTTP (HTTPS) at:

https://mcp.dragdropdo.com/mcp

You connect by signing in: add the server to your assistant, sign in to DragDropDo, and click Allow. There is no key to copy. (API keys are for the REST Business API; the MCP server doesn't accept them.)

How signing in works

When you add DragDropDo to an assistant, it opens a browser window: sign in to DragDropDo (Google, Microsoft or Facebook), check the request, and click Allow. The assistant then gets its own access, renewed automatically.

The approval page shows the app's name and the address it will send you back to (for example claude.ai). Only click Allow if that is the app you are connecting.

Claude (claude.ai, Claude Desktop, Claude mobile)

On Claude plans that support custom connectors:

  1. In Claude, open Settings → Connectors and choose Add custom connector.
  2. Name it (for example DragDropDo) and enter the URL https://mcp.dragdropdo.com/mcp. Click Add.
  3. Click Connect, sign in to DragDropDo, and click Allow.

A connector added on claude.ai is also available in Claude Desktop and the Claude mobile apps. In a chat, enable it from the tools menu and ask, for example, "Can DragDropDo convert WEBP to PNG?"

[!NOTE]

Uploading a file from your computer requires an assistant that can run commands, such as Claude Code or Cursor. In claude.ai, Claude Desktop and Claude mobile the tools can check what DragDropDo supports, but can't yet send a file from your device.

Claude Code

Claude Code supports remote MCP servers over HTTP. Add the server:

claude mcp add --transport http d3 https://mcp.dragdropdo.com/mcp

Then, in Claude Code, run /mcp, select d3 and choose Authenticate. Your browser opens: sign in to DragDropDo and click Allow.

Useful commands: claude mcp list, claude mcp get d3, claude mcp remove d3. Add --scope project to store the entry in the project's .mcp.json, or --scope user for your user config. See Connect Claude Code to tools via MCP.

Cursor

Add an entry with the URL to your MCP config (user: ~/.cursor/mcp.json, or project: .cursor/mcp.json):

{
  "mcpServers": {
    "d3": {
      "url": "https://mcp.dragdropdo.com/mcp"
    }
  }
}

In Cursor's MCP settings the server then shows a sign-in button. Click it, sign in to DragDropDo and click Allow.

Other assistants and custom clients

The server follows the MCP authorization specification (OAuth 2.1 with PKCE and dynamic client registration). A client finds the sign-in from the server's 401 response and from https://mcp.dragdropdo.com/.well-known/oauth-protected-resource/mcp.

For your security, sign-in is open to apps whose sign-in returns to one of these addresses:

  • https://claude.ai/… and https://claude.com/… (Claude)
  • http://localhost, http://127.0.0.1 or http://[::1] on any port (assistants and applications running on your computer, such as Claude Code)
  • cursor://… (Cursor)

If your assistant isn't accepted ("Can't connect this app"), contact us to have it added.

Building your own client? Use an MCP SDK that implements the authorization flow (for example the TypeScript SDK's authProvider option) with a http://localhost redirect URL. For scripts and CI jobs that run without a person to sign in, use the REST Business API with an API key instead: it offers the same operations.

Managing connected apps

Every app you connect appears in Account → API as a Connected app. Connecting the same app again reuses that entry.

To disconnect an app, delete its entry there. It loses access immediately; its next request is refused and it asks you to connect again.

Connected apps don't count toward the number of API keys your plan allows.

Limits

Connected apps use your account's limits, the same as the REST API. Free accounts have a daily limit on operations; with an active subscription there is none. When the limit is reached, tools return an error such as daily operation limit reached, resets at 2026-11-07T00:00:00Z (midnight UTC).

Available tools

The tools are initiate_upload, complete_upload, supported_operation, convert_file, batch_convert_files, compress_file, batch_compress_files, merge_files, zip_files, lock_pdf, unlock_pdf, reset_pdf_password, get_status, poll_status, batch_poll_status and get_download_link. The server also sends instructions describing the upload and operation workflow. Use list_tools from your client after connecting to see the canonical list and schemas for your session.

Troubleshooting

You seeWhat to do
This sign-in link has expiredSign-in links last 10 minutes and work only in the browser where you started. Start again from your assistant.
Can't connect this appThe assistant isn't among the apps that can sign in (see Other assistants and custom clients). Contact us to have it added.
The assistant asks you to connect againThe connection was removed under Account → API, or not used for 30 days. Connect again.
daily operation limit reached, resets at …Your free daily operations are used up. They reset at midnight UTC, or subscribe for no limit.
401 Unauthorized when sending an API keyThe MCP server accepts sign-in only. Remove the Authorization header from your MCP config and connect by signing in.

Related documentation

This documentation is built and hosted on Mintlify, a developer documentation platform.