mcp-steampipe
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 |
|---|---|
| run_steampipe_queryB | Executes a SQL query using the Steampipe CLI and returns the results as a JSON string. Args: query: The SQL query to execute via Steampipe (e.g., "select login from github_user limit 1"). Ensure the query is valid Steampipe SQL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The naming follows a clear verb_noun pattern (run_steampipe_query).
A single tool is too few for most practical purposes, as it severely limits the server's functionality and flexibility. While it might cover the basic query execution, it lacks any supporting operations like listing available tables, checking query status, or managing connections.
The server is severely incomplete for interacting with Steampipe. It only provides query execution, missing essential operations such as listing available plugins/tables, describing table schemas, managing connections, or handling query errors and metadata. This will cause significant agent failures in complex workflows.