JiCoRedact. Approve. Document.

Using Jira Data Center with Claude

Claude works with Jira Data Center through an MCP server that runs inside your network. JiCo is such an MCP server, for Jira Cloud as well — it redacts personal data before Claude sees it and holds every write action for your approval.

The short answer

Claude Desktop and Claude Code reach other systems through the Model Context Protocol (MCP). For Jira Data Center you need an MCP server that speaks the Data Center API and can reach your Jira — so it runs inside your company network or on your own computer. Atlassian's own Rovo MCP Server serves Jira Cloud; it reaches Jira Data Center only through the paid Rovo Connector with cloud sync (see Comparison).

JiCo is a local MCP server for Jira Data Center and Jira Cloud. It differs from a plain pass-through in three ways:

Redaction before the AI model. Assignee, reporter, comment authors, mentions, check-digit numbers such as an IBAN or a social security number, and secrets become placeholders such as «Person 1» before Claude sees them. Free text is checked statistically — that finds a lot, but not everything.
Approval for every write action. When Claude wants to change, comment on or create a ticket, JiCo stops and shows you in plain language what is about to happen. It runs only after your approval — and only if the ticket has not changed since.
Evidence. What went to the AI model and who approved what is kept in an append-only log.

In five steps

1. Register. Register in the customer portal; you receive a seven-day trial licence.
2. Install. Download the package for your system — .pkg for macOS (Apple Silicon), .msi for Windows (64-bit).
3. Connect Jira. In the setup, enter the address of your Jira, plus a personal access token (PAT) for Data Center or your e-mail address and API token for Jira Cloud. The token is then kept in the keychain (macOS) or in Credential Manager (Windows), not in a file.
4. Request the licence. Request it in the setup and confirm via the e-mail link; JiCo installs the licence by itself.
5. Connect Claude. In the Approval Cockpit, under Settings › Connect to AI client, click Set up automatically for Claude Desktop or Claude Code and restart Claude.

Then ask Claude about your tickets as usual. The quick start shows every step in detail.

Limits

Jira Cloud signs in with an e-mail address and API token today; OAuth sign-in is not available yet.
No detection finds every piece of personal data in free text. That is why JiCo shows openly what was redacted.
JiCo protects what runs through JiCo. If someone adds a second, unprotected Jira connection to Claude next to it, JiCo does not learn about it.