mcp-as-code 0.1.0__tar.gz

mcp_as_code-0.1.0/.gitignore

@@ -0,0 +1,51 @@
+# Python bytecode and caches
+__pycache__/
+*.py[cod]
+*$py.class
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.pyre/
+.tox/
+.nox/
+.coverage
+.coverage.*
+htmlcov/
+coverage.xml
+
+# Virtual environments
+.venv/
+venv/
+env/
+ENV/
+
+# Build and packaging artifacts
+build/
+dist/
+*.egg-info/
+.eggs/
+*.egg
+
+# maco generated/runtime workspace
+.maco/
+gateway.json
+
+# Local environment and editor files
+.env
+.env.*
+!.env.example
+.DS_Store
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# Logs and temporary files
+*.log
+*.tmp
+*.bak
+
+# Example runtime artifacts
+examples/**/.maco/
+examples/**/scratch/
+examples/**/maco-serve-mcp/

mcp_as_code-0.1.0/LICENSE

@@ -0,0 +1,203 @@
+Copyright 2026 Jingkai He
+
+                                 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
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Jingkai He
+
+   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.

mcp_as_code-0.1.0/PKG-INFO

@@ -0,0 +1,212 @@
+Metadata-Version: 2.4
+Name: mcp-as-code
+Version: 0.1.0
+Summary: Execute MCP tools through generated Python code interfaces
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.11
+Requires-Dist: jinja2>=3.1
+Requires-Dist: matchlock==0.2.15
+Requires-Dist: mcp>=1.24.0
+Requires-Dist: pydantic>=2.0
+Description-Content-Type: text/markdown
+
+# maco
+
+`maco` (mcp-as-code) lets an MCP client interact with many upstream MCP tools through a small code-execution interface.
+
+It follows Anthropic's [code-execution-with-MCP pattern](https://www.anthropic.com/engineering/code-execution-with-mcp): keep the large MCP surface area behind a gateway, then let agents write short Python programs for loops, filtering, joins, retries, and structured output. Instead of loading hundreds of tool schemas into the context window, the client gets a compact interface for shell discovery and Python execution.
+
+## At a glance
+
+- Point `maco` at a Claude-style `mcp.json` containing one or many MCP servers.
+- Run `maco serve-mcp` to expose one Streamable HTTP MCP endpoint.
+- Connect your MCP client to that endpoint; it sees only `bash` and `code_execute`.
+- Agents thrive on discovery with `rg` and `fd`, so maco gives them `bash` access to navigate the tool interface as a real filesystem.
+- Use `code_execute` to call upstream MCP tools from Python with `from tools.<server> import <tool>`.
+
+## Why it helps
+
+- **Small context footprint:** the client starts with two tools, not every upstream schema.
+- **Programmatic leverage:** use Python for paging, filtering, joining, caching, retries, and local intermediate files.
+- **Progressive discovery:** inspect only the generated wrappers relevant to the task.
+- **Flexible isolation:** run code locally for fast iteration or inside Docker/Matchlock for stronger isolation.
+- **Works with existing MCP servers:** stdio, Streamable HTTP, and SSE server configs are supported.
+
+## How it works
+
+```text
+MCP client
+    │ sees only bash + code_execute
+    ▼
+maco serve-mcp  ── sandbox ──▶ Python code imports generated tools
+    │
+    ▼
+managed maco gateway
+    │
+    ▼
+upstream MCP servers from mcp.json
+```
+
+`maco serve-mcp` starts a managed gateway for the upstream MCP servers, prepares a generated Python SDK for the sandbox, and serves a compact MCP endpoint for downstream clients.
+
+## Installation
+
+Install the Python package `mcp-as-code`; it provides the `maco` executable:
+
+```bash
+uv tool install mcp-as-code
+```
+
+Then verify the CLI:
+
+```bash
+maco version
+```
+
+## Quick start
+
+Create a Claude-style `mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "filesystem": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/tmp"]
+    }
+  }
+}
+```
+
+Start the `maco` MCP server:
+
+```bash
+maco serve-mcp --config mcp.json --provider docker
+```
+
+Use `--provider local` for a faster, non-isolated local feedback loop.
+
+By default this serves Streamable HTTP MCP at `http://127.0.0.1:8789/mcp`.
+
+Configure an MCP client to connect to that endpoint:
+
+<details>
+<summary>Codex</summary>
+
+```bash
+codex mcp add maco --url http://127.0.0.1:8789/mcp
+```
+
+</details>
+
+<details>
+<summary>Claude Code</summary>
+
+```bash
+claude mcp add --transport http maco http://127.0.0.1:8789/mcp
+```
+
+</details>
+
+From the client, the agent uses the MCP `bash` tool for code navigation inside the sandbox:
+
+```bash
+rg --files /workspace/macosdk/tools
+sed -n '1,160p' /workspace/macosdk/tools/filesystem/__init__.py
+```
+
+Then use `code_execute` to call tools in a context-efficient manner, using loops and conditions instead of traditional linear tool-call chaining:
+
+```python
+from tools.filesystem import listDirectory
+
+for path in ["/tmp", "/var/tmp"]:
+    listing = listDirectory(path=path)
+    entries = listing if isinstance(listing, list) else getattr(listing, "entries", [])
+
+    if not entries:
+        print(f"{path}: empty")
+    else:
+        print(f"{path}: {len(entries)} entries")
+```
+
+See [`examples/serve-mcp`](examples/serve-mcp) for a complete example that wraps multiple upstream MCP servers behind one `maco` endpoint.
+
+If you are using the source checkout directly, the script wrapper is equivalent:
+
+```bash
+./scripts/maco-serve-mcp --config mcp.json --provider docker
+```
+
+## MCP config
+
+`maco` expects Claude-style JSON with a top-level `mcpServers` object.
+
+For environment variables, put them under `env`. `maco` expands `$VAR` and `${VAR}` using the environment of the `maco` process, then passes the resolved values to the upstream MCP server:
+
+```json
+{
+  "mcpServers": {
+    "github": {
+      "command": "docker",
+      "args": [
+        "run",
+        "-i",
+        "--rm",
+        "-e",
+        "GITHUB_PERSONAL_ACCESS_TOKEN",
+        "ghcr.io/github/github-mcp-server"
+      ],
+      "env": {
+        "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_TOKEN}"
+      }
+    }
+  }
+}
+```
+
+HTTP-style servers can use URL and header fields:
+
+```json
+{
+  "mcpServers": {
+    "remote": {
+      "type": "http",
+      "url": "http://127.0.0.1:8000/mcp",
+      "headers": {"Authorization": "Bearer ${TOKEN}"}
+    }
+  }
+}
+```
+
+Supported transports are `stdio`, `http`/`streamable_http`, and `sse`.
+
+## Sandbox providers
+
+Choose the execution provider with `--provider`:
+
+- `local` — fastest feedback loop; runs commands as local subprocesses.
+- `docker` — runs commands in a long-lived Docker container.
+- `matchlock` — runs commands in a long-lived Matchlock micro-VM.
+
+The default Docker/Matchlock image is `ghcr.io/jingkaihe/maco:<VERSION>-alpine`, where `<VERSION>` comes from [`VERSION.txt`](VERSION.txt). It includes `maco`, Python 3.12, `uv`, `pydantic`, `rg`, and `fd`.
+
+## Development
+
+```bash
+make check
+make build
+make image
+```
+
+## Safety notes
+
+- `maco serve-mcp` exposes code execution to whatever can reach its HTTP MCP endpoint; bind and firewall it accordingly.
+- The managed gateway uses a bearer token by default. Do not commit `.maco/gateway.json`.
+- Sandbox providers change the isolation boundary, not the authority of the upstream MCP servers. Treat generated tool calls like direct MCP tool calls.
+- Inspect unfamiliar generated wrappers before running code that calls them.
+
+## License
+
+Apache License 2.0. See [`LICENSE`](LICENSE).

