Skip to main content
Glama
turbot

steampipe-mcp

by turbot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to steampipe-mcp

No user-submitted related servers found.

    Related Servers

    • Turbot Guardrails MCP Server by turbot

      Turbot Guardrails MCP Serverofficial

      turbot
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to Turbot Guardrails for natural language exploration, analysis, and automation of cloud governance.
      11 npm
      4
      Apache 2.0

    • Qora

      suveshmoza
      A
      license
      A
      quality
      B
      maintenance
      Lets AI assistants like Cursor and Claude safely explore your database and answer questions about your data in plain English.
      4
      1
      MIT
    • tailpipe-mcp by turbot

      tailpipe-mcpofficial

      turbot
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to cloud and SaaS logs via Tailpipe, enabling natural language querying and analysis of log data.
      12 npm
      7
      Apache 2.0
    • GraphJin by dosco

      GraphJinofficial

      dosco
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to query databases using natural language, with automatic schema discovery and SQL compilation.
      275 npm
      3,170
      Apache 2.0

    • Supabase MCP Server

      pipethedev
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to Supabase projects, enabling them to manage tables, query data, deploy Edge Functions, handle migrations, and access project resources through natural language commands.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources