sqry-gemini

name	sqry-gemini
version	20.0.5
description	Setup and workflow for using sqry semantic code search as an MCP server with Gemini CLI. Covers installation, MCP configuration, CLI fallback, and troubleshooting. Tool reference and query syntax are served live by sqry-mcp.

sqry for Gemini CLI

Use this skill to configure Gemini CLI for sqry v20.0.5 MCP-backed semantic code search.

Setup

Install or upgrade sqry:

curl -fsSL https://raw.githubusercontent.com/verivus-oss/sqry/main/scripts/install.sh | bash -s -- --component all
sqry --version
sqry-mcp --version
sqry-lsp --version
sqryd --version

Index the project:

cd /path/to/your/project
sqry index .
sqry index --status --json .

Configure Gemini:

sqry mcp setup --tool gemini
sqry mcp status

Restart Gemini CLI after setup so it reloads MCP servers.

This writes a global entry to ~/.gemini/settings.json:

{
  "mcpServers": {
    "sqry": {
      "command": "/absolute/path/to/sqry-mcp",
      "args": [],
      "env": {}
    }
  }
}

Gemini uses sqry-mcp's session-scoped workspace resolution: explicit path arguments first, then file-bearing arguments, MCP roots, last-resolved workspace, and legacy environment/CWD fallback. Start Gemini from the project directory for the simplest single-repo flow.

MCP mode: standalone vs daemon

Default: standalone sqry-mcp (no --daemon, or --no-daemon). Serves 37 tools and 6 MCP resources including sqry://meta/manifest and sqry://docs/*.

Daemon (sqry-mcp --daemon) warms the graph for long sessions but exposes only a 16-tool subset and zero MCP resources — agents cannot read sqry://meta/manifest or docs on the daemon path.

# Standalone — full tools + resources (preferred)
sqry-mcp --no-daemon

# Daemon — warm graph, reduced tools, no resources
sqry daemon start
sqry daemon load .
sqry-mcp --daemon

Set "args": ["--daemon"] only when you accept the 16-tool, no-resource tradeoff.

Skill Dependency

Also load sqry-semantic-search. It contains the shared routing rules, CLI fallback commands, ambiguity handling, output-size limits, and rebuild recovery steps.

Tool Naming

Gemini CLI commonly exposes sqry MCP tools with the mcp__sqry__ prefix, for example mcp__sqry__semantic_search and mcp__sqry__get_graph_stats.

Read sqry://meta/manifest first when resources are available, then use sqry://docs/capability-map and sqry://docs/tool-guide for the exact installed tool surface.

CLI Fallback

If Gemini cannot see sqry MCP tools after setup or before restart, use:

sqry query 'kind:function AND name:authenticate' --json
sqry graph direct-callers "AuthService::authenticate" --json
sqry impact "AuthService::authenticate" --json

Recommended GEMINI.md Addition

## Code Search

Use sqry MCP tools for semantic code search.
Read `sqry://docs/capability-map` to find the right tool.
Use `sqry` CLI as fallback when MCP is unavailable.
Use grep/rg for literal text search.

Troubleshooting

• No tools visible: restart Gemini CLI after sqry mcp setup --tool gemini.
• Empty results: run sqry index . from the project root, or sqry index --force . after an upgrade or stale graph warning.
• Stale graph or unknown plugin IDs: remove .sqry/graph, .sqry/graphs, and .sqry/analysis, then rebuild.
• Transport error on resource read: MCP server is not running or not configured.
• 404 on sqry://meta/manifest: old server version; upgrade sqry, or switch to standalone sqry-mcp --no-daemon (daemon serves zero resources).