Server facts
stackql MCP Server
Project
- Author
- stackql
- Repository
- github.com/stackql/stackql
- License
- Not specified
- Category
- Cloud & DevOps
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 1,070
- Last commit
- Data as of
Tags
- Devops
- Sql
- agentic platform engineering
- cloud
- database
- infrastructure
- multicloud
Overview
AWS, Azure, Google, GitHub, Databricks, and Okta are among the providers accessible through StackQL's SQL engine. Agents can distinguish providers already pulled locally from those available in the configured registry and inspect available versions. Pulling a provider updates the local cache without changing cloud resources. Schema tools expose services, resources, fields returned by primary read methods, and method input and output contracts.
For SQL preparation, query_library_search finds templates by natural-language intent, while query_library_get returns a template or renders SQL from validated parameters. SELECT statements can be parsed and planned without execution, then run to retrieve rows. Mutations and EXEC lifecycle operations are controlled by server mode; mutations have real provider-side effects. Credential reloads read the configured environment file and report resolution status without exposing secret values. The server uses stdio and is distributed as a signed binary without runtime dependencies.
stackql setup notes
- stackql records stdio only; confirm a network transport upstream before planning remote access.
- stackql has no recorded license; confirm reuse terms in its repository.