VectorStep Service MCP
An MCP server that exposes 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
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. VectorStep
requires a credential on every route (SPEC-auth-and-roles.md) — VECTORSTEP_TOKEN must be an
admin-role token from that instance's auth.tokens config, since this server authors
pipelines and steps:
claude mcp add vectorstep-service \
--env VECTORSTEP_BASE_URL=http://127.0.0.1:8000 \
--env VECTORSTEP_TOKEN=<an admin-role token> \
-- /absolute/path/to/VectorStep-Service-MCP/.venv/bin/python -m vectorstep_service_mcp
VECTORSTEP_WEBHOOK_TOKEN is a deprecated alias for VECTORSTEP_TOKEN, kept as a fallback so
an existing deployment doesn't break silently — set VECTORSTEP_TOKEN in new configs.
Full install, client config (Claude Code, Claude Desktop, MCP Inspector), and tool inventory: MCP servers.
Documentation
Full docs at vectorstep.io:
| Section | Covers |
|---|---|
| MCP servers | Install, client config, tool inventory, explain tool, write-path design notes for both MCP servers |
| Pipelines | The pipeline/step schema this server authors against |
The ecosystem
| Repo | Role |
|---|---|
| VectorStep | The orchestration service: webhook intake, pipeline runner, trust gating, UI, analytics |
| VectorStep-Gateway | WebSocket gateway that runs agents: LLM providers, MCP tools, the full agentic loop |
| VectorStep-Service-MCP | MCP server exposing pipeline authoring, run inspection and analytics to Claude Code/Desktop |
| VectorStep-Gateway-MCP | MCP server for authoring and inspecting Gateway agents |
Licence
VectorStep Service MCP is proprietary software, free to download and use under the terms in LICENSE. It's installable from PyPI — that's the Licensor's own distribution channel, not a grant for you to redistribute it further — and this GitHub repository is private.
Bug reports, questions, and feature requests are welcome at contact@vectorstep.io. Code contributions are not accepted — see clause 6 of the licence. For a suspected vulnerability, follow SECURITY.md rather than emailing the address above.
1 maintainer
Metadata
1 maintainer
Release files for vectorstep-service-mcp 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| vectorstep_service_mcp-0.1.4.tar.gz | 49.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vectorstep_service_mcp-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 95.4 kB
Release files / vectorstep_service_mcp-0.1.4.tar.gz
| Download URL | vectorstep_service_mcp-0.1.4.tar.gz |
|---|---|
| Size | 49.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
96357c9e09afaec3b4bf448ccdf7b47049d9a6aec1c43ff9369591492d80d694
|
|
BLAKE2b-256 checksum How to use checksums |
5228cd2697b03e3adbb2472aeab4f9fcb85168df73dd9bd98cb2f77ac9841dbc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency logRelease files / vectorstep_service_mcp-0.1.4-py3-none-any.whl
| Download URL | vectorstep_service_mcp-0.1.4-py3-none-any.whl |
|---|---|
| Size | 46.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
513e285b959a0587a1fb8c2a73fff7e733d54cfa04e05518e0cf62bf9ada4451
|
|
BLAKE2b-256 checksum How to use checksums |
8f844f8fa6dc840ac88338aaea295d6373591027f4069c5f5d88012dfba02489
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency logSecurity for vectorstep-service-mcp 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for vectorstep_service_mcp-0.1.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
