Skip to main content
Glama
Pibbers

teradata-gcfr-mcp-server

by Pibbers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to teradata-gcfr-mcp-server

No user-submitted related servers found.

    Related Servers

    • teradata-mcp-poc

      hanaahammad
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Teradata databases through Claude, allowing data exploration, profiling, and in-database KMeans clustering via MCP.
      -

    • redash-mcp

      seob717
      A
      license
      A
      quality
      B
      maintenance
      MCP server that connects Redash to Claude AI, enabling natural language data queries, dashboard management, and SQL execution.
      24
      277 npm
      1
      MIT

    • ONE-MCP

      alexxcpr
      F
      license
      A
      quality
      D
      maintenance
      MCP server for the ONE Framework ERP that enables Claude to explore data models, run queries, and understand business logic through autonomous access.
      10
      -

    • mcp-db-universal

      nishant-gudipaty
      A
      license
      A
      quality
      D
      maintenance
      A database-agnostic MCP server that enables natural language queries to your database through Claude or Copilot, automatically writing and executing SQL.
      8
      8 npm
      MIT
    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.7/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools target a distinct monitoring concern—streams vs processes, current vs historical, load vs transform. A few pairs like load_stats/load_status and process_history/process_status_summary have overlapping row/status information, but descriptions provide enough differentiation.

    Naming Consistency4/5

    All tools share the gcfr_ prefix and use snake_case with descriptive subject+report type names (e.g., stream_status, process_history, sla_process_report). Minor structural deviations such as dataset_registered and health_check break the pattern slightly but remain predictable.

    Tool Count3/5

    21 tools is in the heavy range and each one covers a specific report or query, which is justified by the broad monitoring domain. Still, the count is large enough that an agent may need to scan many similar names.

    Completeness5/5

    The tool surface covers the full operational monitoring lifecycle: stream/process status and history, load and transform statistics, failure/error investigation, SLA reporting, performance trends, data lineage, and connectivity health. No obvious dead ends or missing monitoring scenarios are apparent for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources