SQL-native query and provisioning engine for cloud infrastructure, served over MCP.
SQL-native query and provisioning engine for cloud infrastructure, served over MCP. The server is positioned for infrastructure-as-code workflows and cloud automation, with coverage across asset management, cloud operations, cloud security, and identity governance.
🛠️ Key Features
SQL-based querying and provisioning
Cloud infrastructure access via MCP
Supports a set of cloud-focused domains: asset-management, cloud-operations, cloud-security, and identity-governance
🚀 Use Cases
Infrastructure-as-code and cloud-config workflows
Cloud automation and provisioning using SQL
Cloud security and CSPM-oriented operations
Identity-governance use cases
⚡ Developer Benefits
MCP integration for model-context workflows
Alignment with developer tooling topics: sql, stackql, mcp, llm-tools, and ai-agents
⚠️ Limitations
No tool count or specific MCP tool list is provided in the available data
Details beyond the description and topics are not included in the provided excerpt
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-shellstackql-shell
How it works
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.
StackQL Context Diagram
The following context diagram describes the StackQL architecture at a high level:
flowchart LR
subgraph StackQL
direction BT
subgraph ProviderDefs
Registry[Provider Registry Docs]
end
subgraph App
Proc[$ stackql exec\n$ stackql shell\n$ stackql srv]
style Proc fill:#000,stroke:#000,color:#fff,text-align:left;
%% ,font-family:'Courier New', Courier, monospace
end
end
User((User)) <--> StackQL <--> Provider[Cloud Provider API]
ProviderDefs --> App
More detailed design documentation can be found in the here.
MCP Server
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:
sh
stackql mcp --mcp.server.type=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:
or via curl -L https://bit.ly/stackql-zip -O && unzip stackql-zip
extract the archive (stackql file) to a directory of your choice
add the directory to your PATH environment variable (optional)
Getting StackQL from DockerHub
View all available StackQL images on DockerHub. Images available include stackql, stackql-jupyter-demo and more. Pull the latest StackQL base image using:
bash
docker pull stackql/stackql
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.
Using StackQL with GitHub Actions
Use StackQL in your GitHub Actions workflows to automate cloud infrastructure provisioning, IaC assurance, or compliance/security. Available GitHub Actions include: setup-stackql, stackql-exec and more
Usage
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
sh
# run interactive stackql queries
stackql shell --auth="${AUTH}"
Execute a statement or file
sh
stackql exec --auth="${AUTH}" -i myscript.iql --iqldata vars.jsonnet --output json
# or
stackql exec --auth="${AUTH}""SELECT id, status FROM aws.ec2.instances WHERE region = 'us-east-1'"
ℹ️ output options of json, csv, table and text are available for the exec command using the --output flag
ℹ️ StackQL supports passing parameters using jsonnet or json, see Using Variables
Server
sh
# serve client requests over the Postgres wire protocol (psycopg2, etc.)
stackql srv --auth="${AUTH}"
Contributions are welcome and encouraged. For more information on how to contribute, please see our contributing guide.
License
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.
