Loom + OpenClaw
How to connect Loom to OpenClaw
Connect Loom to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
On this page
Overview
This guide connects Loom to OpenClaw through Agent200's MCP server. When you finish, OpenClaw can search, read and act in Loom with the tools Agent200 provides, whenever a request needs them.
You add one MCP server to OpenClaw with your Agent200 API key. Your Loom account is connected through managed OAuth: you approve access once on Loom's own page, and Agent200 keeps the connection working.
- Connector
- Loom
- Works with
- OpenClaw ยท Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 8 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Loom enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Loom account. They approve access once, on Loom's own page.
- OpenClaw, with custom MCP servers allowed. OpenClaw is open source and self-hosted: anyone running it can add MCP servers, from the CLI, the config file or the Control UI.
Connect Loom to OpenClaw
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to OpenClaw in the next step, as "Authorization: Bearer <your key>". One key covers Loom and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Store your key in ~/.openclaw/.env
OpenClaw fills
${AGENT200_API_KEY}in its config from~/.openclaw/.env, so the key never sits in the config itself.~/.openclaw/.envMCP: OpenClaw key in ~/.openclaw/.env AGENT200_API_KEY=your-agent200-api-key -
3
Step 3: Save the server
openclaw mcp settakes one JSON object. Always set the transport tostreamable-http: without it OpenClaw uses SSE. Keep the single quotes so your shell leaves${AGENT200_API_KEY}for OpenClaw. In the Control UI, add it under Settings > MCP, then put the header in the config editor on the same page.TerminalMCP: OpenClaw save the server from the CLI openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}' -
4
Step 4: Probe the server
Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.
TerminalMCP: OpenClaw probe the server openclaw mcp doctor agent200 --probe openclaw mcp status --verbose -
5
Step 5: Connect your Loom account
The first time you ask OpenClaw for something in Loom, Agent200 returns an authorization link. Open it and approve access on Loom's own page. Agent200 stores the connection and keeps it working; your password never reaches OpenClaw or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Summarize the Loom Sam sent about the onboarding flow
What should come back
- An answer built from your own Loom data.
-
Behind the scenes, OpenClaw calls an Agent200 tool for Loom, such as
loom_list_videos.
If OpenClaw shows an authorization link instead, you have not connected Loom yet: open it, approve access, then ask again.
Get your API key
Create a key in the Agent200 dashboard. It reaches Loom and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Loom to OpenClaw.
Goal: connect Loom to OpenClaw with Agent200, through its MCP server. Guide: https://www.agent200.com/tools/loom/framework/openclaw/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into OpenClaw's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Loom is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to OpenClaw: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for OpenClaw's exact menus or commands. 4. The first Loom request returns an authorization link if the user has not connected Loom yet: show it to them and continue once they have approved access on Loom's own page. 5. Check it works with this request: "Summarize the Loom Sam sent about the onboarding flow" What should come back: - An answer built from your own Loom data. - Behind the scenes, OpenClaw calls an Agent200 tool for Loom, such as `loom_list_videos`. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Loom, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /tools/loom/framework/openclaw.md
Loom tools OpenClaw can call
-
List videos
Readloom_list_videosList the user's videos and videos shared with them.
-
Get a video
Readloom_get_videoRead a video's title, owner, length and link.
-
Read a transcript
Readloom_get_transcriptRead the transcript of a video.
-
List folders
Readloom_list_foldersList the folders in the user's workspace.
-
Add a comment
Writeloom_add_commentLeave a timestamped comment on a video.
-
Rename a video
Writeloom_rename_videoChange a video's title.
-
Move a video
Writeloom_move_videoMove a video into a folder or space.
-
Share a video
Writeloom_share_videoShare a video with other people.
No tool matches that search.
How it works
-
01
You ask OpenClaw
In your own words, for something in Loom.
-
02
OpenClaw picks a tool
It sees the Loom tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Loom connection, within the tools and scopes your project allows.
-
04
OpenClaw answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Loom account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Loom enforces what its API grants.
Troubleshooting
The connection fails right after adding the server
Check the transport is streamable-http: when it is missing OpenClaw uses SSE, which Agent200 does not serve.
Authentication refused (401)
Check headers.Authorization is Bearer ${AGENT200_API_KEY} and that AGENT200_API_KEY is set for the process running OpenClaw.
The doctor warns about a literal header value
Replace the pasted key with ${AGENT200_API_KEY} and move the key to ~/.openclaw/.env.
Changes do not reach your agent
A Gateway or agent running elsewhere needs its own reload or a restart.
OpenClaw shows a Loom authorization link
You have not connected Loom yet, or the connection needs to be approved again. Open the link, approve access on Loom's own page, then ask OpenClaw again.
A tool call is refused or returns less than expected
Agent200 runs only what your project allows. Check that Loom and the tools you need are enabled in the dashboard's Connectors settings, and that you granted Loom the access the task needs.
The API key was pasted into a chat or committed
Create a new key on the API keys page, replace it in OpenClaw's MCP settings, and stop using the old one. Paste the key only into OpenClaw's settings, never into a chat.