mcp-pipe
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
mcp-pipe
Copy/paste for AI tool calls. A self-hosted MCP proxy that works with any host and any MCP server: every tool call gets a handle, so the AI moves data by reference, fixes calls by patch, and runs whole plans in one request — instead of re-typing data it already has.
Docs · pipe__* reference · Security · MIT
The problem
Fixing a call means rewriting it. One wrong column in a 60-line SQL query, and the AI sends all 60 lines again.
Moving data means copying it. Query rows → a slide deck or a sheet: the AI reads the rows, then types them back out into the next tool.
Lists mean one call per item. 200 lines of a file → 200 rows in a sheet, one tool call (and one generated argument) at a time.
Output tokens are the slow, expensive part, and hand-copying is where mistakes creep in.
Related MCP server: OpenAI-Compatible MCP Gateway
Quickstart
Requires Node.js 22+.
npx -y mcp-pipe import claude-desktop --dry-run # see what moves
npx -y mcp-pipe import claude-desktop # move your servers behind mcp-pipe (backup written)Restart Claude Desktop. Your tools are now <server>__<tool>, plus the pipe__* tools. Also: claude-code, cursor, or add it by hand.
No servers to try it on? npx -y mcp-pipe demo-db is a demo SQLite shop database you can wrap.
How it works
host (Claude Desktop / Claude Code / Cursor / your agent)
│ sees one MCP server
▼
mcp-pipe ── store: every call's args + result under a handle (c1, c2, …), and runs
│ resolves "{{ c3.out.rows | jq }}" to real values, then forwards
▼
your MCP servers (postgres, sheets, slides, filesystem, …)the AI wants to… | it sends |
fix a call |
|
pass data on |
|
call a tool per item |
|
run a whole plan |
|
reuse it | keep the pipe in a skill; the AI passes it to |
Every result ends with saved as {{ c3.out }}, the ref that passes it on. Large results come back as a shape + first rows + that ref (peek).
A pipe
name: translate-deck
params: { deck_id: string, lang: string }
steps:
- id: boxes
call: slides__list_text
args: { deck: "{{ deck_id }}" }
- id: tr # the AI (or a subagent) translates; the run pauses here
ai: "Translate each item to {{ lang }}. Return a JSON array, same order, same length."
input: '$boxes | map(.text)'
by: subagent
batch: 20
expect: { type: array, items: { type: string }, sameLengthAs: boxes }
- id: merged
jq: '$boxes | to_entries | map(.value + {text: $tr[.key]})'
- id: write
map: slides__set_text
over: merged
args: { deck: "{{ deck_id }}", slide: "{{ item.slide }}", box: "{{ item.box }}", text: "{{ item.text }}" }To reuse a pipe, put it in a skill (examples): the AI reads the skill, adjusts the YAML if tool names differ, and passes it to pipe__run. The proxy never calls a model: ai steps pause the run and are done by the AI in your conversation, or by a subagent that reads its input by handle, so the main context never holds the deck.
Security in short
Local store (SQLite, mode 600), entries deleted after 7 days; or memory-only.
${env:VAR}/${keychain:service/account}secrets in config.Optional
confirmWrites: true: plans and maps that call write tools show the plan first and need a one-time confirm token.Blind mode: mark a server hidden and its data flows through plans to allowed destinations without reaching the AI.
Never calls an AI model; talks only to the servers you configured.
Details: SECURITY.md · docs/security.
How it compares
plain MCP calls | code mode / programmatic tool calling | declarative tool chainers | mcp-pipe | |
works in any MCP host | ✅ | ❌ needs a specific API/runtime | ✅ | ✅ |
AI writes code | no | yes, in a sandbox | no | no (jq for reshaping) |
fix a call without resending it | ❌ | ❌ | ❌ | ✅ patch + rerun |
data between tools by reference | ❌ | ✅ inside the script | ✅ | ✅ in any call or plan |
saved, parameterised workflows | ❌ | ❌ | partly | ✅ pipes in skills |
steps that need judgement | — | ❌ | ❌ | ✅ AI pause steps |
hide data from the AI | ❌ | partly | ❌ | ✅ blind mode |
Benchmarks
Not published yet. Every number will link to a result file in bench/results/, including where mcp-pipe does not help. How to run them: bench/README.md.
Contributing
npm ci
npm test && npm run typecheck
npm run docs:devIssues and PRs welcome. Conventional commits; every change ends green on npm test && npm run typecheck.
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceA proxy server that wraps existing MCP servers to significantly reduce token consumption by compressing tool descriptions into a two-step interface. It enables users to integrate extensive toolsets without exceeding context limits or incurring high API costs.143Apache 2.0
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that exposes fixed tools for GPT, Claude, and Gemini while routing to any OpenAI-compatible chat completions backend with independent configuration per target.1-
- AlicenseNot gradedqualityCmaintenanceIntelligent MCP proxy server that reduces context bloat by serving only the tools your AI actually needs through semantic search and a fixed two-tool surface.34 PyPI14MIT
- FlicenseNot gradedqualityAmaintenanceA meta-MCP server that aggregates and proxies other MCP servers, letting LLMs discover, add, configure, and toggle backend servers at runtime and use their aggregated tools under unified prefixes. It persists configurations across sessions and supports stdio, HTTP, and hybrid transports with health checks and kit-based server grouping.-