The limits of text search
Text search misses structure
ripgrep finds every line containing authenticate — but can't tell you who calls it, what it returns, or whether it's used at all.
Embeddings are slow and imprecise
Semantic search via embeddings takes 1,400ms+ and returns false positives. ~60% precision means you still read code that doesn't match.
Cloud tools send your code offsite
Sourcegraph, GitHub Copilot, and similar tools require uploading your codebase. Not an option for private or regulated code.
STRUCTURAL QUERIES
Exact answers.
Not guesses.
sqry parses your code like a compiler — building a graph of every symbol, call, import, and type relationship. Queries return exact structural results in milliseconds.
MCP INTEGRATION
AI assistants that query,
not guess.
Connect Claude, Codex, or Gemini to sqry via MCP. Your AI assistant gets exact structural answers instead of probabilistic guesses.
$ sqry mcp setupsemantic_search
Search symbols by name, kind, language, and pathdirect_callers
Exact list of every caller of a functioncall_hierarchy
Full inbound and outbound call treefind_unused
Dead code detection across the codebasesemantic_diff
Structural changes between git commitsWorks in your editor.
sqry ships an LSP server with standard protocol support plus 27 custom methods.
sqry lsp --stdio35 languages supported
TIER 1 — Full relation tracking (28 languages)
TIER 2 — Symbols + imports (7 languages)
Built for speed
sqry is open source.
Support subscriptions fund continued development, priority bug fixes, and enterprise support.