StackQL MCP Server
SQL-native query and provisioning engine for cloud infrastructure, served over MCP via 'stackql mcp'. Multiplatform bundle: contains the darwin, linux and windows binaries; the host selects via platform_overrides.
- Category
- Developer Tools
- Primary Subcategory
- Pending
Integration details
Description
SQL-native query and provisioning engine for cloud infrastructure, served over MCP via 'stackql mcp'. Multiplatform bundle: contains the darwin, linux and windows binaries; the host selects via platform_overrides.
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- StackQL
- Access
- Unknown
- First tracked
- 2026-06-24
- Tool count
- 0
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Get alerts for StackQL MCP Server
Get updates when StackQL MCP Server’s Discoverability Score or category rank changes.
Claude Discoverability Score
StackQL MCP Server isn’t discoverable through Claude’s Connector picker
It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What the current score measures

Remote Connectors Claude can surface from the Connector picker.
Competitive lineup
0 tools agents can invoke
No tools are exposed by this Claude Connector in the latest snapshot.
How do I improve a Verified connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.