MCP server exposing VectorStep's authoring, inspection, and analytics surface to MCP clients (Claude Code/Desktop).
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"vectorstep-service-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# VectorStep Service MCP An [MCP](https://modelcontextprotocol.io) server that exposes [VectorStep](https://github.com/bantex01/VectorStep) — pipeline authoring, run inspection, and analytics — to MCP clients such as Claude Code and Claude Desktop. ## What it is A separate, standalone repository and process with no import-level dependency on VectorStep — the two are coupled only over HTTP, so each can be developed, versioned, and deployed independently. It lets an MCP client create and edit pipelines and step-library definitions (with the same validation VectorStep itself uses), inspect runs and steps, answer operational and quality questions, and trigger runs or submit human feedback. Agents are not authored here — that's the job of the companion `VectorStep-Gateway-MCP`; this server may only read agents, to help author pipelines that reference them. ## Quick start ```bash python3 -m venv .venv .venv/bin/pip install -e . ``` CI runs this repo's test suite on every push and pull request (`.github/workflows/tests.yml`). Then register it with your MCP client, pointing at a running VectorStep instance: ```bash claude mcp add vectorstep-service \ --env VECTORSTEP_BASE_URL=http://127.0.0.1:8000 \ -- /absolute/path/to/VectorStep-Service-MCP/.venv/bin/python -m vectorstep_service_mcp ``` Full install, client config (Claude Code, Claude Desktop, MCP Inspector), and tool inventory: [MCP servers](https://vectorstep.io/docs/integrations/mcp/). ## Documentation Full docs at [vectorstep.io](https://vectorstep.io/docs/): | Section | Covers | |---|---| | [MCP servers](https://vectorstep.io/docs/integrations/mcp/) | Install, client config, tool inventory, `explain` tool, write-path design notes for both MCP servers | | [Pipelines](https://vectorstep.io/docs/pipelines/schema/) | The pipeline/step schema this server authors against | ## The ecosystem | Repo | Role | |---|---| | **VectorStep** | The orchestration service: webhook intake, pipeline runner, trust gati…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.