pipelex-mcp CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Workspace-level guidance lives in ../CLAUDE.md (Pipelex multi-repo workspace). This file covers only what is specific to pipelex-mcp.

What this repo is

pipelex-mcp exposes registered-method discovery, MTHDS validation, inputs projection and preparation, and durable method runs to MCP hosts. It ships as two servers from one capability core (see the Architecture section): a hosted Skybridge console for remote-connector hosts (ChatGPT, claude.ai, Cowork) and a local workshop stdio server distributed on npm as @pipelex/mcp for coding-agent hosts (Claude Code, Codex, Cursor). Both register the same MCP tools — mthds_list_methods, mthds_validate, mthds_inputs_template, mthds_codegen, mthds_prepare_inputs, and the mthds_run / mthds_run_status / mthds_run_results durable-run family — plus one per-shell tool on each side: the console-only mthds_upload_attachments, which turns a file the user attached in the chat into a run-ready pipelex-storage:// reference (ChatGPT's Apps runtime is the only host that substitutes the attachment), and the workshop-only mthds_download_artifacts, which saves a completed run's produced files under the server's working directory (see the Architecture section for both). mthds_list_methods is the source-free name/intent → canonical-id bridge into the existing current-content validate → inputs-template → run flow. An assistant that already holds .mthds file contents (or, on the workshop, their on-disk paths) calls mthds_validate for a stable, structured verdict it can use to explain and repair diagnostics, mthds_inputs_template for a fill-in template of a pipe's declared inputs, mthds_prepare_inputs to turn filled file-bearing inputs run-ready (uploading assets to Pipelex storage on the workshop; pass-through only on the console), mthds_codegen to project the method's concept set into typed code (ts-zod, python-pydantic, python-structures — the target chosen from the project's context) handed back verbatim with its codegen.lock, and the run family to execute a method durably. On a positive validation verdict the mthds_validate tool ships a Skybridge view, run-graph, that renders the method graph interactively with @pipelex/mthds-ui's GraphViewer (hosted console only — the workshop is tools-first, no views); mthds_list_methods, mthds_inputs_template, mthds_codegen, mthds_prepare_inputs, and the status/results tools are plain tools with no view.