What runtime dependencies does Stackql require?
Stackql is delivered as a single signed binary with no runtime dependencies.
@stackql
Basic information
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.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"stackql": {
"command": "npx",
"args": [
"-y",
"@stackql/mcp-server"
]
}
}
}Full 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.
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.
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.
Stackql is delivered as a single signed binary with no runtime dependencies.
Stackql supports AWS, Azure, Google, GitHub, Databricks, Okta, and other providers available through the StackQL provider registry.
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.
Provider credentials are passed via StackQL's standard `--auth` flag or environment variables. The `github` provider works without credentials for public data.
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.

Couples therapist Figs O'Sullivan (LMFT, 17 years, endorsed by Sue Johnson, creator of EFT) inside your AI. Ask relationship questions answered from his clinical writing, name the pattern in a fight, get a three-step rep
This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,

Yuppsy MCP: build and publish real estate websites from your AI assistant. Yuppsy lets your AI assistant create live websites for real estate agents and individual property listings. You don't need a designer or any code
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
PickFu MCP is a Model Context Protocol (MCP) server that connects AI assistants, developers, marketers, product managers, and AI agents to PickFu's consumer research platform. It enables users to create surveys, conduct
Comments