Developer Docs

MediaLab MCP Server

Give Claude direct access to MediaLab. Search your files and folders by name from a conversation, no scripts, no raw API calls.

← Back to Docs

Intro

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.

Instructions

How to start

You'll need:

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

Connection

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.

Prompts

Example prompts

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

Example prompt	What 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.

Security

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