steampipe-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| steampipe_queryA | Query cloud infrastructure, SaaS, APIs, code and more with SQL. Queries are read-only and must use PostgreSQL syntax. For best performance: limit columns requested, use materialized CTEs instead of joins. Trust the search path unless sure you need to specify a schema. Check available tables and columns before querying using steampipe_table_list and steampipe_table_show. |
| steampipe_table_listB | List all available Steampipe tables. Use schema and filter parameters to narrow down results. |
| steampipe_table_showB | Get detailed information about a specific Steampipe table, including column definitions, data types, and descriptions. |
| steampipe_plugin_listA | List all Steampipe plugins installed on the system. Plugins provide access to different data sources like AWS, GCP, or Azure. |
| steampipe_plugin_showA | Get details for a specific Steampipe plugin installation, including version, memory limits, and configuration. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| best_practices | Best practices for writing Steampipe SQL queries |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| status | Get the current status of the Steampipe connection |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: listing plugins vs. showing plugin details vs. executing queries vs. listing tables vs. showing table details. The descriptions reinforce these distinctions, making misselection unlikely.
All tools follow a consistent 'steampipe_' prefix with a clear verb_noun pattern (plugin_list, plugin_show, query, table_list, table_show). This uniformity makes the tool set predictable and easy to navigate.
Five tools is well-scoped for the server's purpose of interacting with Steampipe. It covers plugin management, query execution, and table metadata without being overly sparse or bloated, with each tool earning its place.
The tool set provides strong coverage for querying and exploring Steampipe data, including plugin and table metadata. A minor gap exists in lacking direct plugin installation or configuration management tools, but agents can work around this using existing query capabilities.