CData JDBC Driver connects to PostgreSQL by exposing them as relational SQL models.
Postgresql By Cdata MCP server exists for a simple reason — assistants are far more useful when they can act on Postgresql By Cdata directly instead of describing what you should do. CData JDBC Driver connects to PostgreSQL by exposing them as relational SQL models.
Once Postgresql By Cdata is connected, these are the calls the assistant has available:
postgresql_get_tables — The postgresql_get_tables tool exposed by this serverpostgresql_get_columns — The postgresql_get_columns tool exposed by this serverpostgresql_run_query — The postgresql_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. Postgresql By Cdata's toolset — postgresql_get_tables, postgresql_get_columns, postgresql_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.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| postgresql_get_tables | The postgresql_get_tables tool exposed by this server. |
| postgresql_get_columns | The postgresql_get_columns tool exposed by this server. |
| postgresql_run_query | The postgresql_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/postgresql.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.