MCP server exposing VectorStep Gateway's agent-management and introspection 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-gateway-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 Gateway MCP An [MCP](https://modelcontextprotocol.io) server that exposes [VectorStep Gateway](https://github.com/bantex01/VectorStep-Gateway) — agent authoring and inspection — 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 the Gateway — the two are coupled only over HTTP, so each can be developed, versioned, and deployed independently. It lets an MCP client create and edit agents (`agent.yaml` + `soul.md`, with the same validation the gateway itself uses), inspect what's available (configured MCP tool servers and their tools, configured LLM providers), and read gateway health/metrics. Pipelines/steps are not authored here — that's the job of the companion `VectorStep-Service-MCP`; the two have clean, non-overlapping tool sets. ## 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 Gateway instance: ```bash claude mcp add vectorstep-gateway \ --env GATEWAY_BASE_URL=http://127.0.0.1:18780 \ --env GATEWAY_OPERATOR_TOKEN=<your-operator-token> \ -- /absolute/path/to/VectorStep-Gateway-MCP/.venv/bin/python -m vectorstep_gateway_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, write-path design notes for both MCP servers | | [Gateway](https://vectorstep.io/docs/gateway/agents/) | Agent authoring (`agent.yaml`, `soul.md`) that this server exposes | ## The ecosystem | Repo | Role | |---|---| | **VectorStep** | The orchestration service: webhook …
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.