Jira Data Center is the self-hosted edition of Jira by Atlassian, run on your own servers. This connector lets your AI agents search, create, and update issues, comments, projects, and worklogs on your Jira Data Center server through Agen.co.
Use this page if you host Jira yourself. If you use Jira on Atlassian's cloud (an address ending in atlassian.net), see Jira instead. To reach Jira and Confluence on Atlassian's cloud through Atlassian's own MCP server, see Atlassian.
You can connect with either of two methods:
| Method | Best for | Minimum Jira version |
|---|---|---|
| OAuth | Each person acts with their own Jira permissions. You create an incoming application link on your Jira server. | 8.22 |
| Personal Access Token | A single token tied to one Jira user, for example a dedicated service account. No application link needed. | 8.14 |
Prerequisites
Prerequisites
- A Jira Data Center server, version 8.22 or later for OAuth, or 8.14 or later for a Personal Access Token.
- Network access from Agen.co to your Jira server. If the server is behind a firewall or VPN, allow Agen.co's outbound traffic before you connect.
- For OAuth: a Jira administrator who can create application links.
- For a Personal Access Token: a Jira user whose permissions match what your agents should be able to do.
Agen.co asks for your server's host, which it uses to build every request. Use the address you type in the browser to open Jira, without https:// and without a trailing slash:
| If Jira is at | Enter |
|---|---|
https://jira.acme.com | jira.acme.com |
https://jira.acme.com:8443 | jira.acme.com:8443 |
https://acme.com/jira | acme.com/jira |
Include the port or the context path if your server uses one. The connector always uses HTTPS.
- In the Agen.co portal, go to Connectors → My connectors and click Add connector.
- In the Select connector drawer, search for
Jira Data Centerand select it. The Add Jira Data Center panel opens. - Under Authentication method, select OAuth.
- Copy the read-only Callback URL. Copy the whole value, including the path, rather than assembling it yourself. See How to get your Redirect URL.
Leave the panel open. You return to it after creating the application link.
- Sign in to Jira as an administrator and go to Administration → Applications → Application links.
- Click Create link, select External application, and set the direction to Incoming.
- Enter a name, for example
Agen.co. - Paste the Callback URL you copied into the Redirect URL field.
- Set the permission to Write. Write includes read access, so this is the only permission the connector needs.
- Save the link, then copy the Client ID and Client secret that Jira shows.
Keep the client secret secure
Keep the client secret secure
Never share or commit the client secret to version control. If you lose it, open the link in Application links to view its details, or create a new link.
Return to the Add Jira Data Center panel and fill in the fields:
| Field | Required | Description |
|---|---|---|
| Connector Name | Yes | A name for this connection, for example Jira Data Center. |
| Client ID | Yes | The Client ID from the application link. |
| Client Secret | Yes | The client secret from the application link. |
| Jira server host | Yes | Your server host, as described in Find your Jira server host. |
Click Add. The connector is created right away. The first time a user's agent calls one of its tools, that user signs in to your Jira server and approves access.
- Sign in to Jira as the user the connector should act as.
- Select your avatar in the top-right corner, then select Profile → Personal Access Tokens.
- Click Create token, enter a name, and optionally set an expiry in days.
- Click Create and copy the token. Jira shows it only once.
The token acts as its owner
The token acts as its owner
Every request runs with the permissions of the user who created the token. Use a dedicated user with only the access your agents need. An expired token cannot be reactivated, so create a new token and update the connector before the old one expires.
- In the Agen.co portal, go to Connectors → My connectors and click Add connector.
- Search for
Jira Data Centerand select it. In the Add Jira Data Center panel, under Authentication method, select Personal Access Token. - Fill in the fields:
| Field | Required | Description |
|---|---|---|
| Connector Name | Yes | A name for this connection, for example Jira Data Center. |
| Personal Access Token | Yes | The token you created in Jira. |
| Jira server host | Yes | Your server host, as described in Find your Jira server host. |
- Click Add.
Enabling the connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.
The connector exposes 33 tools:
| Area | What it covers |
|---|---|
| Issues | Searching with JQL, reading, creating, updating, deleting, and assigning issues, and moving them through workflow transitions |
| Comments | Reading, adding, updating, and deleting comments |
| Projects | Listing and reading projects, and creating, updating, and deleting them |
| Worklogs | Logging time and reading the worklogs on an issue |
| Watchers | Adding, removing, and listing the watchers of an issue |
| Issue links | Linking and unlinking issues, and listing the available link types |
| Metadata | Finding valid issue types for a project and the fields that can be edited on an issue |
| Attachments | Uploading, reading the details of, and deleting attachments |
| Users | Reading the connected user, searching users, and looking one up by username or key |
- Rich text uses Jira wiki markup. Issue descriptions, comments, and worklog comments are plain wiki-markup text, for example
*bold*andh2. Heading. Markdown is not rendered. - People are identified by username, not account ID. Assigning an issue, adding a watcher, or mentioning someone uses the Jira username, for example
[~jsmith]in a comment. Search for a user first if an agent only has a name or email address. - Project changes need administrator rights. Creating, updating, and deleting a project requires the connected user to be a Jira administrator, and deleting a project deletes all of its issues.
- An issue with sub-tasks is deleted together with them. Jira refuses to delete an issue that has sub-tasks unless its sub-tasks are deleted too.
- Suppressing notifications needs administrator rights. Turning off watcher emails when updating an issue is only allowed for administrators.
- Search results are capped by your server. A search returns at most the number of issues your server allows per request, so large result sets need paging.
- Everything runs with the connected user's permissions. An agent can only see and change what that user can, whichever method you use.
- No cloud site selection. The tool that lists Atlassian cloud sites in the Jira connector is not included, because your connection always points at the one server you entered.