MediaLab MCP Server

Give Claude direct access to MediaLab. Search, upload, download, organize, and share your media from a conversation, no scripts, no raw API calls.

What it is

The MediaLab MCP server enables Claude to securely connect to MediaLab using the MCP, translating natural language into structured MediaLab API calls.

MediaLab hosts it for you at https://mcp.medialabapps.eu/mcp just connect and go, nothing to install or run yourself.

Each user connects with their own MediaLab private token. No credentials are stored on the server, every request runs in the security context of the user who authenticated it.


What Claude can do

The MCP server exposes MediaLab as a set of tools Claude can call directly on your behalf, grouped by what they let Claude do:

  1. Search & browse - quick name search, structured search using your metadata template fields, and browsing file, folder, and folder-contents details.
  2. Metadata - read the full metadata template, look up or add option values for select-lookup fields, and read or update a file's metadata values.
  3. Folders - create new folders and inspect folder details and contents.
  4. Upload - upload a file from a URL, or from a local file when Claude is running on your own machine.
  5. Download - get a signed, time-limited download URL for a file's source or a specific rendered format.
  6. Comments & reactions - read and add review comments, including timecoded comments for video review, and add or remove emoji reactions.
  7. Share links - generate, update, and revoke public share links for files and folders, and generate upload-invite links for external collaborators.
  8. Branding kits - list your branding kits so the right one can be applied to a share link.

How to start

You'll need:

  1. Claude Code or Claude Desktop installed.
  2. A MediaLab private token generate one under Settings > Profile > API access.
  3. Your MediaLab instance URL, e.g. https://your-company.medialab.app.

Connect Claude to MediaLab

claude mcp add --transport http medialab https://mcp.medialabapps.eu/mcp \
  --header "Authorization: Bearer <your-medialab-private-token>" \
  --header "X-MediaLab-URL: https://your-medialab-instance" \
  --scope user

Run this once from a terminal with Claude Code installed. '--scope user' makes it available in every project on your machine.


Example prompts

Once connected, just ask Claude in plain language - no need to know the tool or parameter names.

Example promptWhat happens
"Find my MediaLab file called "File 1.mp4""Claude calls search_medialab_assets with that query and returns a direct link to the matching file.
"Search MediaLab for a folder named "Demo""Claude sets include_files to false so only matching folders come back.
"Open File 1.mp4 in MediaLab"Claude will open this file in the browser.
"Upload highlights.mp4 to my Marketing folder and generate a share link with download permissions"Claude uploads the file, then generates a share link with the source format downloadable and returns it.
"Search for files with attribution "Jane Doe" and download them to my Downloads folder"Claude looks up the attribution metadata field, finds matching files, and fetches each one's download URL to save locally.
"Leave a comment on file 1234 at 00:01:23 saying the color grading needs work"Claude adds a timecoded review comment to the file, useful for video review workflows.
"Create a "Q1 Campaign" folder under Marketing and set up an upload link so our agency can send us files"Claude creates the folder, then generates an upload-invite link scoped to it.
"What metadata fields do we have for videos, and what are the valid values for "Usage Rights"?"Claude lists the client's metadata fields and looks up the option values for that field.

Security

  1. Each connection authenticates with your own MediaLab private token, sent as a Bearer header on every request.
  2. Nothing is stored server-side, the MCP server holds no credentials of its own.
  3. Your private token grants full access to your account. Treat it like a password and never share it.