Connect Jira to your AI agents.
Connect Jira data to AI agents with Combined. Explore issues, projects, users, source setup, MCP access and read-only business queries.
Put Jira records to work in the agent you already use. Combined syncs business data into a managed data layer and exposes scoped, read-only queries through MCP.
Projects, issues, comments, worklogs, sprints, and team activity.
Start with 5 million MAR without a card; usage after the trial is $5 per million MAR, with no monthly minimum. Combined offers 1,125 connectors across catalog sources and connectors generated through desktop automation.
How to connect Jira to Combined
- Add your source. Open Connected Apps in Combined and select Jira. Use the account or workspace that contains the records you want to analyze.
- Authorize access. Complete the connection flow and choose the required permissions. The setup reference below shows the upstream source's configurable fields; the Combined flow may handle some of them for you.
- Select datasets and sync. Choose the relevant data, set any available history filters, and wait for the first successful sync.
- Grant your agent access. Use the Set up or Access workspace to connect your agent through MCP and scope it to the sources it needs.
- Ask a first question. Discover the synced schema, check freshness, and run a bounded read-only query. Then add another source for a cross-app analysis.
The onboarding guide covers the workspace flow. Prepare these Jira settings before connecting:
| Setting | When needed | Input |
|---|---|---|
| Authentication | Required by source schema | API Token / Service Account / OAuth2.0 |
| API Token | Depends on selected setup option | Credential entered in the connection flow |
| Depends on selected setup option | string | |
| Service Account Token | Depends on selected setup option | Credential entered in the connection flow |
| Client ID | Depends on selected setup option | Credential entered in the connection flow |
| Client Secret | Depends on selected setup option | Credential entered in the connection flow |
| Refresh Token | Depends on selected setup option | Credential entered in the connection flow |
| Domain | Required by source schema | string |
| Expand Issue Changelog | Optional | boolean |
| Expand Issue Transitions | Optional | boolean |
| Expand Issues stream | Optional | array |
| Lookback window | Optional | integer |
| Number of concurrent threads | Optional | integer |
| Projects | Optional | array |
| Render Issue Fields | Optional | boolean |
| Start Date | Optional | string |
Authentication choices are alternatives. Supply the settings for your selected method; enter credentials in the connection flow, rather than in an agent prompt.
Jira datasets you can evaluate
This reference comes from the upstream source catalog and connector definition, version 6.0.1. Your account permissions, selected streams and successful sync determine what your agent can query. Discover the actual table and field names in Combined before writing SQL.
| Dataset | Record key | Update field | Example fields |
|---|---|---|---|
issues | id | updated | expand, id, self, key, renderedFields (19 fields in reference) |
projects | id | Inspect sync configuration | expand, self, id, key, description (34 fields in reference) |
users | accountId | Inspect sync configuration | self, key, accountId, accountType, name (14 fields in reference) |
issue_fields | id | Inspect sync configuration | id, key, name, custom, orderable (11 fields in reference) |
application_roles | key | Inspect sync configuration | key, groups, name, defaultGroups, selectedByDefault (14 fields in reference) |
avatars | id | Inspect sync configuration | id, owner, isSystemAvatar, isSelected, isDeletable (7 fields in reference) |
boards | id | Inspect sync configuration | id, self, name, type, projectId (7 fields in reference) |
dashboards | id | Inspect sync configuration | description, id, isFavourite, name, owner (14 fields in reference) |
filters | id | Inspect sync configuration | expand, self, id, name, description (15 fields in reference) |
groups | groupId | Inspect sync configuration | name, groupId |
issue_link_types | id | Inspect sync configuration | id, name, inward, outward, self |
issue_navigator_settings | Inspect schema | Inspect sync configuration | label, value |
issue_notification_schemes | id | Inspect sync configuration | expand, id, self, name, description (7 fields in reference) |
issue_priorities | id | Inspect sync configuration | self, statusColor, description, iconUrl, name (7 fields in reference) |
issue_resolutions | id | Inspect sync configuration | self, id, description, name, isDefault |
issue_security_schemes | id | Inspect sync configuration | self, id, name, description, defaultSecurityLevelId (6 fields in reference) |
issue_types | id | Inspect sync configuration | avatarId, description, entityId, hierarchyLevel, iconUrl (11 fields in reference) |
issue_type_schemes | id | Inspect sync configuration | id, name, description, defaultIssueTypeId, isDefault |
issue_type_screen_schemes | id | Inspect sync configuration | id, name, description |
jira_settings | id | Inspect sync configuration | id, key, value, name, desc (9 fields in reference) |
labels | label | Inspect sync configuration | label |
permissions | key | Inspect sync configuration | key, name, type, description |
permission_schemes | id | Inspect sync configuration | expand, id, self, name, description (7 fields in reference) |
project_categories | id | Inspect sync configuration | self, id, name, description |
project_roles | id | Inspect sync configuration | actors, admin, currentUserRole, default, description (11 fields in reference) |
project_types | Inspect schema | Inspect sync configuration | key, formattedKey, descriptionI18nKey, icon, color |
screens | id | Inspect sync configuration | id, name, description, scope |
screen_schemes | id | Inspect sync configuration | id, name, description, screens, issueTypeScreenSchemes |
time_tracking | key | Inspect sync configuration | key, name, url |
workflows | Inspect schema | Inspect sync configuration | id, name, description, isEditable, scope (13 fields in reference) |
workflow_schemes | id | Inspect sync configuration | id, name, description, defaultWorkflow, issueTypeMappings (13 fields in reference) |
workflow_statuses | id | Inspect sync configuration | self, description, iconUrl, name, id (8 fields in reference) |
workflow_status_categories | id | Inspect sync configuration | self, id, key, colorName, name |
filter_sharing | id | Inspect sync configuration | id, filterId, type, project, role (6 fields in reference) |
issue_custom_field_contexts | id | Inspect sync configuration | id, fieldId, name, description, isGlobalContext (7 fields in reference) |
issue_custom_field_options | id | Inspect sync configuration | id, value, optionId, disabled, fieldId (6 fields in reference) |
issue_properties | key | Inspect sync configuration | key, issueId, value, isdefault |
issue_remote_links | id | Inspect sync configuration | id, issueId, self, globalId, application (7 fields in reference) |
issue_transitions | issueId + id | Inspect sync configuration | fields, hasScreen, id, issueId, isAvailable (11 fields in reference) |
issue_votes | Inspect schema | Inspect sync configuration | self, issueId, votes, hasVoted, voters |
issue_watchers | Inspect schema | Inspect sync configuration | self, issueId, isWatching, watchCount, watchers |
project_avatars | id | Inspect sync configuration | id, projectId, owner, isSystemAvatar, isSelected (8 fields in reference) |
project_components | id | Inspect sync configuration | self, id, name, description, lead (16 fields in reference) |
project_email | projectId | Inspect sync configuration | projectId, emailAddress |
project_permission_schemes | id | Inspect sync configuration | self, projectId, id, description, name |
project_versions | id | Inspect sync configuration | expand, self, id, description, name (17 fields in reference) |
screen_tabs | id | Inspect sync configuration | id, name, screenId |
screen_tab_fields | id | Inspect sync configuration | id, name, screenId, tabId |
sprints | id | Inspect sync configuration | id, self, state, name, startDate (11 fields in reference) |
users_groups_detailed | accountId | Inspect sync configuration | self, key, accountId, accountType, name (14 fields in reference) |
board_issues | id | updated | expand, id, self, key, fields (8 fields in reference) |
sprint_issues | id | updated | expand, id, self, key, fields (9 fields in reference) |
issue_comments | id | updated | self, id, issueId, author, body (12 fields in reference) |
issue_worklogs | id | updated | self, author, updateAuthor, comment, created (13 fields in reference) |
issue_changelogs | id | updated | id, items, author, created, updated (6 fields in reference) |
A cursor tracks changes for a source stream. It is not automatically the right date for a business metric: invoice date, close date and record-update date can answer different questions.
Useful Jira questions for your AI agent
Start with the datasets you have granted. These prompts turn the referenced schema into checks and summaries; the agent should verify each field against your synced data.
- What is the backlog by project, issue type and current status? Inspect the workflow status names first.
- Which unresolved issues are past their due date?
- Which issues changed status during the reporting window? Use changelog records if the source exposes them.
- Summarize customer-linked issues using explicit support or CRM references rather than matching company names loosely.
Combine Jira with another business app
Connect the second source, identify a maintained customer, account or project mapping, and aggregate each dataset before joining. Keep unmatched records visible and define the reporting window. The CRM-and-billing worked example includes runnable SQL demonstrating how a many-to-many join can double the result.
Use Jira data in Claude Code, Cursor or another MCP client
Once the source is synced, the agent connects to Combined's MCP interface. Use the generated account-specific configuration from your workspace, keep credentials local, and grant only the sources needed for the task. Follow the Claude Code walkthrough or the MCP setup reference.
Use Combined to analyze my Jira data.
List my granted sources, discover the datasets and describe their fields.
Look for datasets corresponding to issues, projects, users, issue_fields, application_roles, avatars.
Check the last successful sync and report the available date coverage.
Propose three useful questions based on the fields actually available.
For the question I choose, run read-only SQL over the complete matching dataset.
Use a bounded result; include source names, time window and query receipt.
Ask for a missing join key or metric definition instead of inventing one.Download this Jira guide as Markdown to use alongside your agent instructions.
Which Jira connection fits the task?
Managed data for complete questions across apps
Choose Combined when you want to analyze synced records, calculate totals, or join Jira with other business data without operating a separate ingestion and query stack. The agent works with your source grants and read-only SQL access.
Application tools for live operations
For a task that must change Jira immediately, evaluate its available API, native agent tools or desktop workflow. Keep application-action permissions separate from read-only analytics access. A live lookup and an aggregate over synced history solve different jobs.
Desktop-generated connectors for workflows beyond the catalog
Combined's 1,125-connector coverage includes connections generated through computer use. Choose this route when the workflow depends on an application's desktop or browser interface, and establish the fields, access and refresh behavior for that connection.
Read the direct MCP versus managed data comparison and compare business-data MCP options.
Troubleshoot your Jira connection
- Authorization fails: check the selected authentication method, credential validity, source permissions and target account.
- History is missing: check the source's start-date or history filter and allow the initial sync to finish before comparing totals.
- The wrong records appear: verify the workspace, account, project or domain selected in the source settings.
- A dataset is absent: check whether it is enabled and permitted for your account, then inspect discovery and sync status.
- The agent cannot query it: confirm the source is included in the agent's grant and that its sync succeeded.
- A total looks wrong: inspect record keys, duplicate rows, time zones, currencies and join fanout before changing the prompt.
Source details reviewed September 10, 2026. Jira upstream connector documentation · Versioned connector definition. See also Combined Sources and data freshness for AI agents.