The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the StackQL MCP Server listing page.
The Universal Interface for the Agentic Era. Configuration-as-Data. Infrastructure-as-Context.
Read the docs »
Raise an Issue ·
Request a Feature ·
Developer Guide ·
BYO Providers
StackQL is an open-source project built with Golang that allows you to create, modify and query the state of services and resources across different local and remote interfaces, using SQL semantics. Such interfaces canonically include, but are not limited to, cloud and SaaS providers (Google, AWS, Azure, Okta, GitHub, etc.).

StackQL is a standalone application that can be used in client mode (via exec or shell) or accessed via a Postgres wire protocol client (psycopg2, etc.) using server mode (srv).
StackQL parses SQL statements and transpiles them into API requests to the (cloud) resource provider. The API calls are then executed and the results are returned to the user.
StackQL provider interfaces are canonically defined in OpenAPI extensions to the providers' specification. These definitions are then used to generate the SQL schema and the API client. The source for the provider definitions are stored in the StackQL Registry. The semantics of provider interactions are defined in our any-sdk library. For more detail on nuts and bolts, please see the local AGENTS.md file and that of any-sdk.
More detailed design documentation can be found in the here.
StackQL is an MCP server - SQL over 40+ cloud and SaaS providers for AI agents. Point any MCP-capable client (Claude, VS Code, Cursor, etc.) at StackQL and it can query and provision cloud resources using SQL.
Run it over stdio:
StackQL MCP is published to the Official MCP Registry as io.github.stackql/stackql-mcp and distributed via npm, PyPI, Docker, a GitHub Action and .mcpb bundles. Pick an install vector and add the matching block to your MCP client config:
Download the bundle for your platform from the latest release and install it in your MCP client (one-click in clients that support
.mcpb).
stackql-mcp-linux-x64.mcpbstackql-mcp-linux-arm64.mcpbstackql-mcp-windows-x64.mcpbstackql-mcp-darwin-universal.mcpbWire StackQL MCP into agentic CI workflows. Defaults to
read_onlymode, the safe default for CI.
For client-specific setup, authentication and server modes, see the full MCP install and usage docs.
StackQL is available for Windows, MacOS, Linux, Docker, GitHub Actions and more. See the installation instructions below for your platform.
amd64 and arm64)
brew install stackql or brew tap stackql/tap && brew install stackql/tap/stackqlamd64 and arm64)
choco install stackqlstackql.exe file) to a directory of your choicePATH environment variable (optional)curl -L https://bit.ly/stackql-zip -O && unzip stackql-zipstackql file) to a directory of your choicePATH environment variable (optional)View all available StackQL images on DockerHub. Images available include
stackql,stackql-jupyter-demoand more. Pull the latest StackQL base image using:
Want findings, not infrastructure? Run a read-only cross-cloud security & FinOps audit with the standard image in one command — see the Docker audit quickstart.
Use StackQL in your GitHub Actions workflows to automate cloud infrastructure provisioning, IaC assurance, or compliance/security. Available GitHub Actions include:
setup-stackql,stackql-execand more
StackQL can be used via the interactive REPL shell, or via the exec command or ran as a server using the Postgres wire protocol.
ℹ️ StackQL does not require or install a database.
Interactive Shell
Execute a statement or file
ℹ️ output options of
json,csv,tableandtextare available for theexeccommand using the--outputflag
ℹ️ StackQL supports passing parameters using
jsonnetorjson, see Using Variables
Server
For more examples, please check our Blog
Contributions are welcome and encouraged. For more information on how to contribute, please see our contributing guide.
Distributed under the MIT License. See LICENSE for more information. Licenses for third party software we are using are included in the /docs/licenses directory.
Get in touch with us via Twitter at @stackql, email us at info@stackql.io or start a conversation using discussions.
Forks of the following support our work:
golang MCP SDKWe gratefully acknowledge these pieces of work.