Gateway overview
The VectorStep Gateway is a lightweight Python/FastAPI WebSocket gateway that runs AI agents with MCP tool access. It acts as an executor backend for VectorStep pipelines, providing an alternative to OpenClaw with support for multiple LLM providers and configurable MCP tool servers.
The gateway sits between VectorStep and your LLM providers. VectorStep sends an agent request over WebSocket; the gateway runs the full agentic loop (LLM calls, MCP tool execution, multi-turn conversation) and returns the final result. VectorStep never sees intermediate tool calls or thinking content — it gets one clean response.
This section is the Gateway’s own reference: configuration, agent authoring, the WebSocket and REST protocols, and day-two operations. If you just want the fastest path to a first pipeline running, see the site’s quick start instead — this page is the Gateway’s standalone introduction.
Quick Start
Section titled “Quick Start”# 1. Install dependenciespython3 -m venv .venvsource .venv/bin/activatepip install -r requirements.txt
# 2. Copy and edit the config templatecp samples/config.yaml.example config.yaml# Edit config.yaml — set your LLM provider keys and MCP servers
# 3. Create your agents directorymkdir -p agents/my-agent# Add agent.yaml and soul.md — see Creating Agents below
# 4. Set environment variables for any ${VAR_NAME} placeholders in config.yamlexport ANTHROPIC_API_KEY=sk-ant-...
# 5. Start the gateway (host/port come from config.yaml's `server:` section)python -m gateway.main
# 6. Find your operator token (auto-generated on first run)cat ~/.vectorstep-gateway/identity/device-auth.json# Copy the 'operator' token — you'll need it for VectorStep's configDirectory Structure
Section titled “Directory Structure”VectorStep-Gateway/├── samples/│ └── config.yaml.example # Config template with all options documented├── agents/ # Your agent definitions (gitignored)├── config.yaml # Your config (gitignored)├── gateway/│ ├── main.py # FastAPI app, WebSocket endpoint, REST API│ ├── tracing.py # OpenTelemetry setup and W3C trace context extraction│ ├── auth/│ ├── agents/│ ├── session/│ ├── mcp/│ ├── llm/│ ├── runner/│ └── models/└── requirements.txtWhere next
Section titled “Where next”- Configuration — every
config.yamlfield. - Providers — model routing and Azure OpenAI specifics.
- Creating agents —
agent.yaml,soul.md, hot reload. - WebSocket protocol — the
agentrequest/response contract. - REST API — health, agent management, MCP introspection.
- Operations — metrics, environment variables, performance notes.
- VectorStep integration — wiring the gateway into a pipeline.