Super-charge your development workflow by asking Jira to create projects, file bugs, update tickets, and surface user data with plain-English prompts. Stop hunting through menus and let natural language keep your backlog, sprints, and permissions perfectly organized.
Instantly tap into every project, issue, user, and group in your Jira instance from Gumloop workflows.

​
What is Jira MCP?

When you create a Jira MCP node with AI, Gumloop builds a custom node that understands the Jira API. Simply describe what you want in natural language and the node translates your request into the right Jira call, returning clean structured data you can send to the rest of your workflow.

​
What Can It Do for You?

  • Spin up new projects or clone existing configurations in seconds
  • File, update, transition, or delete issues without opening Jira
  • Search projects and issues with powerful JQL filters to drive reports
  • Manage users and groups so the right people stay informed

​
Available Tools

ToolWhat It DoesExample Use
Create ProjectSet up a new Jira project for a team, client, or initiative”Create a Scrum project called ‘Website Revamp’ with key WEB and return project key and URL”
Get ProjectRetrieve metadata about a specific project”Get project MKT and return name, lead, and project type”
Update ProjectModify project details like name, lead, or description”Rename project OPS to ‘Operations Platform’ and return updated name”
Delete ProjectDelete an entire project and its issues”Delete project TEST and return confirmation message”
List ProjectsList all accessible Jira projects”List all projects I can access and return project key and name”
Get Issue Types For ProjectList valid issue types for a project”Get issue types for project ENG and return name and description”
Create IssueCreate a new issue, bug, task, or story”Create a bug in project APP with summary ‘Login button unresponsive’ and return issue key and URL”
Get IssueRetrieve full details of an issue”Get issue APP-234 and return summary, status, assignee, and created date”
Update IssueModify issue fields such as assignee, priority, or status”Set priority of issue WEB-101 to High and return new priority”
Delete IssuePermanently remove an issue”Delete issue DEM-3 and return success status”
Transition My IssueMove an assigned issue to a new status”Transition my issue ENG-77 to ‘In Progress’ and return new status”
List IssuesList issues by JQL query”List issues where project = CRM and status = ‘To Do’ returning key and summary”
Comment On IssueAdd a comment to an issue”Add comment ‘Verified in staging’ to issue CRM-89 and return comment ID”
Search IssuesSearch issues using advanced JQL”Search issues ‘project = WEB AND priority = High’ and return key, summary, and status”
Execute JqlExecute a raw JQL query”Run JQL ‘assignee = jane.doe AND updated >= -7d’ and return key and updated date”
Add User To IssueAdd a user as assignee, reporter, or watcher”Add user alex.smith as watcher to issue OPS-12 and return watchers list”
List UsersList all users with pagination”List first 100 users and return display name and email”
List GroupsList all user groups”List all groups and return group name and member count”
Create GroupCreate a new user group”Create group ‘QA Leads’ and return group name and self link”
Add User To GroupAdd a user to a specified group”Add user maria.garcia to group ‘QA Leads’ and return new member count”
Remove User From GroupRemove a user from a specified group”Remove user john.lee from group ‘Contractors’ and return new member count”
Get MyselfGet information about the authenticated user”Get my account info and return display name, email, and time zone”
Get My IssuesFetch open issues assigned to the current user”Get my open issues and return key, summary, and status”
Get My Recent ActivityView recently updated issues the user interacted with”List my recent activity and return issue key and last viewed date”
Get My PermissionsDetermine user permissions in a project”Show my permissions for project FIN and return permission and havePermission”

​
How to Use

1

Create Your Jira MCP Node

Go to your node library, search for Jira, and click “Create a node with AI”
2

Add Your Prompt

Drag the Jira node onto the canvas and write a clear, specific prompt such as “Create a bug in project APP with summary ‘Crash on save’ and return issue key and URL”.
3

Test Your Node

Run the node to verify the output. Adjust your prompt wording or requested fields if needed.
4

Save and Reuse

Once the node produces the data you expect, save it to your library and drop it into any future workflow.

​
Example Prompts

With 23 available tools, these examples showcase common use cases. Feel free to tweak names, keys, or filters to fit your workspace. 
Create a story in project `WEB` titled "Add dark mode toggle" with description "Design plus implementation" and return issue key and URL

Fetch issue from an [Issue Key] and return summary, status, reporter, and created date

Search issues "project = MKT AND labels = seo AND status = 'In Progress'" returning key, summary, and assignee

Add comment "Ready for QA" using an [Issue Key] and return comment ID and created date

List all projects I can access and return key, name, and project type

Run JQL "project = OPS AND priority = Critical ORDER BY created DESC" and return key and created date
Start with a single, specific action like “Get issue from [Issue Key]” before adding additional filters and parameters.

​
Troubleshooting

If your Jira MCP node is not producing the results you expect, try these best practices:

​
Keep Prompts Simple and Specific

  • Good: “Get issue WEB-99 and return summary and status”
  • Bad: “Get the last five issues I worked on, summarize their descriptions, and close open tickets”
While this prompt might work, it’s more efficient to break it into separate nodes. Jira MCP works best with focused, single-action prompts.

​
Match What Jira Can Do

  • Good: “Add user jane.doe as assignee to issue CRM-20”
  • Bad: “Generate a PDF report of all open bugs”
Jira MCP excels at project and issue management. For external tasks, combine it with an appropriate node like an Ask AI node in your workflow.

​
Break Complex Tasks Into Steps

Instead of trying to do everything in one prompt (which might cause timeouts or errors): 
Create a new project for the mobile team, import issues from CSV, add all iOS engineers to the project, and then move the top ten bugs into the Sprint backlog
Break this into smaller, focused nodes:
1

Step 1: Create Project

Create project from a project title input and return project key
2

Step 2: Import Issues

Create issues given issue title and summary in project [project title] and return issue keys
3

Step 3: Add Users

Add users ios.eng1 and ios.eng2 to [project title] and return confirmation
4

Step 4: Move Bugs to Sprint

Transition issues [input issue keys] to status “In Sprint” and return new status
In your workflow, connect these nodes sequentially. The project key output from Step 1 becomes the input for Step 2, and so on.

​
Focus on Data Retrieval

Jira MCP is great at getting information from your Jira workspace. For analysis or document creation, hand off the results to other nodes. Good prompt: “List issues where priority = High and return key, summary, and status”
Bad prompt: “List high-priority issues, summarize each description, and draft an email update”
Use Ask AI to summarize descriptions or craft emails after Jira MCP fetches the raw data.

​
Troubleshooting Node Creation

​
Need More Help?