MCP Tools DirectoryAbout this integration
Stdio MCP proxy: intercepts oversized tool results into a queryable embedded DuckDB.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.3.2
- Package
- mcp-loom
- Last compatibility test
- Not independently tested
Connect your agent
mcp-loomDocumentation-only qualification from the pinned publisher README and package manifest; the package and integration endpoint were not executed or independently security-audited. Downstream packages, permissions, credentials, and network access remain separately trusted and were not reviewed as part of this wrapper artifact.
Capabilities: MCP proxying, tool namespacing, large-result querying
Connected profiles
Additional details
io.github.buttonmonkey/mcp-loom
Source ↗ · Checked 2026-09-170.3.2
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17mcp-loom
Source ↗ · Checked 2026-09-180.3.2
Source ↗ · Checked 2026-09-18Publisher explicitly documents Loom as a stdio MCP server launched by the upstream client and supervising downstream child processes.
Source ↗ · Checked 2026-09-18Loom has no single integration credential; each downstream server can receive only its own configured environment, so authentication remains source-specific.
Source ↗ · Checked 2026-09-18Launch mcp-loom with npx and an absolute path to a validated loom.config.json listing downstream commands.
Source ↗ · Checked 2026-09-18Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-18