CData JDBC Driver connects to Jira by exposing them as relational SQL models.
CData JDBC Driver connects to Jira by exposing them as relational SQL models. Exposed over MCP by the jira by cdata mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Everything the assistant can do here goes through one of these:
jira_get_tables — The jira_get_tables tool exposed by this serverjira_get_columns — The jira_get_columns tool exposed by this serverjira_run_query — The jira_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 planning and project tracking 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. Jira By Cdata's toolset — jira_get_tables, jira_get_columns, jira_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 |
|---|---|
| jira_get_tables | The jira_get_tables tool exposed by this server. |
| jira_get_columns | The jira_get_columns tool exposed by this server. |
| jira_run_query | The jira_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/jira.prp"
]
},
...
}
}Configuration as documented by the project. Restart the client after saving.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.