sqry

sqry is a free, open-source tool from Verivus Pty Ltd for querying the structure of a codebase. It parses source code into an abstract syntax tree and a graph of symbols and relationships, supporting questions such as which functions call another. Documented queries cover callers, callees, implementations, dependency cycles and unused symbols. The project lists 37 language plugins: 28 support full relationship tracking, while nine extract symbols and imports. Users must build an index before querying; that index persists so later queries can load the cached graph. sqry runs locally on Linux, macOS and Windows. Its maker says source code stays on the user's machine and the tool has no telemetry. It is released under the MIT license. An MCP server connects it with AI assistants, and an LSP server works with VS Code, Neovim, Helix and LSP 3.17 clients. Installation options include platform installers and cargo. On Windows, the release ZIP includes MinGW runtime DLLs required alongside the executables.

sqry offers local structural queries across a listed set of 37 language plugins. Users should account for the indexing step and check the language plugin's level of relationship support.

sqry suits developers who want to query code relationships locally, including callers, implementations and unused symbols. It may also suit users of supported AI assistants or LSP-compatible editors.

sqry is a locally run code-analysis and search tool for developers who need to understand symbol relationships, not merely match text. It suits maintainers working in an editor, CI pipeline, or AI-assisted workflow, especially when source privacy matters. The trade-off is a required indexing step and uneven relationship support across its language plugins.

Overview

sqry parses a codebase into an abstract syntax tree and builds a graph of symbols and their connections. That model enables structural questions such as which functions call a target, which functions a target calls, where implementations live, whether dependency cycles exist, and which symbols appear unused. Regex search and code navigation are also part of the tool, so it can cover both relationship analysis and conventional pattern finding.

It is open source under the MIT license, runs self-hosted on Linux, macOS, and Windows, and is intended for local processing. Verivus Pty Ltd says source code stays on the user's machine and that sqry has no telemetry. The project also describes cargo-vet dependency auditing and cargo-deny checks for license policy and CVEs on every commit. Users build an index before querying; the resulting graph snapshot persists for later loads, making repeated exploration more practical than one-off inspection.

Key features

Structural analysis and language coverage

Documented queries and graph commands cover callers, callees, implementations, dependency cycles, and unused symbols. The 37 language plugins are not equivalent: 28 provide full relation tracking, while nine provide symbol extraction and import tracking. A team choosing sqry for cross-language call or dependency analysis should verify that its primary languages are in the stronger group; the latter plugins are useful for inventory and import-oriented work but cannot provide the same relationship depth.

Editor and AI integrations

The LSP server works with VS Code, Neovim, Helix, and any LSP 3.17 client, bringing navigation into established editor workflows. An MCP server connects sqry to Claude, Codex, Gemini, Cursor, and Windsurf. The standalone MCP server exposes 39 tools, while daemon mode narrows that to a curated 16-tool set. Developers who want broad AI access can use the full server; teams preferring a smaller operational surface may find daemon mode easier to manage.

Automation and distribution safeguards

The documentation describes installing sqry and invoking its CLI in GitHub Actions, and the home page lists a GitHub Action for checking dead code, cycles, and duplicates on pull requests. There is no public composite action, so CI users assemble their workflow around the installer and commands rather than dropping in a ready-made composite. Public releases include checksums and Sigstore DSSE attestation metadata, and installation scripts verify checksums by default. Windows users must keep the bundled MinGW runtime DLLs beside the executables; the release ZIP includes those files.

Pricing

There is no paid tier or free trial. The free open-source plan fits individual developers and teams able to operate their own tooling, with no hosted service or subscription terms to budget for. In exchange, deployment, indexing, updates, and CI integration remain the user's responsibility.

Platforms

sqry provides installers for Linux, macOS, and Windows, with cargo installation available across all platforms. It supports self-hosted, local operation. Windows deployments need the release's bundled MinGW runtime DLLs alongside the binaries.

Who it's for

sqry is a strong choice for developers tracing call chains, implementations, cycles, and dead symbols across a local codebase, particularly when proprietary source cannot be sent to a service. It also fits teams that want LSP navigation, MCP access for AI assistants, or pull-request checks for structural problems. It is less suitable for a quick search before an index can be built, or for projects whose main language only receives symbol and import extraction rather than full relation tracking.

Pros and cons

• Pros: Structural queries expose callers, callees, implementations, cycles, and unused symbols instead of limiting analysis to text matches.
• Pros: Local, telemetry-free operation and the MIT license keep source processing under the user's control.
• Pros: LSP, MCP, and GitHub Actions support connect the same index to editors, AI assistants, and pull-request checks.
• Pros: Checksums, Sigstore DSSE attestations, and default installer verification strengthen release integrity.
• Cons: Every query workflow starts with an index build, adding setup time for occasional searches.
• Cons: Nine of 37 plugins lack full relationship tracking, which limits deep analysis for those languages.
• Cons: CI documentation relies on the installer and CLI because no public composite action is published.

Alternatives

Code Search Tools is the broader category guide for comparing code-search options. Choose ast-grep when its API, extension, web, or cross-platform workflow better matches your deployment. Sourcebot is the alternative when a freemium service with web, API, or self-hosted access and a free trial is preferable. Code Fundi fits teams seeking hosted multi-codebase search and chat with a paid Dev tier at $21 a month. Code Search suits users wanting full-text search, find-and-replace, CLI, MCP, and SCIP code intelligence on its Community plan. GNU GLOBAL is a free software option for Linux, macOS, Windows, and self-hosted use. LXR Cross Referencer is a free, self-installed web cross-reference tool. Chromium is a free open-source browser available across desktop, mobile, and extension platforms, rather than a direct structural code-analysis counterpart. Chatterbox TTS is free MIT-licensed speech software, not a code-query replacement.

Verdict

Choose sqry if you need local, relationship-aware code analysis with editor, AI, and CI integration at no license cost. Its main reason to look elsewhere is the indexing requirement combined with partial relationship support in nine plugins; teams needing immediate text search or uniformly deep language coverage should consider another tool.