BachStudio Teradata MCP Server
Related Servers
Alternatives to BachStudio Teradata MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that turns Teradata Vantage into a full-stack analytics agent platform, providing AI agents with structured knowledge of Teradata's native functions for correct and optimal SQL analytics.11MIT

Teradata MCP Serverofficial
AlicenseAqualityAmaintenanceA server providing tools for querying and analyzing Teradata databases, including database management, data quality assessment, and SQL execution capabilities through an MCP interface.47738 PyPI56MIT- AlicenseAqualityCmaintenanceConnects AI agents to Teradata databases for querying, analysis, administration, and AI pipelines with enterprise security.47MIT
- AlicenseAqualityDmaintenanceAn MCP server that connects Claude to Teradata GCFR operational reporting, enabling natural-language queries about stream status, process history, loads, transforms, errors, SLA, and data lineage without writing SQL.21MIT
- AlicenseNot gradedqualityAmaintenanceThis MCP server enables AI models to directly and securely query databases using persistent or temporary connections, supporting multiple data sources with automatic connection management.73 npm1MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI assistants to query and manage Microsoft SQL Server databases using natural language.184 npm5MIT
TDQS
Scored across 38 tools
Most tools have distinct purposes, but there is some overlap between base_tableUsage and dba_tableUsageImpact, which both measure table usage. Similarly, qlty_missingValues and qlty_rowsWithMissingValues could be confused, though they target different outputs. Overall, the tool set is reasonably disambiguated.
Tool names use prefixes (base_, dba_, qlty_, sec_, sql_, rag_, plot_) but mixing camelCase (base_columnDescription) and underscores (sql_Analyze_Cluster_Stats) within the same server creates inconsistency. Naming after the prefix is also inconsistent: some are verb-noun (base_readQuery), others noun-noun (base_tableList).
With 38 tools, the server is on the heavier side for a database interaction server. While the scope justifies many functions, several tools overlap (e.g., table usage metrics) and plotting tools feel slightly out of place, making the count feel excessive rather than lean.
The server covers broad areas (metadata, DBA, data quality, security, SQL optimization, RAG, plotting), but has notable gaps: no dedicated tools for DDL operations (create/alter/drop) beyond generic readQuery, and no individual RAG utilities (e.g., embedding search). The SQL optimization suite is thorough but dependent on pre-existing tables.