Media2URL MCP Server for ChatGPT

Media2URL provides a remote MCP (Model Context Protocol) server at https://media2url.com/mcp. Once ChatGPT is connected to a Media2URL account, the server can accept a file supplied in the conversation, publish it through the existing Media2URL storage and safety pipeline, and return the direct file URL together with a share page URL.

The connection is account-bound. A visitor who has not connected a Media2URL account cannot publish through the server, and the server does not provide an anonymous upload fallback or an unlimited public ingestion endpoint.

get_profile confirms the stable Media2URL account identity represented by the connection. get_usage returns the current plan, MCP upload counter, allowance for the monthly period, active reservations, remaining capacity, and period end.

publish_media is the write operation. It accepts a supplied file name, content type and base64 file payload up to 2 MB, then performs the same presign, storage upload and finalization sequence used by the account upload system. It returns a URL only after the asset has been registered successfully.

Website uploads have separate Free limits of 10 per UTC day and 300 per UTC month. ChatGPT/MCP, WordPress, Canva publish and Figma publish share a separate Free allowance of 90 uploads per UTC month.

Paid plans keep their larger published upload allowances when used through MCP. Storage, file type, file size, abuse and plan-feature checks still apply to the account and the particular operation, so the smaller MCP allowance does not turn unsupported or unsafe uploads into supported ones.

Open Media2URL from the ChatGPT Plugins Directory and choose Connect. Sign in to Media2URL once, approve the requested permissions on the single OAuth consent page, and return to ChatGPT. Then attach your file and ask ChatGPT to publish it. You do not need to paste an MCP URL or configure a developer setting manually.

The requested scopes are mcp:profile, mcp:usage and mcp:publish. Access tokens are checked for the correct Media2URL audience, scope, expiry and account on every request. Authorization codes and issued credentials are stored as hashes rather than in readable form.

The MCP surface currently exposes only the three tools described above. It does not return bearer tokens, storage credentials, delete links, presigned upload URLs or internal database data in tool results. The public result contains the final Media2URL URLs and the usage information needed to understand the account allowance.

publish_media creates public links through this initial connection. Private-link controls, managed replacement and library actions remain subject to the controls available in the Media2URL website and the tools listed in the connected product experience.

If ChatGPT asks you to connect again, open Media2URL from the Plugins Directory and choose Connect; there is no separate setup sequence. If the browser does not return to ChatGPT after approval, repeat the connection in a normal browser window, then retry the publish request.

For an upload failure, check the returned error category and the account usage before retrying. A quota response means the MCP allowance is full, while an invalid-file or plan response means the file or requested control does not fit the current Media2URL policy. Suspected abuse or copyright issues can be reported through the abuse and DMCA processes below.