CData JDBC Driver connects to SAP BusinessObjects BI by exposing them as relational SQL models.
Most database access work still happens through a UI a human drives. Sap Businessobjects Bi By Cdata MCP server moves it into the conversation instead. CData JDBC Driver connects to SAP BusinessObjects BI by exposing them as relational SQL models.
The server publishes 3 tools. What each one is for:
source_get_tables — The source_get_tables tool exposed by this serversource_get_columns — The source_get_columns tool exposed by this serversource_run_query — The source_run_query tool exposed by this serverBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
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. Sap Businessobjects Bi By Cdata's toolset — source_get_tables, source_get_columns, source_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 |
|---|---|
| source_get_tables | The source_get_tables tool exposed by this server. |
| source_get_columns | The source_get_columns tool exposed by this server. |
| source_run_query | The source_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/sap-businessobjects-bi.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.