Merge Unified's Jira integration Merge Agent Handler's Jira MCP server

Connect your AI Agents to Jira in minutes

Merge lets you securely connect your agents to Jira and thousands of tools instantly

Start building for free

Read docs

Jira

Learn more about Merge Agent Handler

Available tools

add_comment

Add a comment to a Jira issue. Supports plain text or ADF format. Text: {'issuekey': 'PROJ-123', 'body': 'Comment'}. ADF: {'issuekey': 'PROJ-123', 'body': {'type': 'doc', 'version': 1, 'content': [...]}}

get_comments

Get comments for a Jira issue

update_comment

Replace the body of an existing Jira comment. Call getcomments first to get a real commentid, which cannot be invented. comment_body accepts plain text, or an ADF dict ({'type': 'doc', 'version': 1, 'content': [...]}) for rich formatting such as bold, lists, tables, links and code blocks.

delete_comment

Delete a comment from a Jira issue

create_issue

Create a Jira issue. REQUIRED: project, issuetype, summary. ALWAYS call discoverissuerequiredfields first — its 'fields' list contains field IDs and allowedvalues needed for the payload. Map each required custom field to its ID, e.g. 'customfield_11623': {'id': '12093'}. Do NOT dump custom field data into description — use the correct field IDs.

get_issue

Get Jira issue details using the issue key

update_issue

Update a Jira issue. Required: issuekey. Optional: summary, description, environment, priority, issuetype, assignee, labels, components, fixVersions, duedate, custom fields (customfield*), or a nested 'fields' object. description/environment accept plain text or an ADF document. Only provided fields are updated; an explicit null clears a custom field.

delete_issue

Delete a Jira issue

link_issues

Link two Jira issues. REQUIRED: outwardissue (FROM), inwardissue (TO), linktype. Common types: 'Duplicate' (marks FROM as duplicate of TO), 'Relates', 'Blocks'. Example: {'outwardissue': 'PROJ-1', 'inwardissue': 'PROJ-2', 'linktype': 'Duplicate'}

transition_issue

Transition a Jira issue to a new status. Provide either transitionid or transitionname. Example: {'issuekey': 'PROJ-123', 'transitionname': 'In Progress', 'comment': 'Starting work'}

search_issues

Search Jira issues using JQL or structured filters. IMPORTANT: By DEFAULT, searches ALL statuses (including Done, Closed) unless explicitly filtered. Use 'resolution' field to filter open issues if needed. DIRECT JQL: {'jql': 'project = PROJ AND status = "Done"'}. STRUCTURED: {'project': 'PROJ', 'textsearch': 'x47'}. For open issues only, add 'resolution': 'Unresolved'. Unbounded search query is not allowed; at least one parameter must be provided. Supports cursor pagination (nextpagetoken, maxresults), date filters (createdafter, updatedafter), text search (textsearch, summarycontains), labels, priority, and field customization (fields, expand). Returns issues plus nextpagetoken (pass to subsequent calls) and is_last (True when no more pages).

get_issue_transitions

Get available transitions for a Jira issue

discover_issue_required_fields

Discover required fields for Jira issue creation. Always call this tool ahead of create_issue.

list_statuses

List all workflow statuses in Jira. READ-ONLY: Creating statuses via API is NOT supported - use Jira UI to add custom statuses like 'In Review', then use this to verify.

get_project_statuses

Get workflow statuses available for a specific project. Use this to verify if custom statuses like 'In Review' are configured before using transition_issue.

get_issue_attachments

Get all attachments from an issue. Returns list with attachment ID, filename, size, author, created date. Use attachment IDs with delete_attachment().

delete_attachment

Delete an attachment by ID. REQUIRED: attachmentId from getissueattachments(). Requires 'Delete All Attachments' or 'Delete Own Attachments' project permission.

add_attachment

Add an attachment to a Jira issue. REQUIRED: issueKey, filename, contentBase64 (base64-encoded file). Optional: contentType (MIME type). Returns attachment ID and metadata.

move_issues_between_projects

Move issues between projects. Max 1000 issues. Returns task ID for async tracking. Requires: targetprojectkey, targetissuetypeid, issuekeys. Auto-maps fields/statuses. Call discoverissuerequired_fields first.

get_move_task_progress

Check progress of bulk move operation. Requires taskid from moveissuesbetweenprojects. Returns status: RUNNING, COMPLETE, or FAILED with progress percentage and result details.

get_projects

Search and filter Jira projects. Supports filtering by: query (name search), keys (project keys), id (project IDs), typeKey (software/servicedesk/business), categoryId, action (view/browse/edit permission), status (live/archived/deleted). Supports ordering via orderBy and field expansion via expand. Returns paginated results with maxresults (default 50, max 100).

get_project

Get a specific Jira project by key or ID

get_project_issue_types

Get issue types for a specific project

get_project_components

