mcp-steampipe
This server acts as an MCP bridge that enables AI models to query and retrieve data from various cloud services, APIs, and infrastructure through Steampipe's SQL interface.
Core Capabilities:
Execute SQL queries against Steampipe's unified data layer using the
run_steampipe_querytoolAccess configured data sources including cloud providers (AWS, Azure, GCP), SaaS platforms (GitHub, Slack, Jira, Salesforce), and APIs
Retrieve structured data as JSON for AI processing and analysis
Perform analytics and reporting with aggregations, joins, and complex queries across different sources
Integration with MCP-compatible AI assistants like Claude for conversational infrastructure access
Example Use Cases:
Query GitHub repositories, issues, and pull requests using SQL syntax
Investigate security configurations and compliance across multi-cloud environments
Automate data discovery through natural language requests
Generate reports on resource usage, costs, or cloud infrastructure
Provides access to GitHub repository data through Steampipe, allowing queries for repository information such as names and fork counts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-steampipe show me my top 5 GitHub repositories by stars"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Steampipe MCP
This is a simple steampipe MCP server. This acts as a bridge between your AI model and Steampipe tool.
Pre-requisites
Python 3.10+ installed.
uv installed (my fav) and mcp[cli]
Steampipe installed and working.
Steampipe plugin configured (e.g., github) with necessary credentials (e.g., token in ~/.steampipe/config/github.spc).
Any LLM supporting MCP. I am using Claude Here.
Node.js and npx installed (required for the MCP Inspector and potentially for running some MCP servers).
Related MCP server: mcp-mssql-server
Running MCP Interceptor
This is an awesome tool for testing your if your MCP server is working as expected
Running the Interceptor
npx -y @modelcontextprotocol/inspector uv --directory . run steampipe_mcp_server.py
A browser window should open with the MCP Inspector UI (usually at http://localhost:XXXX).
Wait for the "Connected" status on the left panel.
Go to the Tools tab.
You should see the run_steampipe_query tool listed with its description.
Click on the tool name.
In the "Arguments" JSON input field, enter a valid Steampipe query:
{
"query": "select name, fork_count from github_my_repository "
}execute and view the json results
Running the tool
Pretty straightforward. Just run the interceptor and make sure the tool is working from the directory. Then add the server configuration to the respective LLM and select the tool from the LLM.
TroubleShooting
If the tool is not found in the interceptor then that means @mcp.tool() decorator has some issue.
Execution error - Look at the "Result" in the Inspector and the server logs (stderr) in your terminal. Did Steampipe run? Was there a SQL error? A timeout? A JSON parsing error? Adjust the Python script accordingly.
tail -f ~/Library/Logs/Claude/mcp.log
tail -f ~/Library/Logs/Claude/mcp-server-steampipe.logSecurity Risk Claude blindly executes your sql query in this POC so there is possibility to generate and execute arbitary SQL Queries via Steampipe using your configured credentials.
Available Tools
1 toolrun_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.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Query your warehouse or a CSV with Claude/ChatGPT over MCP, governed by table-level ACL + audit.
Read and write NetSuite and run SuiteQL from Claude or ChatGPT. Write tools flagged for approval.
Hosted PostgreSQL MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables interaction with SQLite databases, filesystem, AWS IAM, and Gmail through a master MCP server with a Streamlit UI optimized for Claude.1-
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code and other MCP clients to interact with Microsoft SQL Server databases through standardized tools for query execution, schema exploration, table management, and stored procedure execution.90 npm1MIT
- AlicenseAqualityCmaintenanceExposes PostgreSQL query execution, EXPLAIN, and schema inspection tools to MCP-compatible clients like Claude Desktop.31MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to query a Postgres analytics schema via a read-only MCP server, with tools auto-generated from live database introspection and configurable SQL queries defined in YAML.MIT