Loom

io.github.abhinand-adviciyaPublished by GitHub account abhinand-adviciyav1.0.1Updated Oct 24, 2026

Manage Loom projects, tasks, bugs, defects, clients and phases from AI assistants

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an AI assistant manage Loom projects, tasks, bugs, defects, clients and phases through a hosted remote endpoint.

What you can do
Loom exposes its project-management data to an AI assistant over a remote streamable HTTP connection. According to the registry description, the assistant can work with projects, tasks, bugs, defects, clients and phases. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Useful when you already track work in Loom and want an assistant to read or update projects, tasks, bugs, clients or phases without switching apps. Less relevant if your work is not organized in Loom.
Requirements
A remote endpoint at loom.adviciya.com over streamable HTTP; no local package or runtime is needed. A Loom personal access token is required, sent as a bearer token in the Authorization header, generated from Loom Settings > MCP. Network access to the endpoint is required.
Before you install
The server requires a Loom personal access token in the Authorization header; treat it as a secret and grant only the access you need. Because the assistant can manage projects, tasks, bugs, clients and phases, expect it to be able to change or delete records in your Loom workspace. Your project data is sent to a third-party hosted endpoint.

Installation

In SourceWeft

  1. Open Loom in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.abhinand-adviciya%2Floom/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "loom": {
      "type": "http",
      "url": "https://loom.adviciya.com/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

2
  1. v1.0.1LatestSep 20, 2026
  2. v1.0.0Sep 19, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.