Jira MCP server

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

What it does This n8n workflow creates a powerful AI powered Jira management system that allows you to use Claude or other AI assistants to create, update, and manage Jira tickets through natural l...

Best for

Project Management automation workflows
AI Chatbot automation workflows
intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.jiratool, @n8n/n8n-nodes-langchain.mcptrigger, n8n-nodes-base.httprequesttool

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Tamer.

Original n8n.io source

1.1 Workflow description

Title: Jira MCP server
Workflow name: Jira MCP server

What it does This n8n workflow creates a powerful AI-powered Jira management system that allows you to use Claude or other AI assistants to create, update, and manage Jira tickets through natural language requests. The workflow exposes key Jira functions as AI tools, enabling you to interact with your Jira instance through conversational commands. How it works

The workflow sets up an MCP (Model Control Protocol) server, allowing compatible AI assistants to use a suite of Jira management tools The AI assistant can perform various Jira operations including:

Creating new tickets with customized fields Adding comments to existing tickets Retrieving available status transitions for tickets Attaching files to tickets Changing ticket statuses Retrieving detailed information about tickets Getting available projects and issue types

When you make a request to your AI assistant, it determines which Jira operation to perform and executes it through this workflow

Setup Steps

Prerequisites:

Active Jira Cloud account with admin access n8n instance with the Langchain and MCP nodes installed Claude Desktop App or another compatible AI assistant

Jira Credentials Setup:

Configure your Jira Cloud API credentials in n8n Ensure your Jira account has sufficient permissions for all operations

Workflow Configuration:

Import this template into your n8n instance Set up the MCP Trigger node with your desired path (currently "test_mcp") Verify that all Jira tool nodes are correctly connected to the MCP Server node Activate the workflow

Using Claude as an MCP Client:

Open your Claude Desktop App Navigate to Settings > Developer Settings Enable "Connect to local MCP servers" Add a new connection with the URL path to your n8n MCP server (e.g., "http://localhost:5678/webhook/test_mcp") Start a new conversation and ask Claude to perform Jira tasks

Example Usage with Claude Once you've set up the connection between Claude and your MCP server, you can use natural language to manage your Jira tickets. Here are some examples:

Creating a ticket: "Claude, please create a new Jira ticket in the Web Development project with bug issue type. The summary should be 'Homepage loading slowly' and the description should be 'Users are experiencing delays of 5+ seconds when loading the homepage on mobile devices.'" Adding a comment: "Claude, please add a comment to Jira ticket WEB-123 saying 'This issue has been reproduced on multiple devices and browsers. Priority should be increased.'" Checking status: "Claude, can you get the details of ticket WEB-123 and tell me its current status?" Changing status: "Claude, please move ticket WEB-123 to 'In Progress' status."

This workflow creates a seamless bridge between your AI assistant and Jira, making project management more efficient through natural language interactions.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Create Jira ticket

Type / Role: n8n-nodes-base.jiraTool - jiraTool
Config choices: Version 1

Block 2 - Add Comment to Jira Ticket

Type / Role: n8n-nodes-base.jiraTool - jiraTool
Config choices: Version 1

Block 3 - Get Ticket transitions

Type / Role: n8n-nodes-base.jiraTool - jiraTool
Config choices: Version 1

Block 4 - Add Attachment to Jira TIcket

Type / Role: n8n-nodes-base.jiraTool - jiraTool
Config choices: Version 1

Block 5 - Change Jira Ticket Status

Type / Role: n8n-nodes-base.jiraTool - jiraTool
Config choices: Version 1

Block 6 - Jira MCP Server

Type / Role: @n8n/n8n-nodes-langchain.mcpTrigger - mcpTrigger
Config choices: Version 1

Block 7 - Get Issue

Type / Role: n8n-nodes-base.jiraTool - jiraTool
Config choices: Version 1

Block 8 - Get Projects and Issue Types

Type / Role: n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices: Version 4.2

3. Summary Table

Workflow	Jira MCP server
Complexity	intermediate
Nodes	8
Categories	Project Management, AI Chatbot
Author	Tamer
Published	08 May 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/3939/3939.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Project Management workflows AI Chatbot workflows

Frequently asked questions

What does Jira MCP server do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Project Management, AI Chatbot use case.

Tamer

6 workflows

Nodes

n8n-nodes-base.jiratool @n8n/n8n-nodes-langchain.mcptrigger n8n-nodes-base.httprequesttool

Complexity

intermediate

Published 08 May 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/3939/3939.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Tag stale ClickUp tasks and escalate overdue items with assignee comments

