sverklo
v0.29.3

Sverklo + Continue

Continue is an open-source AI code assistant for VS Code and JetBrains. Sverklo is the local-first MCP retrieval backend Continue can use as its codebase context provider.

Continue: https://continue.dev · Sverklo: MIT-licensed, local-first, MCP-native, 37 tools, bundled local embeddings by default · Install: npm install -g sverklo && sverklo init
Relationship: Continue is the assistant UI; sverklo is its retrieval engine. Wire sverklo into Continue's MCP config and the assistant's @codebase-style queries route through sverklo's symbol graph instead of relying on Continue's built-in indexing.

How they fit together

Continue is the agent — it decides what to do, generates code, applies edits. Sverklo is the retrieval layer the agent calls when it needs authoritative answers about your codebase. Without sverklo, the agent generates from training-data patterns and invents function names that don't exist. With sverklo, it looks up real symbols, finds real call sites, measures real blast radius before proposing changes.

The integration is one command:

npm install -g sverklo
cd your-project
sverklo init

sverklo init auto-detects Continue and writes the right MCP config files. The 37 MCP tools appear in the agent's tool list immediately.

Frequently asked questions

What's the best MCP server for Continue.dev?

Sverklo. Continue supports MCP servers as context providers; sverklo registers as one and exposes 37 tools the assistant can call. Symbol-graph lookup, blast-radius analysis, diff-aware risk-scored review, and bi-temporal memory run locally with the default bundled ONNX provider. An explicitly configured remote embedding provider may receive code chunks.

How do I add a symbol graph to Continue?

Run sverklo init in your project. The command writes the MCP config that Continue picks up; the sverklo tools become available to the assistant alongside Continue's built-in retrieval. The default provider needs no API key and stores the index locally; a remote embedding provider is optional and must be explicitly configured.

Is sverklo a replacement for Continue?

No — they're complementary. Continue is the assistant + UI in your editor. Sverklo is the retrieval backend it can call. Use both: Continue for editing, sverklo for grounding.

Can sverklo replace Continue's @codebase indexing?

Sverklo's hybrid retrieval (BM25 + ONNX + PageRank) is more sophisticated than Continue's default indexing — it builds a symbol graph and computes PageRank on imports. If your codebase is large enough that @codebase misses what you need, route through sverklo via MCP instead.

Try it

If you're already using Continue and your agent has hallucinated function names, invented imports, or forgotten yesterday's design decision — sverklo is the retrieval layer that fixes the root cause.

npm install -g sverklo
sverklo init

Or read the 180-task retrieval benchmark first — we publish where sverklo wins and where it loses.

See also