Install anyquery with Homebrew, winget

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• anyquery

Project history

The official README describes anyquery as a SQL query engine for 'pretty much anything', including files, databases, and apps such as Apple Notes, Notion, Chrome, and Todoist. It is built on SQLite and extended through plugins, and it can also run as a MySQL-compatible server for tools such as TablePlus and Metabase.

The project also moved into LLM tooling. The README and docs describe Model Context Protocol support via anyquery mcp, HTTP/SSE mode, and a function-calling server through anyquery gpt, allowing ChatGPT, Claude, Cursor, TypingMind, and similar clients to query local or connected data.

Adoption history

anyquery's distribution footprint is broad for a young project. The official README lists Homebrew, APT, YUM/DNF, Scoop, Winget, Chocolatey, Arch AUR, and GitHub release binaries, while the input facts show Homebrew and Winget packages.

The plugin registry is central to adoption: badges in the README expose integration counts and query-hub counts, and docs describe installing plugins, managing profiles, loading SQLite extensions, and connecting LLM interfaces. This makes anyquery more like a queryable integration platform than a fixed CLI.

How it is used

Users run SQL directly in the anyquery shell, pass one-off queries with flags, start a MySQL-compatible server with anyquery server, install plugins from the registry, and create profiles for separate plugin configurations such as personal and work accounts.

The CLI reference documents --config as a path to the configuration database and --database as either a database path or :memory:, but the official docs inspected here do not specify a fixed default config-file path. For that reason the config-file-location is left null rather than inventing a platform path.

Why package nerds care

anyquery is interesting because it compresses several trends into one package: SQLite-as-runtime, plugin-based data virtualization, local-first CLI workflows, MySQL compatibility for BI tools, and MCP/function-calling bridges for LLM clients.

For package managers, the core binary is only the start. The real ecosystem is registry metadata, plugin binaries or extensions, profiles containing service configuration, and security-sensitive integrations with desktop apps and web accounts.

Timeline

• 2024: The public Git tag list starts with 0.1.x releases.
• 2025: The release feed shows 0.4.4 with security and plugin documentation work.
• 2026: The release feed shows 0.4.5 as a security-fix release and describes anyquery as a query engine for querying anything over SQL.

Related projects

• SQLite is the underlying query engine named by the official README.
• The Model Context Protocol is a supported integration mode for LLM clients.
• MySQL-compatible clients such as TablePlus and Metabase are named by upstream as connection targets.
• PRQL and PQL are alternative query languages supported by the CLI.

Sources

• Official README, docs pages, release feed, and source_facts.package-manager.