Developer · Local MCP server
StackQL MCP Server
SQL-native query and provisioning engine for cloud infrastructure, served over MCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.stackql/stackql-mcp- Version
- 0.12.732
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- MCP Bundle (.mcpb), OCI image (Docker), npm
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- stackql (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/stackql) · how
- Website
- stackql.io
- Repository
- github.com/stackql/stackql
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| MCP Bundle (.mcpb) | https://github.com/stackql/stackql/releases/download/v0.12.732/stackql-mcp-linux-x64.mcpbSHA-256 checksum stated | 0.12.732 | stdio |
| MCP Bundle (.mcpb) | https://github.com/stackql/stackql/releases/download/v0.12.732/stackql-mcp-linux-arm64.mcpbSHA-256 checksum stated | 0.12.732 | stdio |
| MCP Bundle (.mcpb) | https://github.com/stackql/stackql/releases/download/v0.12.732/stackql-mcp-windows-x64.mcpbSHA-256 checksum stated | 0.12.732 | stdio |
| MCP Bundle (.mcpb) | https://github.com/stackql/stackql/releases/download/v0.12.732/stackql-mcp-darwin-universal.mcpbSHA-256 checksum stated | 0.12.732 | stdio |
| OCI image (Docker) | docker.io/stackql/stackql-mcp:0.12.732 | - | stdio |
| npm | @stackql/mcp-server | 0.12.732 | stdio |
How to connect StackQL MCP Server
StackQL MCP Server runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/stackql/stackql/releases/download/v0.12.732/stackql-mcp-linux-x64.mcpb version 0.12.732. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
StackQL MCP Server runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/stackql/stackql/releases/download/v0.12.732/stackql-mcp-linux-arm64.mcpb version 0.12.732. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
StackQL MCP Server runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/stackql/stackql/releases/download/v0.12.732/stackql-mcp-windows-x64.mcpb version 0.12.732. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
StackQL MCP Server runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/stackql/stackql/releases/download/v0.12.732/stackql-mcp-darwin-universal.mcpb version 0.12.732. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
StackQL MCP Server runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/stackql/stackql-mcp:0.12.732. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm docker.io/stackql/stackql-mcp:0.12.732.
StackQL MCP Server runs locally from a Node.js package published to the npm registry: @stackql/mcp-server version 0.12.732. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @stackql/mcp-server@0.12.732.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"stackql-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/stackql/stackql-mcp:0.12.732"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| StablecoinXDrive a StablecoinX business account - auth, API keys, sessions, paymaster policy, webhooks. | Local · stdio |
| StackfactsNeutral, sourced, dated facts for choosing software: price, free tier, idle rules, security record. | Remote · HTTPLive check: ✓ handshake |
| StackhawkAn MCP server that provides interaction with StackHawk's security scanning platform. | Local · stdio |
| StackMapSearch 344 human-reviewed AI/agent repos and the 817 typed connections between them. | Local · stdio |
| StackShieldExternal security monitoring for Laravel apps: list domains, trigger scans, read issues and fixes. | Remote · HTTPLive check: sign-in required |
| StackWitnessIndependent monitoring: status, monitors, and incidents from your StackWitness workspace. | Remote · HTTPLive check: sign-in required |
| StallhuntEvidence-backed Linux performance triage over MCP. | Local · stdio |
| StandoutAnti-slop design taste for AI coding agents: art directions, section code, 0-100 page critic. | Remote · HTTPLive check: ✓ handshake |