mcp_as_code-0.1.0/README.md

@@ -0,0 +1,199 @@
+# maco
+
+`maco` (mcp-as-code) lets an MCP client interact with many upstream MCP tools through a small code-execution interface.
+
+It follows Anthropic's [code-execution-with-MCP pattern](https://www.anthropic.com/engineering/code-execution-with-mcp): keep the large MCP surface area behind a gateway, then let agents write short Python programs for loops, filtering, joins, retries, and structured output. Instead of loading hundreds of tool schemas into the context window, the client gets a compact interface for shell discovery and Python execution.
+
+## At a glance
+
+- Point `maco` at a Claude-style `mcp.json` containing one or many MCP servers.
+- Run `maco serve-mcp` to expose one Streamable HTTP MCP endpoint.
+- Connect your MCP client to that endpoint; it sees only `bash` and `code_execute`.
+- Agents thrive on discovery with `rg` and `fd`, so maco gives them `bash` access to navigate the tool interface as a real filesystem.
+- Use `code_execute` to call upstream MCP tools from Python with `from tools.<server> import <tool>`.
+
+## Why it helps
+
+- **Small context footprint:** the client starts with two tools, not every upstream schema.
+- **Programmatic leverage:** use Python for paging, filtering, joining, caching, retries, and local intermediate files.
+- **Progressive discovery:** inspect only the generated wrappers relevant to the task.
+- **Flexible isolation:** run code locally for fast iteration or inside Docker/Matchlock for stronger isolation.
+- **Works with existing MCP servers:** stdio, Streamable HTTP, and SSE server configs are supported.
+
+## How it works
+
+```text
+MCP client
+    │ sees only bash + code_execute
+    ▼
+maco serve-mcp  ── sandbox ──▶ Python code imports generated tools
+    │
+    ▼
+managed maco gateway
+    │
+    ▼
+upstream MCP servers from mcp.json
+```
+
+`maco serve-mcp` starts a managed gateway for the upstream MCP servers, prepares a generated Python SDK for the sandbox, and serves a compact MCP endpoint for downstream clients.
+
+## Installation
+
+Install the Python package `mcp-as-code`; it provides the `maco` executable:
+
+```bash
+uv tool install mcp-as-code
+```
+
+Then verify the CLI:
+
+```bash
+maco version
+```
+
+## Quick start
+
+Create a Claude-style `mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "filesystem": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/tmp"]
+    }
+  }
+}
+```
+
+Start the `maco` MCP server:
+
+```bash
+maco serve-mcp --config mcp.json --provider docker
+```
+
+Use `--provider local` for a faster, non-isolated local feedback loop.
+
+By default this serves Streamable HTTP MCP at `http://127.0.0.1:8789/mcp`.
+
+Configure an MCP client to connect to that endpoint:
+
+<details>
+<summary>Codex</summary>
+
+```bash
+codex mcp add maco --url http://127.0.0.1:8789/mcp
+```
+
+</details>
+
+<details>
+<summary>Claude Code</summary>
+
+```bash
+claude mcp add --transport http maco http://127.0.0.1:8789/mcp
+```
+
+</details>
+
+From the client, the agent uses the MCP `bash` tool for code navigation inside the sandbox:
+
+```bash
+rg --files /workspace/macosdk/tools
+sed -n '1,160p' /workspace/macosdk/tools/filesystem/__init__.py
+```
+
+Then use `code_execute` to call tools in a context-efficient manner, using loops and conditions instead of traditional linear tool-call chaining:
+
+```python
+from tools.filesystem import listDirectory
+
+for path in ["/tmp", "/var/tmp"]:
+    listing = listDirectory(path=path)
+    entries = listing if isinstance(listing, list) else getattr(listing, "entries", [])
+
+    if not entries:
+        print(f"{path}: empty")
+    else:
+        print(f"{path}: {len(entries)} entries")
+```
+
+See [`examples/serve-mcp`](examples/serve-mcp) for a complete example that wraps multiple upstream MCP servers behind one `maco` endpoint.
+
+If you are using the source checkout directly, the script wrapper is equivalent:
+
+```bash
+./scripts/maco-serve-mcp --config mcp.json --provider docker
+```
+
+## MCP config
+
+`maco` expects Claude-style JSON with a top-level `mcpServers` object.
+
+For environment variables, put them under `env`. `maco` expands `$VAR` and `${VAR}` using the environment of the `maco` process, then passes the resolved values to the upstream MCP server:
+
+```json
+{
+  "mcpServers": {
+    "github": {
+      "command": "docker",
+      "args": [
+        "run",
+        "-i",
+        "--rm",
+        "-e",
+        "GITHUB_PERSONAL_ACCESS_TOKEN",
+        "ghcr.io/github/github-mcp-server"
+      ],
+      "env": {
+        "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_TOKEN}"
+      }
+    }
+  }
+}
+```
+
+HTTP-style servers can use URL and header fields:
+
+```json
+{
+  "mcpServers": {
+    "remote": {
+      "type": "http",
+      "url": "http://127.0.0.1:8000/mcp",
+      "headers": {"Authorization": "Bearer ${TOKEN}"}
+    }
+  }
+}
+```
+
+Supported transports are `stdio`, `http`/`streamable_http`, and `sse`.
+
+## Sandbox providers
+
+Choose the execution provider with `--provider`:
+
+- `local` — fastest feedback loop; runs commands as local subprocesses.
+- `docker` — runs commands in a long-lived Docker container.
+- `matchlock` — runs commands in a long-lived Matchlock micro-VM.
+
+The default Docker/Matchlock image is `ghcr.io/jingkaihe/maco:<VERSION>-alpine`, where `<VERSION>` comes from [`VERSION.txt`](VERSION.txt). It includes `maco`, Python 3.12, `uv`, `pydantic`, `rg`, and `fd`.
+
+## Development
+
+```bash
+make check
+make build
+make image
+```
+
+## Safety notes
+
+- `maco serve-mcp` exposes code execution to whatever can reach its HTTP MCP endpoint; bind and firewall it accordingly.
+- The managed gateway uses a bearer token by default. Do not commit `.maco/gateway.json`.
+- Sandbox providers change the isolation boundary, not the authority of the upstream MCP servers. Treat generated tool calls like direct MCP tool calls.
+- Inspect unfamiliar generated wrappers before running code that calls them.
+
+## License
+
+Apache License 2.0. See [`LICENSE`](LICENSE).

mcp_as_code-0.1.0/VERSION.txt

@@ -0,0 +1 @@
+0.1.0