stackql-mcp-server
mcp-name: io.github.stackql/stackql-mcp
uvx/pip-able launcher for the StackQL MCP server - a SQL-native query and provisioning engine for cloud and SaaS infrastructure (AWS, Azure, Google, GitHub, Databricks, and other providers), served over the Model Context Protocol.
On first run, the launcher downloads the signed stackql binary for your
platform from the matching GitHub release (sha256-verified against pins baked
into this package), caches it under ~/.stackql/mcp-server-bin/, and starts
it as an MCP stdio server. Subsequent runs start instantly from the cache.
Pure stdlib - no dependencies.
Usage
With any MCP client that supports stdio servers:
{
"mcpServers": {
"stackql": {
"command": "uvx",
"args": ["stackql-mcp-server"]
}
}
}
Provider credentials are passed through with stackql's standard --auth flag:
{
"mcpServers": {
"stackql": {
"command": "uvx",
"args": [
"stackql-mcp-server",
"--auth={\"github\":{\"type\":\"null_auth\"}}"
]
}
}
}
Or install it: pip install stackql-mcp-server, then use stackql-mcp as the
command. Any extra arguments are passed to stackql after the standard MCP
server arguments. The launcher sets --approot to ~/.stackql and disables
the audit file sink by default; pass your own --approot or --mcp.config
to override (later flags win).
Environment overrides
STACKQL_MCP_BIN- path to an existingstackqlbinary; skips the download.STACKQL_MCP_BUNDLE- path to a local.mcpbbundle to extract the binary from (testing; skips download and sha verification).
Other installation vectors
- Claude Desktop one-click bundles (
.mcpb): https://github.com/stackql/stackql/releases/latest - npm:
npx -y @stackql/mcp-server - Docker:
docker run -i --rm stackql/stackql-mcp - Native installers and package managers: https://stackql.io/docs/installing-stackql
Links
- Docs: https://stackql.io/docs
- MCP Registry:
io.github.stackql/stackql-mcp - Source: https://github.com/stackql/stackql
Metadata
Release files for stackql-mcp-server 0.12.824
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| stackql_mcp_server-0.12.824.tar.gz | 4.2 kB | Without provenance | Details for stackql_mcp_server-0.12.824.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| stackql_mcp_server-0.12.824-py3-none-any.whl | Python 3 | none | any | Details for stackql_mcp_server-0.12.824-py3-none-any.whl |
Total release size: 9.4 kB
Release files / stackql_mcp_server-0.12.824.tar.gz
| Download URL | stackql_mcp_server-0.12.824.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e0fd102d866107e23234572e3c9a787958b9ed92c7b54bf713216cd3e67e039
|
|
BLAKE2b-256 checksum How to use checksums |
11d324a8f02e1472a89a6fbd34b3114c34b046bdfbf01c111154ce35880786e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / stackql_mcp_server-0.12.824-py3-none-any.whl
| Download URL | stackql_mcp_server-0.12.824-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e833899a47446f54eb7a9c1d09fc99b591d39230cc00cb67a8343f7946136b9b
|
|
BLAKE2b-256 checksum How to use checksums |
e8b5ed12f55055919d5ae1e66bbdf813a2b2397a3d8b9923d156349616997092
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for stackql-mcp-server 0.12.824
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.