## Quick overview This workflow runs daily on a schedule and checks ClickUp tasks in one or more lists for inactivity based on the task’s date_updated field, automatically applying “stale” tags and escalating long-idle tasks by tagging them and posting an assignee comment. ## How it works 1. Runs every day at the configured hour using the schedule trigger. 2. Loads monitoring settings (statuses, tags, stale thresholds, and tag names) and fetches matching tasks from the selected ClickUp list(s), then merges and deduplicates them. 3. Skips tasks that already have the second-level stale tag (for example, stale:14). 4. For tasks without the first-level stale tag, checks the last updated timestamp and adds either the first-level stale tag (for example, stale:7) or the second-level stale tag if they already exceed the higher threshold. 5. For tasks that already have the first-level stale tag, checks whether enough time has passed since that tag was applied and, if so, removes the first-level tag and adds the second-level stale tag. 6. When a task is escalated to the second-level stale tag, posts a warning comment on the ClickUp task and assigns the comment to the task assignee (or the creator if no assignee exists). ## Setup 1. Add a ClickUp API credential (OAuth or API token) and select it on all ClickUp nodes. 2. In the ClickUp task search node(s), choose the list(s) you want to monitor and enable/configure the second list node if you want to pull tasks from multiple lists. 3. Update the monitoring settings (monitoredStatuses, monitoredTags, daysUntilFirstStaleTag, daysUntilSecondStaleTag, and the stale tag names) to match your ClickUp workspace conventions. 4. Adjust the schedule trigger time and, if needed, set the workflow timezone in n8n settings so the run time matches your local time. ## Requirements - A ClickUp account with API access - ClickUp credential configured in n8n - At least one ClickUp list to monitor ## Customization - Change thresholds — Edit `daysUntilFirstStaleTag` and `daysUntilSecondStaleTag` in `SetContext` to any number of days - Change tag names — Update `firstStaleTagName` / `secondStaleTagName` to match your ClickUp tag naming convention - Monitor different statuses — Edit `monitoredStatuses` and `monitoredTags` in `SetContext` (e.g. add `review`, `blocked`) - Add more lists — Duplicate `GetTaskFromList1`, update the List ID, enable the node, and connect its output to a new input port on `AppendListTasks` - Change schedule — Open `TriggerRegularly` and switch from daily to weekdays-only or any custom cron interval - Disable subtasks — Open each `GetTaskFromList` node and set `subtasks` to `false` in the Filters section

View

Summarize daily Slack standups with OpenAI, Notion, and Google Sheets

## Quick overview This workflow runs every weekday, pulls standup messages from a Slack channel, uses OpenAI to generate a structured daily digest, saves the digest to a Notion database, posts a summary back to Slack, and appends an audit entry to Google Sheets. ## How it works 1. Runs every weekday morning on a cron schedule. 2. Fetches the day’s recent messages from a specified Slack standup channel and filters out bot, subtype, and join/leave system messages. 3. Checks whether any standup messages remain and posts a Slack notice if none are found. 4. Formats the remaining Slack updates into a single structured prompt with date, team name, and message count. 5. Sends the formatted standup text to OpenAI (gpt-4.1-mini) to generate a JSON digest with summary, highlights, blockers, per-user updates, and mood. 6. Parses and enriches the AI output with metadata, creates a new page in a Notion database, posts the digest to a Slack summary channel, and appends a run record to a Google Sheets “Audit Log” sheet. ## Setup 1. Add a Slack OAuth2 credential and set the standup channel ID (history source) and the summary channel ID (digest destination). 2. Add an OpenAI credential and confirm the model selection (gpt-4.1-mini) is available in your account. 3. Add a Notion credential, create/select a target database, and replace `YOUR_NOTION_DATABASE_ID` (and ensure the database has the referenced properties: Date, Team, Message Count, Mood). 4. Add a Google Sheets Service Account credential, share the target spreadsheet with the service account email, and replace `YOUR_SHEET_ID` and the sheet name (“Audit Log”) if different. 5. Adjust the schedule cron expression (`0 9 * * 1-5`) to match your team’s standup timing and timezone expectations.

View

Sync check due dates from Google Sheets to Google Calendar with Telegram alerts

## Quick overview This workflow watches a Google Sheets check inventory list and creates or updates matching all-day events in Google Calendar, then posts a creation or update notice to a Telegram group. ## How it works 1. Polls Google Sheets every hour for any updates in the “Check Inventory” sheet. 2. Checks whether the updated row already contains a Google Calendar Event ID. 3. If the Event ID is empty, searches Google Calendar for an existing event whose text matches the check number and backfills the found Event ID to Google Sheets. 4. If no matching calendar event exists, creates an all-day Google Calendar event using the check date and details from the Google Sheets row, then writes the new Event ID back to the sheet. 5. If an Event ID exists, fetches the corresponding Google Calendar event and compares its date, summary, and description to the latest Google Sheets values. 6. When differences are detected, updates the Google Calendar event to match the sheet and sends a Telegram message summarizing the created or updated events. ## Setup 1. Connect credentials for Google Sheets (including Google Sheets Trigger), Google Calendar OAuth2, and a Telegram Bot API account. 2. Replace `YOUR_CHECK_INVENTORY_SHEET_ID` in all Google Sheets nodes and ensure the “Check Inventory” sheet contains the required columns (including “Check Number” and “Event ID”). 3. Set the target Google Calendar ID (for example `[email protected]` or a shared calendar ID) in the Google Calendar nodes. 4. Replace `YOUR_TELEGRAM_GROUP_CHAT_ID` in the Telegram nodes and edit the message text to use the correct @mentions for your team.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Jira MCP server

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Create Jira ticket

Block 2 - Add Comment to Jira Ticket

Block 3 - Get Ticket transitions

Block 4 - Add Attachment to Jira TIcket

Block 5 - Change Jira Ticket Status

Block 6 - Jira MCP Server

Block 7 - Get Issue

Block 8 - Get Projects and Issue Types

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions