// the find
julien040/anyquery
One SQL interface for 60+ tools (e.g., GitHub, Notion, Airtable). Plug into any LLM through MCP.
Anyquery is a SQLite-backed SQL engine that exposes files, databases, and SaaS apps such as Notion, GitHub, and Airtable as queryable tables. It can serve that data to an LLM over MCP or act as a MySQL server for any MySQL-compatible client. It suits developers who want to ask cross-tool questions without writing a one-off API script for each service.
Plugins are separate Go modules, each with its own go.mod, Makefile, and goreleaser config, and they talk to the core over RPC. The RPC library is MIT while the core is AGPL, so third parties can ship plugins without relicensing, and a crashing plugin should not take the engine down with it. The same plugin layer is reachable from the shell, over MCP, and over the MySQL wire protocol, so the README's Metabase and TablePlus guides work without a custom driver. Because it is SQLite underneath, a join between a remote app table and a local CSV or Parquet file is plain SQL rather than a bespoke federation layer.
The README says outright that one person builds and maintains it. With 60+ plugins that each depend on an external API that changes, keeping them all working is a lot for one maintainer, and the integration count badge does not tell you which ones are still passing. The go install path needs cgo, a C toolchain, and three build tags, and it requires Go 1.26 or later, so most people will rely on the prebuilt binaries and trust the release pipeline with OAuth tokens for their Notion and GitHub accounts. Exposing SQL over MCP means the model can reach every connected account, and the README does not say whether plugins are read-only by default or whether write operations go through the same interface. The README also opens with two sponsor banners before the first technical sentence.