Steampipe Model Context Protocol (MCP) Server

Created By
turbota year ago
Enable AI assistants to explore and query your Steampipe data!
Overview

What is Steampipe Model Context Protocol (MCP) Server?

The Steampipe MCP Server enables AI assistants to explore and query your Steampipe data, facilitating natural language exploration and analysis of cloud infrastructure data.

How to use Steampipe MCP?

To use the Steampipe MCP, install the required prerequisites, configure your AI assistant with the MCP server settings, and start querying your cloud infrastructure using natural language.

Key features of Steampipe MCP?

  • Connects AI assistants to cloud infrastructure data.
  • Supports queries across AWS, Azure, GCP, and over 100 cloud services.
  • Provides security and compliance analysis.
  • Assists in cost and resource optimization.
  • Offers query development assistance.

Use cases of Steampipe MCP?

  1. Querying cloud resources like EC2 instances and S3 buckets.
  2. Conducting security analysis on IAM users and access keys.
  3. Generating compliance reports for cloud resources.
  4. Exploring potential risks in cloud infrastructure.

FAQ from Steampipe MCP?

  • What AI assistants are compatible with Steampipe MCP?

The MCP server works with various AI assistants, including Claude and Cursor.

  • Is there a cost associated with using Steampipe MCP?

Steampipe MCP is open-source and free to use under the Apache 2.0 license.

  • What are the prerequisites for installation?

You need Node.js v16 or higher and a running Steampipe installation or a Turbot Pipes workspace.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
turbot
Star
11
Language
TypeScript
License
Apache-2.0 license
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

38 minutes ago