Anyquery

What julien040/anyquery MCP server does

julien040/anyquery MCP server connects an MCP-compatible language model client to Anyquery, a local SQL query engine. Anyquery can query files, PostgreSQL, MySQL, SQLite-compatible databases, and app integrations supplied through plugins. The repository describes support for more than 40 apps, with examples including Apple Notes, Notion, Chrome, and Todoist.

The core engine is built on SQLite. Plugins extend the available sources, and the project also supports loading SQLite extensions. This makes the server suitable when an agent needs to inspect information from several systems without using a separate integration-specific interface for each one.

How it works

The julien040/anyquery MCP server starts through the Anyquery command-line binary. In standard input/output mode, an MCP client starts anyquery mcp --stdio and communicates with the process. Anyquery also supports an HTTP and SSE mode using anyquery mcp --host 127.0.0.1 --port 8070, which can be used through an HTTP and SSE tunnel.

Queries are expressed in SQL and executed by Anyquery against the configured files, databases, or plugins. The project also provides a separate anyquery server command that exposes a MySQL-compatible server for clients such as TablePlus and Metabase; that mode is distinct from the MCP entry point.

Setup and configuration

Install the Anyquery binary through Homebrew, APT, YUM/DNF, Scoop, Winget, Chocolatey, an AUR helper, or the project’s release binaries. macOS and Linux users can also use the project’s shell installer. Building from source requires Go 1.26 or later, cgo, and a C compiler such as GCC or Clang.

For an MCP client using local process transport, configure it to launch anyquery mcp --stdio. The README identifies the command as being started by the LLM client. For network transport, start the HTTP/SSE form and connect the client through the selected tunnel or connection method.

Anyquery’s integrations are plugin-based. Plugins can be installed from the official registry, and users can create plugins or load SQLite extensions. Access to a particular app therefore depends on installing and configuring the relevant plugin; the provided material does not specify credentials or configuration fields for individual integrations.

Tools and capabilities

The julien040/anyquery MCP server provides:

• SQL access to supported files and databases.
• Plugin-based access to connected applications.
• Connections to PostgreSQL, MySQL, and SQLite-compatible databases.
• MCP transport over standard input/output or HTTP and SSE.
• A separate MySQL-compatible server mode.
• Support for SQLite extensions and custom plugins.

Limitations and notes

The available data sources are determined by installed plugins and their individual capabilities. Plugin licensing is separate from the core engine license, so users should review each plugin’s terms.

The core engine is licensed under AGPLv3. The repository states that its RPC library uses MIT licensing, while plugins retain their own licenses. A source build depends on cgo and a compatible C compiler. The provided material does not list specific MCP tool names, client-specific configuration files, or authentication requirements for individual app integrations.