Loom

License: MIT Python 3.11+

MCP server exposing 59 tools for Loom's internal GraphQL API. Works with Claude, Cursor, or any MCP-compatible client.

Features

• List, search, and get detailed metadata for Loom videos
• Read transcripts, captions, AI summaries, chapters, and key takeaways
• Save any fetched content to disk on demand via save_dir parameter
• Manage comments, tasks, reactions, and tags
• Organize with folders, spaces, and watch lists
• Update video settings, share to spaces, and more

Prerequisites

• Python 3.11+
• uv package manager

Setup

Authentication

[!IMPORTANT] This server uses Loom's internal GraphQL API via a browser session cookie. There is no official API key — you must grab the cookie from your browser.

1. Open loom.com in your browser
2. Open DevTools (F12) → Application → Cookies → https://www.loom.com
3. Copy the value of the connect.sid cookie (starts with s%3A...)
4. Paste it as LOOM_COOKIE in your MCP client config below, prefixed with connect.sid=

The cookie lasts about 30 days. See Troubleshooting if you get auth errors.

Installation

Pick your MCP client below for the appropriate config. Each uses uvx to install and run directly from GitHub — no clone needed.

{
  "mcpServers": {
    "loom": {
      "type": "stdio",
      "command": "uvx",
      "args": ["--from", "git+https://github.com/karbassi/loom-mcp.git", "loom-mcp"],
      "env": {
        "LOOM_COOKIE": "connect.sid=s%3A..."
      }
    }
  }
}

claude mcp add loom -- uvx --from git+https://github.com/karbassi/loom-mcp.git loom-mcp

export LOOM_COOKIE="connect.sid=s%3A..."

{
  "mcpServers": {
    "loom": {
      "type": "stdio",
      "command": "uvx",
      "args": ["--from", "git+https://github.com/karbassi/loom-mcp.git", "loom-mcp"],
      "env": {
        "LOOM_COOKIE": "connect.sid=s%3A..."
      }
    }
  }
}

{
  "mcpServers": {
    "loom": {
      "type": "stdio",
      "command": "uvx",
      "args": ["--from", "git+https://github.com/karbassi/loom-mcp.git", "loom-mcp"],
      "env": {
        "LOOM_COOKIE": "connect.sid=s%3A..."
      }
    }
  }
}

git clone [email protected]:karbassi/loom-mcp.git
cd loom-mcp
uv sync
uv run loom-mcp

{
  "mcpServers": {
    "loom": {
      "type": "stdio",
      "command": "uv",
      "args": ["run", "--directory", "/path/to/loom-mcp", "loom-mcp"],
      "env": {
        "LOOM_COOKIE": "connect.sid=s%3A..."
      }
    }
  }
}

Shared HTTP server

By default every client starts its own stdio process. To run one long-lived server that many clients share:

LOOM_COOKIE="connect.sid=s%3A..." LOOM_MCP_TRANSPORT=http LOOM_MCP_PORT=8505 loom-mcp

{
  "mcpServers": {
    "loom": { "type": "http", "url": "http://127.0.0.1:8505/mcp" }
  }
}

The endpoint has no authentication: anything that can connect to it can use every tool with your Loom session, including deleting videos. So:

• The server only binds to loopback (LOOM_MCP_HOST must be 127.0.0.1, localhost, or ::1). Any local process can still connect, so only use HTTP mode on a machine where every local user and process is trusted with your Loom account.
• It always turns on FastMCP's Host/Origin protection, which FastMCP leaves off by default. That check only stops DNS-rebinding attacks from web pages. It does not authenticate anyone.
• To reach it from another machine, put it behind a reverse proxy that controls who can connect: a bearer token, mTLS, an IP allowlist on a private network, or similar. Then add the proxy's hostname to FASTMCP_HTTP_ALLOWED_HOSTS, e.g. FASTMCP_HTTP_ALLOWED_HOSTS='["mcp.example.com"]'. If a browser-based client will call it, also add that client's origin to FASTMCP_HTTP_ALLOWED_ORIGINS, e.g. '["https://mcp.example.com"]'. Never expose the port or the proxy publicly without access control.

File-writing tools (save_dir on the read tools, download_media) write on the server's machine, not the client's, and need absolute paths. See Saving to disk.

Tools

Read (31 tools)

Tools marked with Save accept an optional save_dir parameter — see Saving to disk.

Write (29 tools)

[!NOTE] Write tools modify your Loom data. Destructive actions (delete, archive, move) cannot always be undone.

Saving to disk

Most per-video read tools accept an optional save_dir parameter. When provided, the tool saves its output to {save_dir}/{video_id}/ and returns the file path alongside the content. When omitted, nothing is saved.

save_dir (and download_media's out_path) must be an absolute path; ~ is expanded. Relative paths are rejected because they would resolve against the server process's working directory, which means nothing for a shared or launchd-managed server.

Just ask naturally — "get the details from my last meeting and save them to ~/Downloads/loom" — and the LLM will pass save_dir="~/Downloads/loom" to the tool.

get_video_details saves each piece individually (metadata.json, transcript.txt, summary.txt, etc.) plus a combined details.md.

Troubleshooting

Auth errors

If you get auth errors, your connect.sid cookie has expired (~30 days). Grab a fresh one from your browser using the steps in Authentication.

Debugging with MCP Inspector

npx @modelcontextprotocol/inspector uvx --from git+https://github.com/karbassi/loom-mcp.git loom-mcp

Contributing

Issues and pull requests are welcome on GitHub.

License

MIT