StackQL

An MCP server and CLI that lets an agent query and provision cloud, SaaS and API resources with plain SQL

MCP serverOfficial

High risk

We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.

Why this level

  • Can create and change real cloud resources
  • Handles provider credentials
All reasons and checks

stackql/stackql

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/stackql

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

This entry is high risk, so there is no one-click install. Review the code and add the config by hand.

Run in a terminal

claude mcp add --transport stdio stackql -- npx -y @stackql/mcp-server

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "stackql": {
      "command": "npx",
      "args": [
        "-y",
        "@stackql/mcp-server"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "stackql": {
      "command": "npx",
      "args": [
        "-y",
        "@stackql/mcp-server"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Run in a terminal

code --add-mcp '{"name":"stackql","type":"stdio","command":"npx","args":["-y","@stackql/mcp-server"]}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "stackql": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@stackql/mcp-server"
      ]
    }
  }
}

If the file already exists, add the server inside the servers key.

Run in a terminal

codex mcp add stackql -- npx -y @stackql/mcp-server

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.stackql]
command = "npx"
args = ["-y", "@stackql/mcp-server"]

If the file already exists, append the block to the end.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "stackql": {
      "command": "npx",
      "args": [
        "-y",
        "@stackql/mcp-server"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "stackql": {
      "command": "npx",
      "args": [
        "-y",
        "@stackql/mcp-server"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "stackql": {
      "command": "npx",
      "args": [
        "-y",
        "@stackql/mcp-server"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "stackql": {
      "command": "npx",
      "args": [
        "-y",
        "@stackql/mcp-server"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "stackql": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@stackql/mcp-server"
      ]
    }
  }
}

If the file already exists, add the server inside the mcp key.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "stackql": {
      "command": "npx",
      "args": [
        "-y",
        "@stackql/mcp-server"
      ]
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "stackql": {
      "command": "npx",
      "args": [
        "-y",
        "@stackql/mcp-server"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 3c7afc1.

Text for your agent

Add the MCP server: npx -y @stackql/mcp-server. The user sets cloud provider credentials via environment variables.

Other ways from the author
npx -y @stackql/mcp-server

The package downloads the signed stackql binary on first run.

This is third-party code. Review the repository files before installing.

What it does

StackQL exposes cloud and SaaS providers as tables you query with SQL: SELECT to inventory resources, INSERT and other operations to create and change them. The MCP server hands this to an agent, so it can build infrastructure reports, find config problems and provision resources through one language. The npm package downloads the signed stackql binary on first run and speaks stdio. Providers come from a separate registry, and cloud auth uses each provider's usual environment variables. Besides MCP, the project ships a CLI and is packaged as a Codex plugin.

Who it is for. For infrastructure engineers and developers who want one way to read and change cloud resources from an agent.

Good fit when

  • You need to inventory resources across several clouds
  • You need to check configuration against rules
  • You want to provision resources with a SQL query from an agent

Not a fit when

  • You have no cloud credentials for the needed providers
  • The task is simpler with the cloud's own CLI

Example request

Use stackql to list all running virtual machines in the project and their public addresses

Limitations

The server itself needs no key, but querying providers requires their credentials via environment variables, and some operations change real resources. Providers come from a registry, so coverage depends on it. On first run the npm package downloads the stackql binary.

How to disable. Remove the stackql server from your MCP config or uninstall the @stackql/mcp-server package.

MCP

Transport
stdio
Authentication
not required
Environment variables
Environment variables
PROVIDER_CREDENTIALS
secret
Cloud and SaaS provider credentials via their usual environment variables, depending on the provider

Security check

  • Can create and change real cloud resources
  • Handles provider credentials

README in short

The README describes StackQL as a SQL engine for cloud, SaaS and APIs, for both humans and agents. It shows binary installs across operating systems, Docker usage and MCP setup. Providers come from a separate registry, with GitHub Actions and Jupyter integrations. The MCP server is packaged for npm and PyPI, plus a Codex plugin. MIT licensed.

FAQ

Does the server itself need a key?

No, but calling clouds needs their credentials, usually the same environment variables as the native CLIs.

Can it change resources, not just read?

Yes, StackQL supports not only SELECT but also create and change operations.

Editors’ pick

An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant

MCP serverMedium riskNo VPN needed80.7KRepository stars
Editors’ pick

GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent

MCP serverHigh risk33.3KRepository stars

Agent Skills for Google products

Agent Skills for Google products and technologies

Editors’ pick

Official Google skill collection for working with Google Cloud, BigQuery, GKE, ads and analytics from an agent

SkillHigh risk20.5KRepository stars
Official

AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring

MCP serverHigh risk9.7KRepository stars
Foxx AIStackQL

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.