Stackql
@stackql
About Stackql
Open source SQL-native query and provisioning engine for cloud and SaaS infrastructure. Ships as a single signed binary with MCP tools for provider discovery, schema exploration, queries, and lifecycle operations.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"stackql": {
"command": "npx",
"args": [
"-y",
"@stackql/mcp-server"
]
}
}
}Tools
16Full I/O contract for one method. Requires provider, service, resource, method.
Output fields for a resource's primary read method. Requires provider, service, resource.
Access methods (HTTP operations) for a resource. Call before writing any query. Requires provider, service, resource.
Available cloud/SaaS providers (top of the hierarchy). No inputs.
Providers (and their versions) available in the configured registry. Distinct from list_providers, which lists only providers already pulled. Optional provider arg lists versions for that provider.
Resources under a provider.service. Requires provider and service.
Services under a provider. Requires provider.
Install a single provider from the registry into the local approot cache. Requires provider; version is optional (latest published is pulled when empty). Writes only local cache state; no cloud control/data plane effect.
Retrieve a query library entry by id. Without params: returns the raw template, param declarations and notes (adapt from it when no exact match exists). With params: the server validates values and returns rendered SQL plus which tool to execute it with (run_select_query or run_mutation_query). Read-only, no credentials.
Search the curated StackQL query library by natural-language intent. Returns ranked template ids with required param names. Consult this before composing SQL from scratch; follow up with query_library_get. Read-only, no credentials.
Re-source provider credentials from the server's configured env file into the process environment, then report per-provider credential resolution status. Call after fixing or rotating credentials (eg a query failed with a credential resolution error), then retry the query. Never returns secret values. Optional provider arg scopes the report.
Execute a stackql EXEC lifecycle operation. Returns {messages, timestamp}. Gated by server mode.
Execute INSERT/UPDATE/REPLACE/DELETE against the provider. Real side effects. Returns {messages, timestamp}. Gated by server mode. Consult query_library_search for a vetted template before composing SQL from scratch; when the SQL came from a library entry, pass its id as source.
Execute a SELECT. Returns {rows}. Reads only. Consult query_library_search for a vetted template before composing SQL from scratch; when the SQL came from a library entry, pass its id as source.
Get server identity and runtime: stackql version, backing SQL engine, provider registry location, mode, read-only flag. Call once at session start.
Parse and plan a SELECT without executing. Returns {valid, errors}. SELECT only.
Overview
What is Stackql?
Stackql is an open-source, SQL-native query and provisioning engine for cloud and SaaS infrastructure. The MCP server exposes StackQL's provider registry and query engine as MCP tools, letting agents discover providers, explore schemas, and run live SQL queries against AWS, Azure, Google, GitHub, Databricks, Okta, and other providers through a single signed binary with no runtime dependencies.
How to use Stackql?
Install via the prebuilt MCP Bundle from the latest release for one-click setup in Claude Desktop, or manually with the stackql binary using the server config and an --approot setting. Provider credentials are passed via StackQL's --auth flag or environment variables.
Key features of Stackql
- Open-source SQL-native query and provisioning engine
- Single signed binary with no runtime dependencies
- Discover and install providers from the StackQL registry
- Explore provider schemas with service and resource tools
- Run live SQL queries against cloud and SaaS APIs
- Provision and lifecycle operations gated by server mode
Use cases of Stackql
- Query cloud and SaaS infrastructure across providers using SQL
- Discover and explore provider schemas and available resources
- Validate and run SQL queries before execution against live APIs
- Perform provisioning and lifecycle operations on cloud resources
FAQ from Stackql
What runtime dependencies does Stackql require?
Stackql is delivered as a single signed binary with no runtime dependencies.
What providers does Stackql support?
Stackql supports AWS, Azure, Google, GitHub, Databricks, Okta, and other providers available through the StackQL provider registry.
How do I install Stackql on Claude Desktop?
Download the prebuilt MCP Bundle (stackql-mcp-<platform>.mcpb) from the latest release, then go to Settings -> Extensions -> Install Extension. No separate StackQL install is needed.
How does authentication work?
Provider credentials are passed via StackQL's standard --auth flag or environment variables. The github provider works without credentials for public data.
What transport does Stackql use?
Stackql uses the stdio transport and works with any stdio-based MCP client. A server config with --approot and audit settings is required for manual installations.
Frequently asked questions
What runtime dependencies does Stackql require?
Stackql is delivered as a single signed binary with no runtime dependencies.
What providers does Stackql support?
Stackql supports AWS, Azure, Google, GitHub, Databricks, Okta, and other providers available through the StackQL provider registry.
How do I install Stackql on Claude Desktop?
Download the prebuilt MCP Bundle (`stackql-mcp-<platform>.mcpb`) from the latest release, then go to Settings -> Extensions -> Install Extension. No separate StackQL install is needed.
How does authentication work?
Provider credentials are passed via StackQL's standard `--auth` flag or environment variables. The `github` provider works without credentials for public data.
What transport does Stackql use?
Stackql uses the stdio transport and works with any stdio-based MCP client. A server config with `--approot` and audit settings is required for manual installations.
Basic information
More Other MCP servers
Awesome Mlops
visengerA curated list of references for MLOps
Codelf
unbugA search tool helps dev to solve the naming things problem.
Activepieces
activepiecesAI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
Glasswarp
GlasswarpSee and control a real Windows PC you own — from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.
IDA Pro MCP
mrexodiaAI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Comments