Best for
- Teams needing a unified SQL interface across cloud and SaaS providers
- Users who want AI agents to access cloud resources in a structured way
- Cloud operations, security, FinOps, and infrastructure-as-code workflows
S
StackQL MCP Server
Official
Query and provision cloud infrastructure with SQL.
GitHub source repository ↗
55FMRS · C
The source identifies this as a StackQL-maintained server using stdio transport, distributed through npm, PyPI, Docker, GitHub Actions, and .mcpb bundles. It is suited to SQL-based querying and provisioning of cloud and SaaS resources; named tools, exact authentication scopes, and complete client compatibility are not specified in the source.
StackQL MCP Server is StackQL’s SQL-native engine for querying and provisioning cloud infrastructure over MCP. It serves more than 40 cloud and SaaS providers by transpiling SQL statements into provider API requests for querying, creating, modifying, and operating resources.
Tools
The tool list has not been reviewed yet.
Setup
Configure an MCP-capable client with command set to npx and args set to -y and @stackql/mcp-server. Alternative distribution methods include PyPI, Docker, GitHub Actions, and platform-specific .mcpb bundles. Refer to StackQL documentation for client configuration, authentication, and server modes.
claude_desktop_config.json
{"mcpServers":{"stackql":{"command":"npx","args":["-y","@stackql/mcp-server"]}}}
Fit and risk
Not for
- Users who only need local file or browser automation
- Environments that cannot grant cloud or SaaS API access
- Users expecting a tool inventory with individually named MCP tools, which the source does not provide
Required permissions
- Provider authentication must be supplied through --auth or the client configuration
- Effective permissions depend on the provider credentials and requested operations; the server supports querying and provisioning
- GitHub Actions defaults to read_only mode, which is intended as the safe CI default
Risks and side effects
- Provisioning or modifying resources can cause real infrastructure changes
- Overprivileged credentials can broaden the impact across cloud or SaaS resources
- AI-generated SQL or API operations should be reviewed before execution
- Cross-cloud operations may create cost, compliance, and security consequences
Troubleshooting
- Verify that the client supports MCP over stdio
- Confirm that npx, the PyPI package, Docker, or the relevant platform bundle is available
- Check authentication parameters and provider credential permissions
- Validate connectivity with read-only or query operations before provisioning
- Consult StackQL documentation for client configuration, authentication, and server modes
Use cases
Query cloud and SaaS resources with SQL
Manage cross-cloud assets and perform security audits
Let AI agents query or provision infrastructure through MCP
Automate infrastructure provisioning and compliance checks with GitHub Actions
Supported clients
ClaudePartial support
VS CodePartial support
CursorPartial support