Model Context Protocol

Give your AI a temporary image URL

MCP for DropIMG

Point an MCP client at https://dropimg.io/mcp with your DropIMG API key. Tools map 1:1 to the REST API. Same quotas. Same expiry.

  • Endpoint: https://dropimg.io/mcp
  • Bearer dropimg_api_…
  • upload · get · list · delete
Create an API key REST API

Cursor / Claude

Add a remote Streamable HTTP server. URL: https://dropimg.io/mcp. Header: Authorization Bearer dropimg_api_…. The key is created on Integrations and shown once.

Tools

  • upload_image — base64 or data URL, optional expiry (7d). Returns the URL and when it expires.
  • get_image — metadata for one id, so an agent can ask when abc123xy expires.
  • list_images — your live drops, same envelope as REST.
  • delete_image — owner delete. No delete tokens on MCP.

OAuth

Clients that speak MCP 2026-07-28 authorization can register and Connect DropIMG. Scopes match the API key: images:write, images:read, images:delete. The magic-link session is only the identity behind that flow.

MCP questions

How do I connect?

Create an API key on Integrations. In Cursor or Claude, add a remote MCP server at https://dropimg.io/mcp with Authorization: Bearer dropimg_api_…. OAuth is also available for clients that support MCP authorization.

Which tools exist?

upload_image, get_image, list_images, and delete_image. Upload accepts base64 or a data URL plus an optional expiry label.

Is this a second backend?

No. MCP calls the same createDrop path as the website, ShareX, the extension, and /api/v1.

Do uploads show in My drops?

Yes. source=mcp, owned by your account, same history caps as the rest of DropIMG.