MCP100 verdict
Not currently recommended. Mature cloud-control MCP with unusually strong safety controls, but full cloud infrastructure mutation remains too consequential for Selected.
MCP100 Assessment
Editorial verdict
Reviewed September 11, 2026
Task Fit
Mapped
Cloud operations
Trust
Status warning
Editorial trust review has not been completed.
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals unavailable
No independently comparable adoption metric is currently stored.
Evidence scope
No MCP-specific repository metric is stored
No MCP-specific package metric is stored
Stars observation date unavailable · Downloads observation date unavailable
Publisher activity observed September 11, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed September 11, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
No sufficient client-specific setup evidence has been stored from the publisher or client documentation.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-09-11T00:00:00.000Z
Type-appropriate, source-backed setup for this mcp server profile.
Loading optional publisher installation details…
Use the signed MCP bundle / connector, Docker image, or stackql mcp command.Capability
Mature cloud-control MCP with unusually strong safety controls, but full cloud infrastructure mutation remains too consequential for Selected.
Discover providers, services, resources, methods, and server status.
Validate and execute SELECT-style StackQL queries.
Run mutating or lifecycle operations when server mode permits.
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
Reviewed access
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
Related reviewed MCPs
Connect agents to Azure resources and more than forty Azure services.
Choose this instead if
Choose Azure MCP Server instead if discovering and inspecting resources across supported Azure services.
Connect agents to Azure resources and more than forty Azure services.
Access supported Cloudflare developer platform capabilities.
Choose this instead if
Choose Cloudflare MCP instead if searching and executing supported Cloudflare API operations across Workers, DNS, R2, Zero Trust, and related products.
Access supported Cloudflare developer platform capabilities.
Investigate and manage Buildkite pipelines, builds, jobs, logs, artifacts, and test data.
Choose this instead if
Choose buildkite instead if cI/CD investigation and controlled Buildkite operations through hosted or self-managed MCP transports.
Investigate and manage Buildkite pipelines, builds, jobs, logs, artifacts, and test data.
StackQL Studios is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
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.
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.
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 --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:
{
"mcpServers": {
"stackql": {
"command": "npx",
"args": ["-y", "@stackql/mcp-server"]
}
}
}
{
"mcpServers": {
"stackql": {
"command": "uvx",
"args": ["stackql-mcp-server"]
}
}
}
{
"mcpServers": {
"stackql": {
"command": "docker",
"args": ["run", "-i", "--rm", "stackql/stackql-mcp"]
}
}
}
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.
- uses: stackql/setup-stackql-mcp@v1
with:
mode: read_only
For client-specific setup, authentication and server modes, see the full MCP install and usage docs.
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
# run interactive stackql queries
stackql shell --auth="${AUTH}"
Execute a statement or file
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,tableandtextare available for theexeccommand using the--outputflag
ℹ️ StackQL supports passing parameters using
jsonnetorjson, see Using Variables
Server
# serve client requests over the Postgres wire protocol (psycopg2, etc.)
stackql srv --auth="${AUTH}"
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.
From the publisher README
Original client setup and configuration retained from the publisher documentation.
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][dockerhub]. Images available include [
stackql][dockerstackql], [stackql-jupyter-demo][dockerjupyter] and more. Pull the latest StackQL base image using:
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.
Use StackQL in your GitHub Actions workflows to automate cloud infrastructure provisioning, IaC assurance, or compliance/security. Available GitHub Actions include: [
setup-stackql][setupaction], [stackql-exec][execaction] and more