Stackql

by stackql

354 downloads

Not rated

GitHub

About

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.

Details

Author: stackql
Downloads: 354
Categories: Other, Cloud Service, Infrastructure, Database

- 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

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name Stackql

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

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

JSON

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

JSON

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

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

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

JSON

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

JSON

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

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

From the repository

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.

`describe_method`

Full I/O contract for one method. Requires provider, service, resource, method.

`describe_resource`

Output fields for a resource's primary read method. Requires provider, service, resource.

`list_methods`

Access methods (HTTP operations) for a resource. Call before writing any query. Requires provider, service, resource.

`list_providers`

Available cloud/SaaS providers (top of the hierarchy). No inputs.

`list_registry`

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.

`list_resources`

Resources under a provider.service. Requires provider and service.

`list_services`

Services under a provider. Requires provider.

`pull_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.

`query_library_get`

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.

`query_library_search`

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.

`reload_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.

`run_lifecycle_operation`

Execute a stackql EXEC lifecycle operation. Returns {messages, timestamp}. Gated by server mode.

`run_mutation_query`

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.

`run_select_query`

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.

`server_info`

Get server identity and runtime: stackql version, backing SQL engine, provider registry location, mode, read-only flag. Call once at session start.

`validate_select_query`

Parse and plan a SELECT without executing. Returns {valid, errors}. SELECT only.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

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

McpServers

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

StackQL MCP Server

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 - all through a single signed binary with no runtime dependencies.

Tools

- list_providers, pull_provider, list_registry - discover and install providers from the StackQL registry - list_services, list_resources, describe_resource, list_methods, describe_method - explore provider schemas - run_select_query, validate_select_query - live SQL queries against cloud APIs - run_mutation_query, run_lifecycle_operation - provisioning and lifecycle operations (gated by server mode) - server_info - server and registry status

Install (Claude Desktop - one-click)

Download the prebuilt MCP Bundle for your platform from the latest release - stackql-mcp-<platform>.mcpb - then Settings -> Extensions -> Install Extension. No separate StackQL install needed. Each bundle has a .sha256 alongside it.

Install (manual, any stdio MCP client)

With the stackql binary installed, use the server config shown above. Replace /Users/yourname with your home directory. The --approot and audit settings matter: some MCP clients launch servers with an unwritable working directory.

Authentication

Provider credentials are passed via StackQL's standard --auth flag or environment variables - see the provider docs. The github provider works without credentials for public data.

Links

- Website: https://stackql.io - Docs: https://stackql.io/docs - Official MCP Registry: io.github.stackql/stackql-mcp - Source: https://github.com/stackql/stackql

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

describe_method

describe_resource

list_methods

list_providers

list_registry

list_resources

list_services

pull_provider

query_library_get

query_library_search

reload_credentials

run_lifecycle_operation

run_mutation_query

run_select_query

server_info

validate_select_query

Claude Desktop / Cursor

McpServers

StackQL MCP Server

Tools

Install (Claude Desktop - one-click)

Install (manual, any stdio MCP client)

Authentication

Links

Install

More like this

Sequential Thinking

Aws Kb Retrieval Server

Filesystem

EverArt

Google Drive

Reactive Resume

`describe_method`

`describe_resource`

`list_methods`

`list_providers`

`list_registry`

`list_resources`

`list_services`

`pull_provider`

`query_library_get`

`query_library_search`

`reload_credentials`

`run_lifecycle_operation`

`run_mutation_query`

`run_select_query`

`server_info`

`validate_select_query`