Query, provision and deprovision cloud and SaaS resources with SQL. The plugin
runs the StackQL MCP server as a local process on your computer and connects
ChatGPT or Codex to it over stdio: discover providers, services, resources and
method contracts, run SELECT queries against live provider APIs, validate a
query before running it, and change resources with INSERT, UPDATE, DELETE and
lifecycle EXEC operations. The bundled stackql-setup skill walks through
credentials and a first query.
The MCP server is a local process, so the plugin is desktop only: it installs from the ChatGPT desktop app and works in threads that run on your computer, and in Codex CLI. ChatGPT on the web cannot start local servers. A ChatGPT desktop Chat session can start the server and still not expose its tools (openai/codex#38162); Codex threads are unaffected.
Node.js 24.22.1 or later (22.23.4 or 26.12.1 on those release lines; these are the October 2026 Node.js security releases), and network access to GitHub releases and the StackQL provider registry on first use.
- Runs:
server/bin/stackql-mcp.jswith Node.js. It starts the StackQL binary asstackql mcp --mcp.server.type=stdiowith the configuration directory below as the application root and the audit log disabled. - Fetches, on first use only: the StackQL release bundle for your platform
from
releases.stackql.io(a proxy in front of the GitHub release assets), verified against the SHA-256 pinned inserver/platforms.jsonand cached under~/.stackql/mcp-server-bin. Provider definitions are downloaded from the StackQL provider registry the first time a provider is pulled. - Sends: your queries go from your machine straight to the cloud or SaaS provider APIs you query, authenticated with the credentials in your StackQL environment file. Nothing is sent to StackQL Studios. The binary and the server carry no telemetry.
Provider credentials live in ~/.stackql/.env (%USERPROFILE%\.stackql\.env
on Windows), created empty on first start. Providers use their standard
environment variable names, for example AWS_ACCESS_KEY_ID and
AWS_SECRET_ACCESS_KEY. After editing the file, ask the assistant to call
reload_credentials; it reports resolution status by variable name and never
returns a value. Set STACKQL_PLUGIN_CONFIG_DIR to use a different directory.
The server starts in safe mode: SELECT queries run freely, and INSERT,
UPDATE, DELETE and EXEC ask for approval before they run. Read-only tools are
annotated readOnlyHint and mutating tools destructiveHint.
- Documentation: https://stackql.io/getting-started
- Source: https://github.com/stackql/stackql
- Privacy policy: https://stackql.io/privacy
- Support: https://stackql.io/support