CData JDBC Driver connects to Amazon Redshift by exposing them as relational SQL models.
CData JDBC Driver connects to Amazon Redshift by exposing them as relational SQL models. The amazon redshift by cdata mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
amazon_redshift_get_tables — The amazon_redshift_get_tables tool exposed by this serveramazon_redshift_get_columns — The amazon_redshift_get_columns tool exposed by this serveramazon_redshift_run_query — The amazon_redshift_run_query tool exposed by this serverBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Amazon Redshift By Cdata's toolset — amazon_redshift_get_tables, amazon_redshift_get_columns, amazon_redshift_run_query — is a fair guide to whether it matches your workflow. It is maintained by CDataSoftware; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| amazon_redshift_get_tables | The amazon_redshift_get_tables tool exposed by this server. |
| amazon_redshift_get_columns | The amazon_redshift_get_columns tool exposed by this server. |
| amazon_redshift_run_query | The amazon_redshift_run_query tool exposed by this server. |
**Linux/Mac**
```json
{
"mcpServers": {
"{classname_dash}": {
"command": "/PATH/TO/java",
"args": [
"-jar",
"/PATH/TO/CDataMCP-jar-with-dependencies.jar",
"/PATH/TO/amazon-redshift.prp"
]
},
...
}
}Configuration as documented by the project. Restart the client after saving.
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.