Loom MCP server
io.github.buttonmonkey/mcp-loom·v0.3.2·1 starsStdio MCP proxy: intercepts oversized tool results into a queryable embedded DuckDB.
1 stars45 downloads/wk
Reviews
Write oneNobody has reviewed Loom yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Loom tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan36 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 81 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Loom compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- GitHub stars
- 1
- more than 65% of 28,688 servers
- Downloads a week
- 45
- more than 37% of 12,191 servers with a package
Install Loom in Claude Code, Cursor or VS Code
Runs npx -y mcp-loom on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-loom -- npx -y mcp-loom
What the publisher says
From the Loom repository's README, as published. We do not edit it. Read it on GitHub
███╗ ███╗ ██████╗██████╗ ██╗ ██████╗ ██████╗ ███╗ ███╗
████╗ ████║██╔════╝██╔══██╗ ██║ ██╔═══██╗██╔═══██╗████╗ ████║
██╔████╔██║██║ ██████╔╝█████╗██║ ██║ ██║██║ ██║██╔████╔██║
██║╚██╔╝██║██║ ██╔═══╝ ╚════╝██║ ██║ ██║██║ ██║██║╚██╔╝██║
██║ ╚═╝ ██║╚██████╗██║ ███████╗╚██████╔╝╚██████╔╝██║ ╚═╝ ██║
╚═╝ ╚═╝ ╚═════╝╚═╝ ╚══════╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝
The context loom for MCP.
One proxy in front of N servers. Oversized tool results are woven
into queryable datasets — 48k tokens in, 2k envelope out.
warp: results stream in weft: the loom shuttles across
══════════════════════ ═════════════════════════════
│ │ │ │
│ │ │ │ 48,377 tokens ┄┄┄┄┄┄┄┄┄> ✂ intercept
●━━━━┿━━━━┿━━━━┿━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
│ ●━━━━┿━━━━┿━━━━━━━ ingest → DuckDB ━━━━━━┫
│ │ ●━━━━┿━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
│ │ │ ●━━━━ schema · stats · joins ━━┛
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
[ raw floods, dropped ] [ 2,104
What it does
An MCP client asks a tool a question, and the answer comes back as a ten-thousand-row JSON dump — most of which the model didn't need but now has to hold in context. Loom sits in the middle.
When a result is small, it passes through untouched. When a result is large and tabular, Loom ingests it into an embedded DuckDB and hands the model a compact envelope instead: a dataset ref, the schema, column stats, a few sample rows, join hints, and provenance. The model then queries precisely what it needs — including joins across data from different servers, which no single server can answer alone.
The economics: a 48k-token tool result becomes a ~2k-token envelope. The model spends its context on answers, not raw dumps.
When loom helps — and when it won't
Loom earns its place in three situations that cover the ordinary case of real MCP usage:
- Clients with no shell. Claude Desktop, mobile, and agent platforms — the largest client surfaces — have no CLI to fall back to. MCP tools are the model's only path to the data, so interception engages by construction.
- Servers with no model-reachable CLI. Internal tools, SaaS connectors, and credentialed databases whose secrets live only in the server's env block — the bulk of real connectors. There is no gh-equivalent for the model to route around.
- Auditable analysis over persistent datasets. Loom turns "the model eyeballed a dump" into "the model ran verifiable queries over data you can still inspect" — exact SQL over provenance-stamped datasets that stay reopenable and re-queryable after the fact. This one applies everywhere, shell or no shell, and is the honest answer to "why route through loom at all."
Cross-server joins run through all three: no single CLI answers a question spanning two services' data.
Two boundaries, stated plainly:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Loom: common questions
- Is Loom MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Loom safety report
- How do I install Loom?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Loom need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Loom maintained?
- The last commit was 120 days ago (2026-07-06). The latest release is v0.3.2.
- How does Loom compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers); downloads a week 45 (more than 37% of 12,191 servers with a package). Full comparison.