orcho-mcp 0.1.0__tar.gz

orcho_mcp-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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 Symphos
+
+   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.

orcho_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,145 @@
+Metadata-Version: 2.4
+Name: orcho-mcp
+Version: 0.1.0
+Summary: Orcho — Model Context Protocol server for Claude Code, Cursor, Zed, and other MCP-speaking clients
+Author-email: Symphos <founder@symphos.ai>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/symphos-ai/orcho-mcp
+Project-URL: Repository, https://github.com/symphos-ai/orcho-mcp
+Project-URL: Issues, https://github.com/symphos-ai/orcho-mcp/issues
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: orcho-core<0.2,>=0.1.0
+Requires-Dist: mcp>=1.2
+Requires-Dist: pydantic>=2.6
+Requires-Dist: anyio>=4.4
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.23; extra == "dev"
+Requires-Dist: pytest-cov>=4.0; extra == "dev"
+Requires-Dist: ruff>=0.5; extra == "dev"
+Dynamic: license-file
+
+# orcho-mcp
+
+[![PyPI](https://img.shields.io/pypi/v/orcho-mcp.svg)](https://pypi.org/project/orcho-mcp/)
+[![Python 3.12+](https://img.shields.io/badge/python-3.12%2B-blue.svg)](https://pypi.org/project/orcho-mcp/)
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](LICENSE)
+[![CI](https://github.com/symphos-ai/orcho-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/symphos-ai/orcho-mcp/actions/workflows/ci.yml)
+[![DCO](https://github.com/symphos-ai/orcho-mcp/actions/workflows/dco.yml/badge.svg)](https://github.com/symphos-ai/orcho-mcp/actions/workflows/dco.yml)
+[![Release](https://github.com/symphos-ai/orcho-mcp/actions/workflows/release.yml/badge.svg)](https://github.com/symphos-ai/orcho-mcp/actions/workflows/release.yml)
+[![codecov](https://codecov.io/gh/symphos-ai/orcho-mcp/branch/main/graph/badge.svg)](https://codecov.io/gh/symphos-ai/orcho-mcp)
+[![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/symphos-ai/orcho-mcp/badge)](https://scorecard.dev/viewer/?uri=github.com/symphos-ai/orcho-mcp)
+
+[Model Context Protocol](https://modelcontextprotocol.io) server for Orcho.
+
+Exposes orcho's runtime to MCP-aware clients (Claude Code, Cursor, Zed, and other MCP-speaking tools) over stdio. Full async control loop — act, observe, decide, inspect — without raw log scraping.
+
+> **Status:** ``v0.1.0`` public release line. Core control loop surfaces are available:
+>
+> - **Act**: ``orcho_run_start`` / ``orcho_run_resume`` / ``orcho_run_cancel`` with L4-test-pinned semantics (process-group signal handling, supervisor-owned restart-recovery, race-aware cancel).
+> - **Observe**: ``orcho_run_status`` / ``orcho_run_history`` / ``orcho_run_metrics`` / ``orcho_run_events_tail`` — read-only, polling-friendly.
+> - **Decide**: ``orcho_phase_handoff_decide`` — generic phase-handoff state transition for paused runs. The pipeline pauses with ``status=awaiting_phase_handoff`` when a phase's declared ``handoff`` policy fires; ``continue`` / ``retry_feedback`` / ``halt`` write a decision artifact (``halt`` flips ``meta.status`` to ``halted`` synchronously). Pure state transition; never spawns.
+> - **Inspect**: ``orcho_run_evidence`` — typed inspection slices (``plan`` / ``findings`` / ``commands`` / ``artifacts`` / ``errors`` / ``sub_runs`` / ``all``) with severity filter (P0..P3).
+>
+> Live progress: ``orcho_run_watch`` emits ordered ``notifications/progress`` when the MCP request carries a ``progressToken``. Clients that don't carry one poll ``orcho_run_status`` / ``orcho_run_events_tail`` against the same run state.
+
+## Install
+
+```bash
+pipx install 'orcho[mcp]'
+```
+
+For a project-managed Python environment:
+
+```bash
+pip install orcho-mcp
+```
+
+This pulls `orcho-core` (the engine), the official `mcp` Python SDK, and the runtime pieces orcho-mcp depends on.
+
+## Create a workspace
+
+Orcho writes run state into an Orcho workspace. Start by pointing it at
+the folder that groups your project repos:
+
+```bash
+orcho workspace init ~/www/my-workspace
+```
+
+The command creates `~/www/my-workspace/workspace-orchestrator/`,
+including `.orcho/` settings and extension-point guides, and prints the
+MCP config snippet for that workspace. To write the snippet directly
+into a project-local MCP config:
+
+```bash
+ORCHO_MCP_COMMAND="$(command -v orcho-mcp)"
+
+orcho workspace init ~/www/my-workspace \
+  --mcp-config ~/www/my-workspace/.mcp.json \
+  --mcp-server-name orcho-my-workspace \
+  --orcho-mcp-command "$ORCHO_MCP_COMMAND"
+```
+
+`ORCHO_MCP_COMMAND` must point to the command your MCP client can run.
+For packaged installs this is normally `orcho-mcp`. For source installs,
+use the absolute path inside the Orcho environment, for example
+`/Users/me/orcho-preview/orcho-core/.venv/bin/orcho-mcp`.
+
+Each MCP server process owns one workspace through `ORCHO_WORKSPACE`.
+For multiple workspaces, add multiple MCP server entries.
+
+## Register with an MCP-aware client
+
+Each client has its own MCP registry/config format. Use
+[`docs/mcp_client_setup.md`](docs/mcp_client_setup.md) for copy-paste
+instructions for Codex CLI/app, Claude Code, Gemini CLI, the Claude app,
+and Antigravity.
+
+## What's inside
+
+```bash
+npx @modelcontextprotocol/inspector orcho-mcp
+```
+
+Opens a web UI on localhost showing every registered tool, resource, and prompt with full JSON schemas — Anthropic's official Inspector ≈ Swagger UI for MCP.
+
+A static catalogue is also committed at [`docs/mcp_schema.json`](docs/mcp_schema.json) — the same shape, snapshotted in CI.
+
+## Control loop
+
+The full contract — **starting**, **observing**, **resuming**, **cancelling**, **deciding** (QA gate), and **inspecting** runs through the MCP wire — lives in [`docs/run_lifecycle.md`](docs/run_lifecycle.md). Tool docstrings stay terse; that file is the long-form reference.
+
+Tool naming is consistent: every run-lifecycle tool is `orcho_run_<verb>`. State-transition and inspection tools sit beside that group with their own names:
+
+| Group | Tools |
+|---|---|
+| **Act** | `orcho_run_start`, `orcho_run_resume`, `orcho_run_cancel` |
+| **Observe** | `orcho_run_status`, `orcho_run_history`, `orcho_run_metrics`, `orcho_run_events_tail` |
+| **Decide** | `orcho_phase_handoff_decide` |
+| **Inspect** | `orcho_run_evidence`, `orcho_run_diff` |
+
+For an end-to-end walkthrough of the full control loop with code, see [`docs/control_loop_walkthrough.md`](docs/control_loop_walkthrough.md).
+
+## Architecture
+
+orcho-mcp is one of the public Orcho runtime packages:
+
+- `orcho-core` — pipeline runtime + CLI (Apache-2.0).
+- **`orcho-mcp`** — MCP server, this repo (Apache-2.0).
+
+The post-v1 cross-MCP consumer roadmap (orcho-as-MCP-client — pipeline agents calling external GitHub / Linear / Slack MCP servers) is documented in `orcho-core/docs/plans/2026-05-06-cross-mcp-orchestration.md`.
+
+For contributor-facing architecture and test guidance:
+
+- [`docs/architecture/mcp_boundaries.md`](docs/architecture/mcp_boundaries.md)
+  describes the package boundaries enforced by the architecture tests.
+- [`docs/architecture/observation_delivery.md`](docs/architecture/observation_delivery.md)
+  defines the durable replay contract for MCP observation and notification use.
+- [`docs/testing.md`](docs/testing.md) explains the test philosophy, layer model,
+  fixture style, and verification commands.
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

orcho_mcp-0.1.0/README.md

@@ -0,0 +1,122 @@
+# orcho-mcp
+
+[![PyPI](https://img.shields.io/pypi/v/orcho-mcp.svg)](https://pypi.org/project/orcho-mcp/)
+[![Python 3.12+](https://img.shields.io/badge/python-3.12%2B-blue.svg)](https://pypi.org/project/orcho-mcp/)
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](LICENSE)
+[![CI](https://github.com/symphos-ai/orcho-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/symphos-ai/orcho-mcp/actions/workflows/ci.yml)
+[![DCO](https://github.com/symphos-ai/orcho-mcp/actions/workflows/dco.yml/badge.svg)](https://github.com/symphos-ai/orcho-mcp/actions/workflows/dco.yml)
+[![Release](https://github.com/symphos-ai/orcho-mcp/actions/workflows/release.yml/badge.svg)](https://github.com/symphos-ai/orcho-mcp/actions/workflows/release.yml)
+[![codecov](https://codecov.io/gh/symphos-ai/orcho-mcp/branch/main/graph/badge.svg)](https://codecov.io/gh/symphos-ai/orcho-mcp)
+[![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/symphos-ai/orcho-mcp/badge)](https://scorecard.dev/viewer/?uri=github.com/symphos-ai/orcho-mcp)
+
+[Model Context Protocol](https://modelcontextprotocol.io) server for Orcho.
+
+Exposes orcho's runtime to MCP-aware clients (Claude Code, Cursor, Zed, and other MCP-speaking tools) over stdio. Full async control loop — act, observe, decide, inspect — without raw log scraping.
+
+> **Status:** ``v0.1.0`` public release line. Core control loop surfaces are available:
+>
+> - **Act**: ``orcho_run_start`` / ``orcho_run_resume`` / ``orcho_run_cancel`` with L4-test-pinned semantics (process-group signal handling, supervisor-owned restart-recovery, race-aware cancel).
+> - **Observe**: ``orcho_run_status`` / ``orcho_run_history`` / ``orcho_run_metrics`` / ``orcho_run_events_tail`` — read-only, polling-friendly.
+> - **Decide**: ``orcho_phase_handoff_decide`` — generic phase-handoff state transition for paused runs. The pipeline pauses with ``status=awaiting_phase_handoff`` when a phase's declared ``handoff`` policy fires; ``continue`` / ``retry_feedback`` / ``halt`` write a decision artifact (``halt`` flips ``meta.status`` to ``halted`` synchronously). Pure state transition; never spawns.
+> - **Inspect**: ``orcho_run_evidence`` — typed inspection slices (``plan`` / ``findings`` / ``commands`` / ``artifacts`` / ``errors`` / ``sub_runs`` / ``all``) with severity filter (P0..P3).
+>
+> Live progress: ``orcho_run_watch`` emits ordered ``notifications/progress`` when the MCP request carries a ``progressToken``. Clients that don't carry one poll ``orcho_run_status`` / ``orcho_run_events_tail`` against the same run state.
+
+## Install
+
+```bash
+pipx install 'orcho[mcp]'
+```
+
+For a project-managed Python environment:
+
+```bash
+pip install orcho-mcp
+```
+
+This pulls `orcho-core` (the engine), the official `mcp` Python SDK, and the runtime pieces orcho-mcp depends on.
+
+## Create a workspace
+
+Orcho writes run state into an Orcho workspace. Start by pointing it at
+the folder that groups your project repos:
+
+```bash
+orcho workspace init ~/www/my-workspace
+```
+
+The command creates `~/www/my-workspace/workspace-orchestrator/`,
+including `.orcho/` settings and extension-point guides, and prints the
+MCP config snippet for that workspace. To write the snippet directly
+into a project-local MCP config:
+
+```bash
+ORCHO_MCP_COMMAND="$(command -v orcho-mcp)"
+
+orcho workspace init ~/www/my-workspace \
+  --mcp-config ~/www/my-workspace/.mcp.json \
+  --mcp-server-name orcho-my-workspace \
+  --orcho-mcp-command "$ORCHO_MCP_COMMAND"
+```
+
+`ORCHO_MCP_COMMAND` must point to the command your MCP client can run.
+For packaged installs this is normally `orcho-mcp`. For source installs,
+use the absolute path inside the Orcho environment, for example
+`/Users/me/orcho-preview/orcho-core/.venv/bin/orcho-mcp`.
+
+Each MCP server process owns one workspace through `ORCHO_WORKSPACE`.
+For multiple workspaces, add multiple MCP server entries.
+
+## Register with an MCP-aware client
+
+Each client has its own MCP registry/config format. Use
+[`docs/mcp_client_setup.md`](docs/mcp_client_setup.md) for copy-paste
+instructions for Codex CLI/app, Claude Code, Gemini CLI, the Claude app,
+and Antigravity.
+
+## What's inside
+
+```bash
+npx @modelcontextprotocol/inspector orcho-mcp
+```
+
+Opens a web UI on localhost showing every registered tool, resource, and prompt with full JSON schemas — Anthropic's official Inspector ≈ Swagger UI for MCP.
+
+A static catalogue is also committed at [`docs/mcp_schema.json`](docs/mcp_schema.json) — the same shape, snapshotted in CI.
+
+## Control loop
+
+The full contract — **starting**, **observing**, **resuming**, **cancelling**, **deciding** (QA gate), and **inspecting** runs through the MCP wire — lives in [`docs/run_lifecycle.md`](docs/run_lifecycle.md). Tool docstrings stay terse; that file is the long-form reference.
+
+Tool naming is consistent: every run-lifecycle tool is `orcho_run_<verb>`. State-transition and inspection tools sit beside that group with their own names:
+
+| Group | Tools |
+|---|---|
+| **Act** | `orcho_run_start`, `orcho_run_resume`, `orcho_run_cancel` |
+| **Observe** | `orcho_run_status`, `orcho_run_history`, `orcho_run_metrics`, `orcho_run_events_tail` |
+| **Decide** | `orcho_phase_handoff_decide` |
+| **Inspect** | `orcho_run_evidence`, `orcho_run_diff` |
+
+For an end-to-end walkthrough of the full control loop with code, see [`docs/control_loop_walkthrough.md`](docs/control_loop_walkthrough.md).
+
+## Architecture
+
+orcho-mcp is one of the public Orcho runtime packages:
+
+- `orcho-core` — pipeline runtime + CLI (Apache-2.0).
+- **`orcho-mcp`** — MCP server, this repo (Apache-2.0).
+
+The post-v1 cross-MCP consumer roadmap (orcho-as-MCP-client — pipeline agents calling external GitHub / Linear / Slack MCP servers) is documented in `orcho-core/docs/plans/2026-05-06-cross-mcp-orchestration.md`.
+
+For contributor-facing architecture and test guidance:
+
+- [`docs/architecture/mcp_boundaries.md`](docs/architecture/mcp_boundaries.md)
+  describes the package boundaries enforced by the architecture tests.
+- [`docs/architecture/observation_delivery.md`](docs/architecture/observation_delivery.md)
+  defines the durable replay contract for MCP observation and notification use.
+- [`docs/testing.md`](docs/testing.md) explains the test philosophy, layer model,
+  fixture style, and verification commands.
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

orcho_mcp-0.1.0/pyproject.toml

@@ -0,0 +1,85 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "orcho-mcp"
+version = "0.1.0"
+description = "Orcho — Model Context Protocol server for Claude Code, Cursor, Zed, and other MCP-speaking clients"
+requires-python = ">=3.12"
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [{ name = "Symphos", email = "founder@symphos.ai" }]
+
+dependencies = [
+    # Pipeline runtime + the public APIs we depend on:
+    #   - pipeline.argv.build_orch_argv (public argv builder)
+    #   - ORCHO_RUN_ID env / --run-id flag
+    #   - core.observability.events.append_event (cross-process append)
+    "orcho-core>=0.1.0,<0.2",
+    # Anthropic's MCP SDK — server + client primitives.
+    "mcp>=1.2",
+    # JSON Schema generation for tool I/O.
+    "pydantic>=2.6",
+    # Async helpers used by FastMCP's stdio transport.
+    "anyio>=4.4",
+]
+
+[project.optional-dependencies]
+dev = ["pytest>=8.0", "pytest-asyncio>=0.23", "pytest-cov>=4.0", "ruff>=0.5"]
+
+[project.urls]
+Homepage = "https://github.com/symphos-ai/orcho-mcp"
+Repository = "https://github.com/symphos-ai/orcho-mcp"
+Issues = "https://github.com/symphos-ai/orcho-mcp/issues"
+
+[project.scripts]
+orcho-mcp = "orcho_mcp.server:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+include = ["orcho_mcp*"]
+
+[tool.setuptools.package-data]
+# Bundle the user-facing onboarding markdown so it's available under
+# non-editable wheel installs, not just `pip install -e .`.
+orcho_mcp = ["_onboarding/*.md"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+# ``"src"`` puts THIS checkout's ``orcho_mcp`` package ahead of any editable
+# install on ``sys.path``, so a bare ``pytest`` exercises the source under
+# development rather than a stale stable install of the same dist.
+# ``"."`` makes ``tests.fixtures.*`` helpers resolvable under default
+# ``--import-mode=prepend``. ``tests/`` and its subdirectories are
+# intentionally NOT packages (no ``__init__.py``) to avoid shadowing the ``mcp``
+# SDK at import time inside test modules; pytest treats them as namespace
+# packages once ``tests/`` is on path.
+pythonpath = ["src", "."]
+addopts = "-ra -m 'not mcp_integration'"
+markers = [
+    "unit: pure unit tests for local handlers and services.",
+    "integration: multi-module tests or tests that exercise subprocess/protocol boundaries.",
+    "acceptance: end-to-end user-visible MCP behaviour checks.",
+    "smoke: small broad-coverage checks suitable for quick confidence.",
+    "serial: must run outside xdist because it uses shared process, filesystem, git, env, port, or global event state.",
+    "mcp_protocol: initialize/list/call stdio protocol, resources, prompts, subscriptions, and schema framing.",
+    "mcp_run_control: run start/status/control, typed pilot, async pilot, and Orcho run lifecycle integration.",
+    "mcp_supervisor: subprocess supervisor, spawn, process lifecycle, and run directory management.",
+    "mcp_observe: watch, event tailing, summaries, progress, and silent/terminal parity.",
+    "mcp_services: read/query services, workspace state, path resolution, and domain service helpers.",
+    "mcp_schema: tool/resource/prompt catalog snapshots and JSON schema contract checks.",
+    "mcp_integration: real pipeline subprocess via --mock; slower; gated. Run with `pytest -m mcp_integration`.",
+]
+
+[tool.ruff]
+target-version = "py312"
+line-length = 100
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "UP", "B", "SIM"]
+ignore = ["E501"]
+
+[tool.ruff.lint.isort]
+combine-as-imports = true

orcho_mcp-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

orcho_mcp-0.1.0/src/orcho_mcp/__init__.py

@@ -0,0 +1,10 @@
+"""orcho_mcp — Model Context Protocol server for the Orcho pipeline engine.
+
+Exposes orcho's runtime to MCP-aware clients (Claude Code, Cursor, Zed,
+and other MCP-speaking tools) over stdio transport. The package exposes
+read tools, run-control tools, resources, MCP prompts, progress
+notifications, and workflow helpers.
+
+Versioning follows the public Orcho release tags.
+"""
+__version__ = "0.1.0"

orcho_mcp-0.1.0/src/orcho_mcp/__main__.py

@@ -0,0 +1,17 @@
+"""Allow ``python -m orcho_mcp`` to start the server.
+
+Console-script users hit ``orcho_mcp.server:main`` directly via the
+setuptools entry-point stub, but ``python -m orcho_mcp`` is the
+universal fallback that works without ``pip install`` happening to
+register the script. Importantly, it goes through the canonical
+``orcho_mcp.server`` import path — not ``__main__`` — so the FastMCP
+instance loaded by ``tools.py`` (etc.) matches the one ``main()`` runs.
+"""
+from __future__ import annotations
+
+import sys
+
+from orcho_mcp.server import main
+
+if __name__ == "__main__":
+    sys.exit(main())