sqry MCP Server
Version: 31.0.0
MCP Registry name: mcp-name: io.github.verivus-oss/sqry
sqry-mcp exposes sqry semantic code-search tools to Model Context Protocol clients.
Modes
Standalone mode:
Daemon-backed mode:
sqry daemon start
sqry daemon load .
sqry-mcp --daemon
Standalone mode currently exposes 39 tools. Daemon-hosted MCP exposes a 17-tool subset backed by sqryd. Use dynamic discovery for exact schemas and descriptions:
MCP clients can also call tools/list, and sqry clients can read sqry://meta/manifest.
Removed in 21.0.0: the sqry_ask natural-language MCP tool was removed. Use sqry_query, semantic_search, and relation_query instead; see Removed features for migration.
Setup
sqry mcp setup --tool claude
sqry mcp setup --tool codex
sqry mcp setup --tool gemini
Preview without writing:
sqry mcp setup --tool codex --dry-run
Codex and Gemini use global MCP config and rely on starting the assistant in the target project. Claude project scope can pin a workspace root.
When setup writes a standalone command, expect --no-daemon. Use --daemon only when you have started and loaded sqryd intentionally.
Prefer discovery over copying static tables:
- MCP
tools/list
sqry-mcp --list-tools
sqry://meta/manifest
sqry://docs/tool-guide
sqry://docs/capability-map
The standalone catalog includes tools for symbol search, navigation, relation queries, graph export, impact analysis, semantic diff, duplicate/cycle/unused detection, workspace status, and context propagation.
Use query for string predicates and filters for structured JSON pre-filters:
{
"name": "semantic_search",
"arguments": {
"query": "kind:function items:true",
"filters": {
"language": ["rust"],
"visibility": "public"
}
}
}
Use items:true or is_definition:true inside query for definition-only predicates. For list_symbols, use the structured items_only parameter instead:
{
"name": "list_symbols",
"arguments": {
"kind": "function",
"language": "rust",
"items_only": true
}
}
On pre-V16 snapshots without trustworthy definition signal, these definition-only surfaces return a reindexRequired / reindex-required advisory instead of silently evaluating stale default-false marker data.
Workspaces
MCP resolves workspace context from explicit paths, file-bearing arguments, MCP roots, recent session context, and current working directory fallback.
For multi-root projects, configure a workspace with .sqry-workspace or a VS Code .code-workspace file containing sqry.workspace.
sqry workspace status . --json
source_root_id
workspace_status.aggregate.source_root_statuses[].source_root_id is an opaque 8-hex display/correlation token. It is not a path and not a path prefix.
Invalid tool path:
Valid tool paths:
src/lib.rs
/absolute/path/to/workspace/src/lib.rs
Under redaction, result paths can be rendered with a source-root prefix for display. Use source_root_id only to correlate that display prefix with aggregate status entries. Cleartext source roots appear only in top-level source_roots[] when the selected redaction preset permits them.
Redaction
The MCP runtime default is minimal. For hosted or external LLM providers, standard is the recommended preset unless stricter path privacy is required. strict is available for stronger redaction.
Keep these separate:
- Runtime default:
minimal
- Recommended external-provider preset:
standard
- Library/environment defaults: see
sqry-mcp-redaction docs for embedding-specific behavior