Jira Data Center MCP Server
AaronPJaeger/jira-data-center-mcp-server
Acesso completo ao Jira Data Center via MCP para automação e pesquisa
Ver no GitHubServidor MCP de nível enterprise para Jira Data Center v10 que expõe busca, inspeção, criação e atualização de issues, transições de workflow, comentários, operações Agile e auditoria. Integra Claude e clientes MCP-compatíveis diretamente com instâncias Jira corporativas.
Instalação
npx convez-ai AaronPJaeger/jira-data-center-mcp-server1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Buscar e analisar issues do Jira via Claude com contexto completo
- Criar e atualizar issues automaticamente em workflows complexos
- Consultar histórico, auditoria e propriedades de projetos enterprise
- Automatizar operações Agile (sprints, backlogs) sem deixar o editor
Veredito

Implementação robusta e bem-documentada para integrar Jira Data Center com Claude. Ideal para equipes enterprise que precisam de automação profunda; exige configuração cuidadosa de tokens e URLs, mas oferece cobertura ampla da API Jira.
README
A tradução para o português deste README ainda está na fila.
Jira Data Center v10 MCP Server
Enterprise-grade Model Context Protocol (MCP) server for Jira Data Center v10.
This server exposes Jira search, issue inspection, creation, rich updates, workflow transitions, comments, identity lookup, schema discovery, issue links, attachments, worklogs, Jira Software Agile operations, audit/history, saved filters, issue properties, project roles, groups, security levels, and guarded destructive operations to MCP-compatible clients.
Installation
Quick Install with uv (Recommended)
Install the server with uv:
uv tool install git+https://github.com/AaronPJaeger/jira-data-center-mcp-server.git
To install a specific release:
uv tool install git+https://github.com/AaronPJaeger/jira-data-center-mcp-server.git@v0.1.0
This installs jira-data-center-mcp-server as a standalone executable with all dependencies pre-resolved. To upgrade later:
uv tool upgrade jira-data-center-mcp-server
For development, clone the repository and install locally:
git clone https://github.com/AaronPJaeger/jira-data-center-mcp-server.git
cd jira-data-center-mcp-server
uv sync # install dependencies into local .venv
uv tool install --force . # rebuild the global executable used by MCP clients
After making code changes, rebuild and restart the MCP server:
uv tool install --force .
# Then restart the MCP server from your MCP client (e.g. VS Code MCP panel)
MCP Client Configuration
After installing, add the server to your MCP client configuration. Use the full path to the executable — find it with uv tool dir --bin (typically ~/.local/bin on Linux/macOS or %USERPROFILE%\.local\bin on Windows).
VS Code (settings.json or user-level mcp.json):
{
"servers": {
"jira": {
"type": "stdio",
"command": "/full/path/to/jira-data-center-mcp-server",
"env": {
"JIRA_SERVER_URL": "https://your-jira-instance.com",
"JIRA_PAT": "your_personal_access_token",
"JIRA_MCP_PROFILE": "standard"
}
}
}
}
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"jira": {
"command": "/full/path/to/jira-data-center-mcp-server",
"env": {
"JIRA_SERVER_URL": "https://your-jira-instance.com",
"JIRA_PAT": "your_personal_access_token",
"JIRA_MCP_PROFILE": "standard"
}
}
}
}
Tip: If
~/.local/binis on your PATH (runuv tool update-shellto add it), you can use just"jira-data-center-mcp-server"instead of the full path.
Configuration
The server is configured via environment variables. Create a .env file in your working directory or pass them directly:
JIRA_SERVER_URL=https://your-enterprise-jira-datacenter.com
JIRA_PAT=your_personal_access_token_here
LOG_LEVEL=INFO
JIRA_MCP_PROFILE=standard
| Variable | Purpose | Default |
|---|---|---|
JIRA_SERVER_URL | Jira Data Center base URL | (required) |
JIRA_PAT | Personal Access Token | (required) |
LOG_LEVEL | Logging verbosity | INFO |
JIRA_MCP_PROFILE | Active tool profile | standard |
JIRA_MCP_ENABLED_GROUPS | Override profile with explicit groups (comma-separated) | (none) |
Profiles
Profiles control which tools the server exposes to MCP clients. Use standard if you're unsure — it covers normal day-to-day Jira work without exposing destructive or bulk operations.
| Profile | Purpose |
|---|---|
readonly | Discovery, triage, reporting, metadata, issue history, Agile read-only. Safe for dashboards and bots. |
standard | Recommended default. Normal issue work — create, update, transition, comment, link, attach — without destructive or bulk tools. |
agile | Sprint and backlog planning. Adds board/sprint write operations. |
admin | Metadata, roles, groups, permissions, and security context. Read-heavy admin tasks. |
full | All non-destructive, non-bulk tools. |
dangerous | All tools, including delete and bulk operations. Destructive tools still require confirm=True. |
You can also bypass profiles and enable exact tool groups:
JIRA_MCP_ENABLED_GROUPS=READONLY_CORE,METADATA,WORKFLOW_READ,AGILE_READ
The get_mcp_profile_status tool reports the active profile and enabled groups at runtime.
Getting Your Jira PAT (Personal Access Token):
- Log in to your Jira Data Center instance
- Navigate to Profile > Personal Access Tokens (or your admin dashboard)
- Click Create Token
- Name it "MCP Server" and copy the token value
- Do not commit
.envto version control — add it to.gitignoreif not already present
Manual Installation (without uv)
Prerequisites
- Python 3.10 or later
- Git
Step 1: Clone the Repository
git clone https://github.com/AaronPJaeger/jira-data-center-mcp-server.git
cd jira-data-center-mcp-server
Step 2: Create a Python Virtual Environment
Windows (PowerShell):
python -m venv .venv
.\.venv\Scripts\Activate.ps1
macOS/Linux:
python3 -m venv .venv
source .venv/bin/activate
Step 3: Install Dependencies
pip install -r requirements.txt
Step 4: Run the Server
python -m jira_data_center_mcp_server
Tool Coverage
Search and inspection
search_issuesget_issue_detailsvalidate_jqlget_issue_changelogget_issue_activity
Project/schema metadata
list_projectsget_project_metadataget_create_issue_metadatalist_issue_typeslist_prioritieslist_fieldsget_custom_field_optionslist_componentslist_versions
Issue lifecycle and mutation
create_issuecreate_subtasklist_subtasksupdate_issueupdate_issue_structuredupdate_issue_fieldsdelete_issue
Workflow
get_available_transitionstransition_issuetransition_issue_with_fieldslist_statuseslist_resolutionslist_workflows
Comments and collaboration
add_commentlist_commentsupdate_commentdelete_commentassign_issueunassign_issuelist_watcherswatch_issueunwatch_issuesearch_users
Permissions and server context
get_myselfget_my_permissionsget_server_info
Links, remote links, and issue properties
list_issue_linkslist_issue_link_typescreate_issue_linkdelete_issue_linklist_remote_linksadd_remote_linkdelete_remote_linklist_issue_propertiesget_issue_propertyset_issue_propertydelete_issue_property
Attachments
list_attachmentsadd_attachmentdownload_attachmentdelete_attachment
Worklogs
list_worklogsadd_worklogupdate_worklogdelete_worklog
Jira Software Agile
list_boardsget_board_configurationlist_sprintsget_sprintlist_sprint_issuesmove_issues_to_sprintmove_issues_to_backlogrank_issue
Filters, roles, groups, security
list_filtersget_filterrun_filterlist_project_rolesget_project_role_actorslist_groupslist_security_levelsset_issue_security_level
Conservative bulk operations
bulk_update_issuesbulk_transition_issuesbulk_add_comment
Troubleshooting
Virtual Environment Issues
Problem: command not found: python or .venv not activated
Solution:
- Verify Python is installed:
python --version - Reactivate the virtual environment:
- Windows:
.\.venv\Scripts\Activate.ps1 - macOS/Linux:
source .venv/bin/activate
- Windows:
Jira Connection Errors
Problem: JIRAError: (401) Unauthorized
Solution:
- Verify
JIRA_SERVER_URLis correct (no trailing slashes) - Verify
JIRA_PATtoken is valid and has not expired - Confirm the token has permissions for your Jira instance
Problem: JIRAError: (404) Not Found
Solution:
- Double-check the Jira server URL
- Verify you have network access to the Jira instance
.env File Not Loading
Problem: Server starts but ignores .env values
Solution:
- Confirm
.envexists in the project root directory - Check file encoding is UTF-8 (not UTF-16 or other)
- Restart the server after editing
.env
Safety and Operational Notes
Destructive or broad actions require explicit confirmation parameters:
delete_issue(confirm=True)delete_comment(confirm=True)delete_issue_link(confirm=True)delete_remote_link(confirm=True)delete_issue_property(confirm=True)delete_attachment(confirm=True)delete_worklog(confirm=True)bulk_update_issues(confirm=True)bulk_transition_issues(confirm=True)bulk_add_comment(confirm=True)
Bulk operations only accept explicit issue keys. They do not mutate by broad JQL query.