Get all components for a Jira project. Returns component names, IDs, descriptions, lead users, and assignee info. Components organize issues (e.g., 'Frontend', 'Backend'). Example: getprojectcomponents(project_key='PROJ')

get_project_versions

Get versions for a specific project

get_priorities

Get all available priorities. Returns list with 'id', 'name', 'description' fields. Use these values when setting priority in createissue or updateissue. Format: {"name": "High"} or {"id": "3"}.

get_project_templates

Get template keys for project type. Returns list with 'templateKey' field (e.g., 'com.pyxis.greenhopper.jira:gh-scrum-template'). Use this templateKey value for createproject's projectTemplateKey parameter. Call this BEFORE createproject.

create_project

Create Jira project. REQUIRED: key (2-10 uppercase), name, projectTypeKey ('software'/'business'/'servicedesk'), projectTemplateKey (from getprojecttemplates), leadAccountId (from getcurrentuser/searchusers). Input at top level, NO 'fields' wrapper. Requires 'Administer Jira' permission and 'manage:jira-configuration' OAuth scope.

update_project

Update a Jira project. All parameters are optional. Only provided fields will be updated. Changing key or schemes requires 'Administer Jira' permission, otherwise 'Administer Projects' permission is sufficient. Example: {'projectIdOrKey': 'PROJ', 'name': 'New Name', 'description': 'Updated description'}.

delete_project

Delete a Jira project. WARNING: This is a destructive operation. Cannot delete archived projects - restore them first via Jira UI. Requires 'Administer Jira' global permission. Example: {'projectIdOrKey': 'PROJ', 'enableUndo': false}.

move_issues_to_sprint

Move issues to sprint. Max 50 issues. Requires sprintid and issuekeys. Optional ranking. Sprint must be active or future. Requires 'Manage Sprints' permission. Use getboardsprints to find sprint IDs.

move_issues_to_backlog

Move issues to backlog. Max 50 issues. Removes from future/active sprints. Requires issue_keys. Use to unassign issues from sprints. Requires 'Manage Sprints' permission and valid license.

get_board_sprints

List sprints for board. Returns sprint IDs, names, states, dates. Filter by state: active, future, closed. Pagination supported. Use to find sprint IDs for move operations.

get_sprint

Get sprint details. Requires sprint_id. Returns state, dates, goal, board ID. Use to check sprint status before moving issues.

create_board

Create Jira board (scrum/kanban). Required: name, type (scrum/kanban), filter_id. Filter must ORDER BY Rank for issue reordering. Returns board ID. Requires 'Create shared objects' permission for shared boards.

get_boards

List all Jira boards. Filter by type (scrum/kanban), name, or project. Pagination supported. Returns board IDs, names, types. Use to discover board IDs for sprint operations.

get_board

Get Jira board details. Requires boardid. Returns name, type, location, configuration. Use getboards to find board IDs.

get_active_sprint

Get the active sprint for a Jira project by project key. Iterates boards for the project in API order (up to 20 boards) and returns the first active sprint found. Use this instead of manually calling getboards and getboard_sprints.

search_users

Search for Jira users. Requires at least one of: query (e.g., 'john'), username, or account_id parameter to search for users.

get_user

Get a specific Jira user by account ID or username

get_current_user

Get the current authenticated user

get_user_assignee_suggestions

Get user assignee suggestions for an issue or project

get_user_groups

Get groups that a user belongs to

validate_credential

Validate Jira credentials. Verifies credentials during setup.

add_worklog

Log work on a Jira issue. Requires issuekey and timespent (Jira duration, e.g. '1h 30m'). Optional comment supports plain text or ADF. adjustestimate controls the remaining estimate ('auto' Jira default, 'leave', 'new', 'manual'). Example: {'issuekey': 'PROJ-123', 'time_spent': '2h', 'comment': 'Investigated the bug'}

get_worklogs

Get worklog entries for a Jira issue

View all tools by creating a free account See more tools

How to set up Merge Agent Handler

In an mcp.json file, add the configuration below, and restart Cursor.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Copy Code

Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.

Make sure Claude is using the Node v20+.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "mcp-remote@latest",
8        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9        "--header",
10        "Authorization: Bearer ${AUTH_TOKEN}"
11      ],
12      "env": {
13        "AUTH_TOKEN": "yMt*****"
14      }
15    }
16  }
17}

Copy Code

Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.

Learn more in the official documentation ↗

1{
2    "mcpServers": {
3      "agent-handler": {
4        "command": "npx",
5        "args": [
6          "-y",
7          "mcp-remote@latest",
8          "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9          "--header",
10          "Authorization: Bearer ${AUTH_TOKEN}"
11        ],
12        "env": {
13          "AUTH_TOKEN": "<ah-production-access-key>"
14        }
15      }
16    }
17  }

Copy Code

In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".

You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.

Learn more in the official documentation ↗

