Best for
- Developers building AI agents that need direct Teradata access
- Users wanting to quickly create semantic layers
- Users needing database admin capabilities
- Users wanting to use RAG pipelines
T
Teradata MCP Server
Community
Connect AI agents directly to Teradata with enterprise security and extensibility.
GitHub source repository ↗
47FMRS · D
The server provides comprehensive MCP integration for Teradata databases, covering querying, admin, semantic layers, and RAG. Installation is straightforward and supports multiple clients. As a community project, security and support should be self-assessed.
Teradata MCP Server is a community-developed MCP server that enables AI agents to interact directly with Teradata databases. It provides multiple tool sets for querying and analysis, semantic layer generation, AI and RAG pipelines, and database administration. The server runs via uvx over stdio and supports various clients including Claude Desktop, VS Code + Copilot, Open WebUI, and Flowise.
Tools
base
Base tools for exploring tables, profiling data, explaining results, and visualizing patterns.
dba
Database admin tools for managing security, monitoring capacity, and automating backups.
qlty
Quality tools for data quality analysis.
plot
Plotting tools for visualizing patterns.
rag
RAG tools for semantic search and retrieval-augmented generation.
tdvs
Teradata vector store tools for vector storage.
fs
File system tools, possibly for file operations.
sec
Security tools for managing security.
bar
Backup and recovery tools for automated backups.
Setup
- Ensure you have a Teradata database (or free sandbox) and uv installed.
- Add the above JSON configuration to your client's configuration.
- For Claude Desktop, edit claude_desktop_config.json and add the mcpServers configuration.
claude_desktop_config.json
{
"mcpServers": {
"teradata": {
"command": "uvx",
"args": ["teradata-mcp-server"],
"env": {
"DATABASE_URI": "teradata://<USERNAME>:<PASSWORD>@<HOST_URL>:1025/<USERNAME>"
}
}
}
}
Fit and risk
Not for
- Non-Teradata database users
- Users needing a full GUI management interface
- Enterprises requiring official support (community project)
Required permissions
- Requires Teradata database credentials
- May need access to database objects (tables, views, stored procedures)
- May execute SQL queries
- May require file system access (depending on tool)
Risks and side effects
- Database credentials are stored in plaintext in environment
- Executing SQL queries may modify data or impact performance
- Row limit protection reduces token overflow risk
- Community project, security should be self-assessed
Troubleshooting
- Check that the DATABASE_URI environment variable is set correctly
- Ensure Teradata database is reachable and credentials are valid
- Check that command and args in client configuration are correct
- Review logs for detailed error information
Use cases
Exploratory data analysis
Data engineering
Agent development
Visual workflow building
Testing new local LLMs
Supported clients
Claude DesktopFull support
VS Code + CopilotFull support
Open WebUIFull support
FlowiseFull support