
Pipe (SPR) MCP Server
io.github.MachuraHarryPublished by GitHub account MachuraHarryv1.0.0Updated Oct 24, 2026
AI-native runtime with built-in MCP server. 232 builtins, AI pipelines, RAG, single ~8 MB binary.
Overview
A local MCP server from the Pipe runtime that exposes AI pipeline, agent, RAG and tool-calling builtins to an assistant.
- What you can do
- Run AI pipelines: summarize, translate, classify, extract, generate and ask across configurable providers
- Build agents and swarms: tool registration, tool calling, multi-agent handoffs and vision queries
- Search and retrieve: web and wiki search, embeddings, cosine similarity and nearest-neighbour lookup
- Connect MCP servers and clients: use external stdio or SSE servers and expose Pipe-defined tools
- Manage models and cost: provider, model, host, key, timeout, cache, token and cost controls
- Execute scripts and tools directly, with sandbox profiles, file locking and self-healing retries
- When to use it
- Worth adding when you want an assistant to run Pipe scripts or pipelines locally, chain LLM calls with embeddings and retrieval, or orchestrate agents that call tools and other MCP servers from one binary.
- Requirements
- A local process on the desktop: install the Pipe binary from the provided platform packages or the project installer. AI features need a provider configured, and cloud providers need an API key set through the environment or the key builtin; a local Ollama setup avoids that.
Installation
In SourceWeft
- Open Pipe (SPR) MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
[Image] Pipe — The MCP-native runtime, production-ready
[CI] [License: MIT] [Version] [SPR] [MCP] [GitHub MCP Registry] [MCP Registry]
The first language with built-in MCP — server and client. 249 builtins, single ~8 MB binary. Zero dependencies. Officially listed in the official MCP Registry (v1.1.1, active). One-click install from GitHub MCP Registry for Copilot & VS Code.
What's New in v1.3
Pipe v1.3.0 builds on the multi-agent and vision work from v1.2.0:
- Multi-agent swarms —
ai_swarm/ai_swarm_trace/swarm_agent: named agents hand a conversation off to one another via a reserved tool call, with the full message history carried forward.ai_swarm_streamadds live progress observation (tool calls, handoffs, reasoning, round-check callbacks to intervene mid-run) and now runs independent tool calls within a round in parallel where safe. ai_vision— ask a question about an image (an http(s) URL, local file, or raw bytes) via an OpenAI-compatible vision model.- OpenCode Zen AI provider — 6th provider, with free-tier models usable without any API key.
- Built-in self-updater —
pipe --update/--update-checkfetch, checksum-verify and swap in the latest GitHub release. tool_call— direct, LLM-free invocation of a registered tool.file_lock/file_unlock— real cross-process advisory file locking.elifkeyword inif/elsechains.ai_tool:parallel_safeflag — batches of Pipe-definedfntools can now run in parallel too, not just builtins.pipe -buildnow supports real multi-file projects, preserving relative subdirectory paths.- Hardened sandbox — audit rounds 7-11: closed filesystem-write gate gaps, the
wiki_searchegress gap, anexec_whitelistshell-injection gap, and a hard-link escape. - 249 builtins — 41 AI + 13 MCP + 195 standard, up from 226 in v0.9.3
- 23 modules — MQTT, SQLite, pipe-http, pipe-web, pipe-orm, pipe-cli, and more
Quick Install
Windows (PowerShell): irm https://pipe-lang.com/install.ps1 | iex
The installer downloads the latest release, verifies its SHA256 checksum and installs pipe into ~/.local/bin (or /usr/local/bin when run as root). Pin a version with PIPE_VERSION=v1.0.0. See the full install docs.
Installed copies update themselves against the latest GitHub release: pipe --update (or pipe --update-check to only look, pipe --version to show what you are on). The updater verifies the release checksum and replaces the binary in place.
Privacy & DSGVO
Pipe is DSGVO-konform / GDPR-compliant by design:
- Zero telemetry & analytics — the binary never phones home, nothing leaves your machine
- Self-hosted single binary — runs entirely on your infrastructure
- No cloud — no vendor server processes your data
- Open source (MIT) — fully auditable
- Local AI — with Ollama, not a single byte leaves your network; cloud providers are used only if you configure one
The Problem
Running AI in production is harder than it should be:
- Security — LLMs with file access, network, and
execare a liability. You need fine-grained sandboxing at the language level, not afterthought middleware. - Performance — Sequential API calls turn a 1-second pipeline into a 10-second bottleneck. Parallelism shouldn't require
asyncio.gather()boilerplate. - Vendor Lock-in — Switching from OpenAI to DeepSeek means rewriting your Python SDK code. Provider changes should be one line.
- Tool Integration — Connecting LLMs to external tools (GitHub, databases, filesystems) is a maze of SDKs and API wrappers. MCP should be a language primitive, not a library.
Pipe fixes this at the language level.
What is Pipe?
Pipe is a Semantic Pipeline Runtime (SPR) — a pipeline-native language where summarize, translate, and classify sit on the same syntax level as +, sort, and len. Data flows top to bottom through composable transformations. One binary. Zero dependencies.
Python + LangChain (~80 lines):
Pipe (5 lines):
Model Context Protocol
Pipe has built-in MCP — both as a server and client. No SDKs, no npm packages, no Python. Pure Go stdlib.
MCP Server — Expose your tools
Configure in Claude Desktop (claude_desktop_config.json):
MCP Client — Use external tools
Any stdio MCP server works immediately: Filesystem, GitHub, Git, Postgres, SQLite, Slack, Brave Search, Memory, Sequential Thinking — anything on npm/uvx.
Use Cases
Log Analysis → Incident Report
RAG Pipeline
AI Agent with Tool Calling
Concurrency — 3 LLM Calls in 1.5s, Not 4s
Discord CI/CD Notifications
Comparison: Pipe vs Python + LangChain
Features
- MCP-native — 13 builtins for MCP Server + Client. Pure Go stdlib. Connect to any stdio MCP server
- Ship AI pipelines 10x faster — 41 AI + 13 MCP builtins: no imports, no SDKs, no API wrappers
- Lock down AI agents in one line — Declarative sandbox profiles: restrict
exec,write_file,http_getwith a single block - Deploy in seconds — One statically-linked ~8 MB binary. No venv, no pip, no Docker. Linux, macOS, Windows, Raspberry Pi, or your browser via WebAssembly
- 3 LLM calls in 1.5s, not 4s —
>>starts any pipeline stage in the background. Futures auto-resolve.ai_batchhandles hundreds of texts concurrently with built-in rate limiting - No vendor lock-in — OpenAI, Anthropic (Claude), DeepSeek, Ollama. Switch with one line. Same code works everywhere
- Concurrency primitives — channels (
send/recv), mutex (lock/unlock), counting semaphore (acquire/release) - Pipeline-native syntax —
>sequential,>>parallel. Data flows top to bottom — readable, composable, debuggable - Social platforms built in — Discord webhooks and Telegram bots as Pipe modules. AI code reviews, notifications, chat — zero API costs for sending
- Bytecode VM — Compile to bytecode, run on a stack VM with automatic caching. Measured 0.6x-55x vs tree-walker depending on workload (recursion-heavy code up to ~55x)
- Module ecosystem — 23 curated modules, registry with version pinning (
@1.0.0).pipe -getinstalls, import by name - Built-in testing —
testblocks withassert_eq,assert_error. Run withpipe -test. Zero setup - GitHub Action — Run Pipe directly in CI/CD. No installation needed
- VSCode Extension — Syntax highlighting, IntelliSense, LSP-powered diagnostics and completions
- Self-extracting binary — Ship your pipeline as a standalone executable (
pipe -build)
Quick Start
Try it in your browser
No install needed — Pipe runs fully in your browser via WebAssembly:
[Pipe]
Open the Pipe Playground
GitHub Action
Run Pipe directly in CI/CD — no installation needed:
VSCode Extension
Syntax highlighting and full IntelliSense for .pipe files, powered by a Language Server Protocol client (vscode/) and the pipe-lsp server (cmd/pipe-lsp):
- Completion, hover docs, signature help, go-to-definition, references, rename
- Diagnostics (parse errors, undefined/unused variables) and semantic highlighting
- Format document, auto-completion of brackets, auto-indent and code folding
Or run the extension in development with F5 from the vscode/ folder. See VSCode Extension Documentation.
Module Ecosystem
Pipe has a curated module library — 23 reusable modules with version pinning:
→ Ecosystem Documentation | → Contribute a Module
Execution Modes
54 AI + MCP Builtins (41 AI + 13 MCP)
Understanding
summarize, translate, classify, extract, ask, generate, generate_json
Speed & Control
ai_stream, ai_batch, ai_parallel, ai_rate_limit, ai_chat, ai_chat_json
Search & Retrieval
web_search, wiki_search, embed, embed_batch, cosine_sim, dot_product, nearest
Agents & Tools
agent, agent_ask, agent_clear, ai_tool, ai_with_tools, tool_call, swarm_agent, ai_swarm, ai_swarm_trace, ai_swarm_stream, ai_vision
Config & Cost
ai_provider, ai_model, ai_host, ai_set_key, ai_timeout, ai_cache, ai_cost, ai_tokens, ai_cache_hits, ai_cache_misses
MCP — Model Context Protocol
mcp_server, mcp_serve_stdio, mcp_serve_sse, mcp_tools, mcp_resource, mcp_resource_template, mcp_prompt, mcp_resources, mcp_read_resource, mcp_prompts, mcp_prompt_get, mcp_use_stdio, mcp_use_sse
Self-Healing
try_ai, try_ai_log
Advanced Features
Self-Healing Code (try_ai)
Parallel Pipeline (>>)
Guard Clauses in Match
Concurrency: Channels
Sandbox Profiles
Architecture
- 67 token types, 43 AST node types, 43 opcodes
- ~37,000 LoC Go, 752 tests, 101 example programs
- Zero dependencies — pure Go stdlib
Documentation
→ Full documentation (English) → Vollständige Dokumentation (Deutsch)
Project Structure
Contributing
See CONTRIBUTING.md.
License
MIT — see LICENSE.
Source: README.md at commit cd921a8
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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
- License10 pts