Teradata MCP Server
Related Servers
Alternatives to Teradata MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables AI agents and users to query, analyze, and manage Teradata databases through modular tools for search, data quality, administration, and data science operations. Provides comprehensive database interaction capabilities including RAG applications, feature store management, and vector operations.39MIT
- FlicenseBqualityFmaintenanceEnables secure interaction with Teradata databases through SQL queries, schema exploration, and business intelligence analysis with enterprise-grade OAuth 2.1 authentication and workload management capabilities.89-
- FlicenseAqualityDmaintenanceEnables running SQL queries, exploring metadata, and interacting with Teradata databases through the Model Context Protocol.4-
- FlicenseNot gradedqualityDmaintenanceEnables machine learning data preprocessing pipeline creation and model training, deployment, and prediction for Teradata databases.1-
- FlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Teradata databases through Claude, allowing data exploration, profiling, and in-database KMeans clustering via MCP.-
- AlicenseCqualityDmaintenanceMCP server for Teradata databases, providing tools and prompts for querying, analyzing, and managing data through AI agents.38MIT
TDQS
Scored across 47 tools
Each tool has a clearly distinct purpose, and descriptions explicitly cross-reference related tools to guide selection. Overlaps like base_columnDescription vs base_columnMetadata are resolved by stating when to use each. No ambiguity remains for an agent.
The prefix system (base_, dba_, graph_, etc.) is consistent, but naming after the prefix mixes verb_noun, noun_verb, and camelCase patterns (e.g., base_readQuery vs base_tableList, base_columnMetadata). Some names omit underscores between words, reducing predictability.
47 tools is high for a single server, covering diverse domains (DBA, graph, quality, RAG, security, SQL optimization). While each domain is internally coherent, the breadth suggests the server could be split into smaller, more focused servers. The count exceeds the recommended 3-15 range for a well-scoped server.
The tool surface is comprehensive for a read-heavy database server: it covers metadata inspection, DBA analytics, dependency graph analysis, data quality profiling, security visibility, and SQL optimization. Minor gaps exist (no user/role creation, no write operations), but they align with the server's apparent purpose.