MCP

Connect an AI client

Use the stateless Streamable HTTP endpoint and authenticate every request with your Bearer key: https://video2url.com/api/mcp.

Recommended

Option A — let your Agent install it

Copy this entire prompt into Codex, Claude Code, Cursor, or another coding agent. The Agent should detect your MCP client and finish the setup with you.

Agent installation prompt

Set up the Video2URL remote MCP server in my current AI coding client. First detect which MCP-compatible client and operating system I am using. Ask me for my Video2URL API key only when needed and never print it back, log it, or commit it to a repository. Configure a server named video2url using the Streamable HTTP endpoint https://video2url.com/api/mcp and the Authorization header Bearer <MY_API_KEY>. Use the correct user-level configuration file for this client, preserve all existing MCP servers, and explain every file you change. Reload or restart the client if required. Then verify the connection by listing the Video2URL tools and confirm that create_upload, complete_upload, get_upload_status, create_share_link, get_share_link, and revoke_share_link are available. If automatic configuration is impossible, give me the exact configuration path and one command or action at a time. Never expose my API key in your final report.

Expected result:Restart or reload your client, open its MCP tools list, and confirm that the six Video2URL tools appear. If they do not, check the endpoint, Bearer prefix, and key permissions.

Option B — configure it manually

Use this generic remote-server entry if your client supports Streamable HTTP. Replace only the YOUR_API_KEY placeholder, then merge the video2url entry into your existing configuration.

MCP client configuration

{
  "mcpServers": {
    "video2url": {
      "url": "https://video2url.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Verify the connection

Restart or reload your client, open its MCP tools list, and confirm that the six Video2URL tools appear. If they do not, check the endpoint, Bearer prefix, and key permissions.

create_upload

Requires filename, MIME type, and size in bytes; returns a presigned URL.

complete_upload

Requires uploadId after the raw-file PUT succeeds.

get_upload_status

Requires uploadId and returns upload status plus the file record when ready.

create_share_link

Requires fileId; title, visibility, and password are optional, with visibility defaulting to unlisted.

get_share_link

Requires shareId and returns a share link owned by the authenticated user.

revoke_share_link

Requires shareId and revokes a share link owned by the authenticated user.

For uploads, follow this sequence:

create_upload → Receive an uploadId and a temporary PUT URL.
PUT → Send the raw file directly to the returned URL.
complete_upload → Verify the stored file.
create_share_link → Receive the final share link.