Loom
Reach Loom videos and transcripts through Atlassian's Rovo MCP server, which serves Loom.
Connect it with: MCP. Loom's own documentation: https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/.
What agents can do
Connect Loom so the agents working your tasks can reach it. With it connected, they can:
- Find a Loom video a task names and read its transcript.
- Summarize a recorded walkthrough into steps or acceptance criteria.
- Search Jira and Confluence on the same connection, since the server is Atlassian's.
Before you start
- A Loom workspace you reach with your Atlassian account (Loom's MCP access comes through Atlassian's Rovo MCP server).
- If your organization restricts MCP clients, an admin allows this Jaah's domain in Atlassian Administration > Connectors > Atlassian MCP server.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Loom
Loom's MCP server signs you in itself, so connecting needs no key and no app of your own.
- In Jaah, open Secrets and select New.
- Search for Loom and select its card.
- Name the secret and choose who can use it (see Who can use it).
- Select Connect Loom, sign in to Loom in the window that opens, and approve the access it lists.
- You land back in Jaah on the new secret. Then link it to the projects whose agents should use it (see Use it in an agent session).
Connect with an API key
Loom has no API key option in Jaah: connect with the sign-in above.
Use your own OAuth app
Not needed: Loom's MCP server registers Jaah itself when you connect, so there is no app of your own to create.
Test the connection
Select Test on the secret. Jaah makes one read-only call to Loom with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.
Tell the agent in your task description which secret to use, for example “use the Loom secret org/loom”.
Link Loom's MCP server to a project
Loom also runs an MCP server, which gives agents ready-made Loom tools instead of raw API calls. A project's agents get those tools only once you link the secret to the project:
- Open the project and its MCP tab.
- Select Link, pick the Loom secret, and confirm.
- New tasks on the project start with the Loom tools. Tasks already running keep the tools they started with.
Jaah connects agents to the server through a local bridge, so the token never appears in the agent's configuration or its transcript. A Google Antigravity session in the terminal runtime runs without these tools; on ACP it gets them.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Reconnect: when Loom ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Loom's side too, revoke Jaah in Loom's settings.
Limitations
- Loom has no MCP server of its own: this connection is Atlassian's Rovo MCP server, and the Loom tools it offers are Atlassian's choice.
- One Atlassian connection already covers Loom: you do not need both this card and the Atlassian card.
- Agents can do only what the connected Loom account and its granted scopes allow.
Troubleshooting
Agents see Jira and Confluence tools but no Loom tools
You signed in with an Atlassian account that has no Loom access. Reconnect with the account you use for Loom.
Test says Loom rejected the token (401)
The grant expired or was removed from your Atlassian account's Connected apps. Select Reconnect.
The secret shows Needs reconnect
Loom ended the grant (a password change, a revoked connection or a long idle period). Select Reconnect on the secret and sign in to Loom again.
New tasks on the project have no Loom tools
Link the secret on the project's MCP tab, then start a new task. Tasks already running keep the tools they started with, and an agent marked Not supported on that tab cannot load MCP servers.
Still stuck? Select Test and read the result: it names the value Loom refused and the status it answered.
FAQ
Why does signing in to Loom take me to Atlassian?
Loom's MCP access is served by Atlassian's Rovo MCP server, so you sign in with your Atlassian account.
Does Jaah need an app registered at Atlassian?
No. Jaah registers itself with Atlassian's sign-in server the first time anyone connects, and every later connection reuses that registration.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Loom account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.