Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Communication - official Loom (Atlassian) server

Atlassian MCP server (Loom tools)

Loom does not run a standalone MCP server; Loom tools ship inside the Atlassian remote MCP server. With them an agent can read Loom videos, transcripts, comments and AI meeting action items, and can comment, share, organize, rename and upload videos within the user's existing Loom permissions. Loom (Atlassian) hosts it at https://mcp.atlassian.com/v2/mcp with OAuth or API key auth.

Last verified 15 tools5 sources

Install

Terminal
claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp
Terminal
codex mcp add atlassian --url https://mcp.atlassian.com/v2/mcp

Generic

JSON
{
"mcpServers": {
    "atlassian": {
      "url": "https://mcp.atlassian.com/v2/mcp"
    }
}
}

Tools

getLoomVideo
A video's core metadata, and optionally its transcript, comments, AI agent briefs, AI-extracted meeting action items, or attached links.
listLoomVideos
The videos you own, most recent first.
listLoomVideosSharedWithMe
Videos others have shared with you, most recent first.
getLoomVideoComments
Comments on a video, each with author and the in-video timestamp it is anchored to.
getLoomMeetingActionItems
The AI-generated meeting action items Loom extracted from a recording.
getLoomVideoDownloadUrl
A time-limited signed URL to download the MP4 file itself.
listLoomFolders
Folders in the current workspace a video can be moved into.
createLoomVideoUpload
Step 1 of 2 for uploading a new video.
publishLoomVideo
Step 2 of 2, finalizes the video publishing.
updateLoomVideoTitle
Rename a video.
updateLoomVideoPermissions
Set visibility to OWNER, WORKSPACE, or PUBLIC.
shareLoomVideo
Share a video with specific Atlassian users by notification.
createLoomVideoComment
Post a comment on a video, anchored to a point in seconds.
createLoomFolder
Create a folder in the current workspace, optionally nested or placed in a space.
moveLoomVideoToFolder
Move a video into a folder in the current workspace.

As documented on October 17, 2026. A running server reports its current list through tools/list.

Notes and caveats

  • Same server as the Atlassian (Rovo) MCP server; dedupe against any Atlassian entry.
  • Loom says it needs no separate server or plugin.
  • The Loom workspace must be linked to an Atlassian Cloud site, and the user approves the READ_LOOM and WRITE_LOOM toolsets.
  • Loom tools are only on Atlassian MCP v2.
  • They were announced on 2026-08-11 as part of the Rovo MCP v2 Preview, and current docs say v2 is released.
  • Existing v1 users are moved to v2 tools automatically on 2027-03-01.
  • MCP calls use Rovo credits.
  • Atlassian's docs give Cursor and VS Code only as one-click install links and marketplace steps, with no copyable snippet.
  • Atlassian also documents a Windsurf JSON config.
  • The repo is a support and docs repo for the hosted server and has no published releases.

FAQ

What does the Atlassian MCP server (Loom tools) do?

Loom does not run a standalone MCP server; Loom tools ship inside the Atlassian remote MCP server. With them an agent can read Loom videos, transcripts, comments and AI meeting action items, and can comment, share, organize, rename and upload videos within the user's existing Loom permissions. The vendor documents 15 tools, including getLoomVideo, listLoomVideos, listLoomVideosSharedWithMe and getLoomVideoComments.

How do I add the Atlassian MCP server (Loom tools) to Claude Code?

Run claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp, copied from Loom (Atlassian)'s docs. This page also has snippets for Codex and Generic.

Does the Atlassian MCP server (Loom tools) need authentication?

Yes, OAuth or API key. Transport: Streamable HTTP. Status: GA, last checked October 17, 2026.

Sources

Last verified against 5 Loom (Atlassian) pages, then re-checked independently.

Newsletter

New MCP servers, the week they ship

One email per week. New official MCP servers, the coding tools that support them and how developers wire them up.