1{
2  "inputs": [
3    {
4      "type": "promptString",
5      "id": "agent-handler-auth",
6      "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7      "password": true
8    }
9  ],
10  "servers": {
11    "agent-handler": {
12      "type": "stdio",
13      "command": "npx",
14      "args": [
15        "-y",
16        "mcp-remote@latest",
17        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18        "--header",
19        "Authorization: Bearer ${input:agent-handler-auth}"
20      ]
21    }
22  }
23}

Copy Code

FAQs on using Merge's Jira MCP server

How can I use the Jira MCP server?

Your use cases depend on the type of agent you’re building. That said, here are a few common use cases:

Combine data sources for broader insights: Your agent can combine information from Jira with other data sources (e.g., your survey tool) to uncover broader insights, such as correlating sprint velocity with customer satisfaction metrics

Manage issues or projects from Slack: Your agent can help users retrieve information on specific Jira issues from an app like Slack to quickly understand their status, details, history, and more. The user can also ask the agent to make specific updates on an issue without leaving Slack

Deliver consistent product updates to leadership: Your agent can send the executive team weekly summaries of the product-specific tickets created in Jira over the past week within Slack; this lets them understand the top issues and, depending on the insights, it can help them make effective resource allocation decisions over time

Coordinate development workflows: Your agent can automatically create Jira issues when critical bugs are detected in production, link them to related GitHub pull requests, and assign them to the appropriate developers based on code ownership

What are popular tools for Jira’s MCP server?

Here are some of the most common tools segmented by data types:

Issues

<code class="blog_inline-code">search_issues</code>
<code class="blog_inline-code">get_issue</code>
<code class="blog_inline-code">get_issue_attachments</code>
<code class="blog_inline-code">update_issue</code>
<code class="blog_inline-code">add_comment</code>

Projects

<code class="blog_inline-code">get_projects</code>
<code class="blog_inline-code">get_project_statuses</code>
<code class="blog_inline-code">create_project</code>
<code class="blog_inline-code">update_project</code>

Boards

<code class="blog_inline-code">get_board</code>
<code class="blog_inline-code">get_board_sprints</code>
<code class="blog_inline-code">create_board</code>

What makes Merge Agent Handler’s Jira MCP server better than alternative Jira MCP servers?

Merge Agent Handler differentiates itself by operating as a full agent–tool management platform, not just an MCP endpoint.

Enterprise-grade security and DLP: All Jira tool inputs and outputs pass through a security gateway that can block, redact, or mask sensitive data based on default or custom rules. This helps prevent data leakage when agents create or update Jira issues

Managed authentication and credentials: Merge Agent Handler handles Jira authentication flows, credential storage, and token validation, removing this burden from your agent code

Real-time observability and audit trail: Every Jira tool call is logged with full context. Logs are fully searchable, enabling teams to audit agent behavior, debug failures, and optimize workflows

Tool Packs and controlled access: Jira tools can be bundled with other MCP connectors (e.g., Slack, Salesforce) into Tool Packs, allowing precise control over which Jira actions an agent is allowed to perform

Can I set custom security rules for Jira tool calls with Merge Agent Handler?

Yes, you can set custom security rules for any Jira tool calls to block or redact sensitive data. You can also log certain tool calls, allowing the agent to make them while providing your team with real-time visibility whenever this happens.

Here are some specific examples:

Block your agents from creating or updating Jira issues with credit card numbers in fields like descriptions and comments

Automatically redact SSNs when your agents retrieve or update Jira issue details. That way, they only see masked versions

Monitor and log whenever your agents attempt to add authentication credentials or access tokens in Jira issue comments or descriptions

Block your agents from creating Jira tickets with sensitive terms like "confidential", "internal only", or proprietary project codenames in the summary or description fields

How can I add tools to Merge Agent Handler’s Jira MCP server?

You can add or modify Jira tools using Connector Studio within Merge Agent Handler:

1. Start from a pre-built Jira connector: Log into the Agent Handler dashboard and navigate to "Connectors" in the sidebar. Select the Jira connector from the list of available connectors.

2. Enable or disable specific Jira tools in a Tool Pack: Navigate to "Tool Packs" and either create a new Tool Pack or select an existing one. Add the Jira connector to your Tool Pack, then choose which specific Jira tools you want to make available to your agent.

3. Customize/extend tools, or add tools tailored to your workflows: Within Connector Studio, you can modify existing Jira tools by editing their names, descriptions, input schemas, and implementation logic. You can also create entirely new custom tools for Jira-specific actions that aren't available by default, such as custom field updates or advanced query filters.

4. Associate the updated Tool Pack with your agent: Once you've configured your Jira tools, save your Tool Pack. Then connect it to your agent using the MCP entry URL provided in the Tool Pack settings. Your agent will now have access to exactly the Jira tools you've configured, with all authentication, security rules, and logging handled automatically by Agent Handler.