toolpipe 0.1.0__tar.gz

toolpipe-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,98 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+    tags: ["v*"]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+        os: [ubuntu-latest, macos-latest]
+      fail-fast: false
+
+    runs-on: ${{ matrix.os }}
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: uv sync
+
+      - name: Lint (ruff check)
+        run: uv run ruff check .
+
+      - name: Format (ruff format check)
+        run: uv run ruff format --check .
+
+      - name: Type check (pyright)
+        run: uv run pyright
+
+      - name: Test
+        run: uv run pytest
+
+  publish:
+    needs: [test]
+    if: startsWith(github.ref, 'refs/tags/v')
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: Build
+        run: uv build
+
+      - name: Publish to PyPI
+        run: uv publish
+        env:
+          UV_PUBLISH_TOKEN: ${{ secrets.PYPI_TOKEN }}
+
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  release:
+    needs: [publish]
+    if: startsWith(github.ref, 'refs/tags/v')
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Download build artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Extract changelog for this version
+        run: |
+          TAG="${{ github.ref_name }}"
+          awk -v tag="$TAG" 'index($0, "## " tag) == 1{found=NR; print; next} found && /^## v/{exit} found' CHANGELOG.md > release-notes.md
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v2
+        with:
+          body_path: release-notes.md
+          files: dist/*

toolpipe-0.1.0/.gitignore

@@ -0,0 +1,16 @@
+# Python-generated files
+__pycache__/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+
+# Virtual environments
+.venv
+
+# Local ToolPipe result store (runtime state)
+.toolpipe/
+
+# Miscellaneous
+misc/

toolpipe-0.1.0/CHANGELOG.md

@@ -0,0 +1,26 @@
+# Changelog
+
+## v0.1.0
+
+Initial release: ToolPipe MCP data-plane proxy.
+
+- STDIO proxying of multiple downstream MCP servers with namespaced tools;
+  overlapping namespaces resolve by longest prefix.
+- Fail-fast TOML config validation (bad sections, unknown keys, bad
+  ranges/types) with `${VAR}` environment substitution.
+- Output-schema normalization so large responses can become references.
+- SQLite + content-hashed blob result store (TTL, refcounts, dedup-aware
+  storage limits, blob repair, ref-collision retry).
+- Automatic virtualization middleware (JSON + text, compact `res_*` envelopes);
+  limit rejections raise a clear `ToolError`.
+- Control tools: inspect, read, select (JMESPath), search (iterative walk with
+  depth cap and exact truncation), release, pipe.
+- Zero-config serve with IDE auto-discovery (Claude Code, Cursor, Codex,
+  OpenCode, Zed); first-use consent (once/session/workspace/always) with
+  elicitation and approve-tool fallback; scope files with unresolved `${VAR}`.
+- Server management tools (pending/approve/add/remove/list) and per-server/tool
+  virtualization policies (auto/always/never).
+- Direct result piping with literal args, collision detection, single-bump
+  reads, and re-virtualization of large target outputs.
+- CLI: serve, inspect, results, stats, clean; stderr-only logging.
+- Demo producer/analytics pair; 100k-customer acceptance test.

toolpipe-0.1.0/LICENSE

@@ -0,0 +1,192 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+
+   Copyright 2026 Kunal Kaul
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

toolpipe-0.1.0/PKG-INFO

@@ -0,0 +1,251 @@
+Metadata-Version: 2.5
+Name: toolpipe
+Version: 0.1.0
+Summary: Pass MCP results by reference, not through the LLM.
+Project-URL: Homepage, https://github.com/kunalkaul/toolpipe
+Project-URL: Repository, https://github.com/kunalkaul/toolpipe
+Project-URL: Changelog, https://github.com/kunalkaul/toolpipe/blob/main/CHANGELOG.md
+Author-email: Kunal Kaul <kkdevcode@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: llm,mcp,proxy,tools
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.11
+Requires-Dist: fastmcp<5,>=4
+Requires-Dist: jmespath>=1.1.0
+Description-Content-Type: text/markdown
+
+# ToolPipe
+
+> **Pass MCP results by reference, not through the LLM.**
+
+ToolPipe is an MCP data-plane proxy that keeps large tool outputs out of LLM context by storing them as references and piping the underlying data directly between tools.
+
+```text
+Without ToolPipe:  Tool A → 18 MB → LLM → Tool B
+With ToolPipe:     Tool A → ToolPipe storage ├→ LLM: res_xxx └→ Tool B: actual data
+```
+
+The LLM stays the **reasoning plane** (it sees a small `res_*` reference plus a
+preview). ToolPipe is the **data plane** (it holds the bytes and feeds them to
+the next tool).
+
+## How it works
+
+1. ToolPipe exposes downstream MCP servers' tools through one server, namespaced
+   (`producer_generate_customers`, `analytics_calculate_statistics`).
+2. When a downstream tool returns more than `inline_max_bytes` (default 32 KiB),
+   ToolPipe stores the payload locally (SQLite metadata + content-hashed blobs)
+   and returns a compact reference envelope instead.
+3. The agent then uses control tools to inspect, read, search, or select from
+   the stored result — or pipes data straight into another tool without the
+   payload ever re-entering context.
+
+```text
+100,000 customer objects (~5.1 MiB)
+        │ producer_generate_customers
+        ▼
+ToolPipe res_A (542 B: ref + preview)
+        │ mapping customers[].revenue
+        ▼ analytics_calculate_statistics
+{count: 100000, min: 0.0, max: 4999.0, mean: 2499.5} (60 B)
+```
+
+Measured on the bundled demo: **5,355,595 B → 542 B (~9881x smaller)** for the
+producer step; the final stats response is 60 B.
+
+## Installation
+
+Requires Python 3.11+ and [uv](https://docs.astral.sh/uv/).
+
+```bash
+uv sync
+uv run toolpipe --help
+```
+
+## Configuration
+
+Zero-config first: just add ToolPipe to your agent — no `toolpipe.toml`
+needed.
+
+```bash
+toolpipe serve
+```
+
+On startup ToolPipe auto-discovers the MCP servers you already configured in
+Claude Code (`.mcp.json`), Cursor (`.cursor/mcp.json`), Codex
+(`.codex/config.toml`), OpenCode (`opencode.json`), and Zed
+(`.zed/settings.json`), workspace files first. Discovered servers spawn
+nothing until you approve them: the first time the agent routes a call through
+one, **you** are asked — once, for this session, for this workspace, or always
+— and your choice is saved. Static TOML and explicit imports work as before:
+
+```bash
+toolpipe serve --config toolpipe.toml
+toolpipe serve --import-mcp-json path/to/mcp.json
+toolpipe serve --import-codex-toml ~/.codex/config.toml
+toolpipe serve --no-discover --no-dynamic-servers
+```
+
+See `examples/toolpipe.toml` (working demo config). Format:
+
+```toml
+[toolpipe]
+name = "ToolPipe"
+
+[results]
+storage_dir = ".toolpipe"
+inline_max_bytes = 32768   # below this: pass through unchanged
+preview_max_bytes = 4096   # preview budget inside reference envelopes
+read_max_bytes = 16384     # max bytes per toolpipe_read_result call
+max_result_bytes = 104857600
+max_store_bytes = 1073741824
+ttl_seconds = 3600
+
+[servers.producer]
+command = "uv"
+args = ["run", "python", "examples/demo/producer_mcp.py"]
+
+[servers.analytics]
+command = "uv"
+args = ["run", "python", "examples/demo/analytics_mcp.py"]
+
+[servers.remote]
+url = "http://localhost:9001/mcp"
+```
+
+Secrets use `${VAR}` substitution and fail fast when unset:
+
+```toml
+[servers.github]
+command = "npx"
+args = ["-y", "@example/github-mcp"]
+
+[servers.github.env]
+GITHUB_TOKEN = "${GITHUB_TOKEN}"
+```
+
+### MCP client config (generic Claude/Cursor/Codex style)
+
+Plug-and-play entry — no config file:
+
+```json
+{
+  "mcpServers": {
+    "toolpipe": {
+      "command": "toolpipe",
+      "args": ["serve"]
+    }
+  }
+}
+```
+
+Pinned-config entry:
+
+```json
+{
+  "mcpServers": {
+    "toolpipe": {
+      "command": "toolpipe",
+      "args": ["serve", "--config", "/path/to/toolpipe.toml"]
+    }
+  }
+}
+```
+
+## Consent scopes
+
+| Scope | Meaning | Stored in |
+| ----- | ------- | --------- |
+| `once` | This one call only | Memory |
+| `session` | This ToolPipe process | Memory |
+| `workspace` | This project, across restarts | `<storage_dir>/servers.json` |
+| `always` | Everywhere, across restarts | `~/.toolpipe/servers.json` |
+
+Approvals persist connect info with `${VAR}` references unresolved (resolved
+secrets are never written to disk). Removing a server revokes it everywhere
+but keeps stored results. If your client cannot render approval prompts, the
+agent asks in chat and calls `toolpipe_approve_server` instead.
+
+## Control tools
+
+| Tool | Purpose |
+| ---- | ------- |
+| `toolpipe_inspect_result` | Metadata + bounded preview for a `res_*` ref |
+| `toolpipe_read_result` | Bounded byte-slice reads (diagnostic; prefer select for JSON) |
+| `toolpipe_select_result` | JMESPath selection, e.g. `customers[].revenue` (small→inline, large→new ref) |
+| `toolpipe_search_result` | Substring/regex search; line matches for text, leaf paths for JSON |
+| `toolpipe_release_result` | Drop a stored result immediately |
+| `toolpipe_pipe_result` | Pipe mapped data directly into a downstream tool |
+| `toolpipe_pending_servers` | Discovered servers waiting for approval |
+| `toolpipe_approve_server` | Approve a server (`once`/`session`/`workspace`/`always`) |
+| `toolpipe_add_server` | Manually register a server discovery cannot see |
+| `toolpipe_remove_server` | Revoke a server (stored results are kept) |
+| `toolpipe_list_servers` | Servers with scope, status, tool counts (env redacted) |
+| `toolpipe_set_policy` | `auto`/`always`/`never` per `server` or `server:tool` |
+| `toolpipe_get_policy` | Configured policies (default is `auto`) |
+
+Selectors are JMESPath only — no Python/Jinja/shell evaluation, ever.
+
+## CLI
+
+```bash
+toolpipe serve [--config toolpipe.toml] [--log-level INFO]
+toolpipe serve --import-mcp-json mcp.json --import-codex-toml config.toml
+toolpipe serve --no-discover --no-dynamic-servers
+toolpipe inspect res_abc123 --config toolpipe.toml
+toolpipe results --config toolpipe.toml
+toolpipe stats --config toolpipe.toml     # includes "estimated bytes avoided"
+toolpipe clean --config toolpipe.toml     # expired results only
+```
+
+Logs go to stderr (stdout is the MCP protocol channel). Payloads and secrets
+are never logged.
+
+## Demo
+
+```bash
+uv run toolpipe serve --config examples/toolpipe.toml
+```
+
+Then, from any MCP client: `producer_generate_customers(count=100000)` returns
+a `res_*` reference; `toolpipe_pipe_result` with mapping
+`{"values": "customers[].revenue"}` into `analytics_calculate_statistics`
+returns the stats without the array crossing context.
+
+## Limitations
+
+- STDIO upstream only; one process = one result scope (no multi-user mode).
+- JSON and text virtualization only — images/audio/binary pass through.
+- No CSV/row operations, no streaming, no cross-hose shared refs.
+- Storage pressure fails loudly instead of evicting (`StorageLimitError`); no LRU.
+- No `save_result(path=...)` by design (avoids path-traversal policy).
+
+## Security
+
+- JMESPath only; `eval`/`exec`/shell/Jinja/JS are not supported anywhere.
+- Refs are opaque random tokens, never filesystem paths or hashes.
+- Pipe targets must be approved downstream tools; `toolpipe_*` control tools are rejected.
+- First use asks for approval showing the exact command; `deny` persists nothing.
+- Scope files keep `${VAR}` references unresolved; listings redact env values.
+- `never` policy disables virtualization only — a context-bloat footgun, not a data leak.
+- All size/TTL limits enforced; `stdout` carries protocol output only.
+
+## Development
+
+```bash
+uv sync
+uv run pytest
+uv run ruff check .
+uv run ruff format --check .
+uv run pyright
+uv build
+```
+
+See `CHANGELOG.md` for release history.