Docs

Get started with Vaelor.

Vaelor is a single Go binary that speaks MCP over HTTP. This page covers the install paths and the first calls. For the full tool reference, run tools/list against a live server, or read the README on GitHub — it is the source of truth and stays current with the code.

Install

Two paths. Docker is recommended — one build, one run, no Go toolchain. From source needs Go 1.24+ and a C compiler (CGO for the tree-sitter grammars).

docker build -t vaelor .

Build the image (one-time)

docker run -p 8897:8897 -e LLM_API_BASE=http://host.docker.internal:8317/v1 -e LLM_API_KEY=your-key vaelor

Run it — server listens on :8897/mcp

make build && ./bin/vaelor

Or from source (Go 1.24+ + a C compiler)

Register as an MCP server

One URL, any MCP client. Claude Code, Cursor, Windsurf, Aider, Cline — all speak the Model Context Protocol. Register the HTTP endpoint and the tools appear in your agent.

claude mcp add -s user -t http vaelor http://127.0.0.1:8897/mcp

Claude Code

First call

No local clone needed — understand and call_trace take a GitHub repo directly and fetch it on the first call (cached after). Start with a small repo.

{ "tool": "call_trace", "arguments": { "repo": "gorilla/mux", "symbol": "ServeHTTP", "direction": "callees", "depth": 2 } }

Walks Router.ServeHTTP through the routing path with cycle detection

Add the graph and the embedder (optional)

The core ~30 tools run on the binary alone. Add sidecars to unlock specific tool families: PostgreSQL + Apache AGE (DATABASE_URL) for code_graph and the persistent PageRank/community/surprise signals; pgvector + an embedder (EMBED_URL) for semantic_search and code_research reranking; Redis for L2 cache. Each sidecar is open source and optional.

Full tool reference

Vaelor exposes 30+ MCP tools. The authoritative list is what a running server reports — call tools/list against your endpoint, or read the README's tool table on GitHub. The README stays current with the code; a static page here would drift.

README on GitHub →

Quickstart on the home page

The Quickstart section on the home page covers the same install path with the prerequisite breakdown (what the LLM endpoint unlocks, what each sidecar unlocks) in one place.