Resources · Zapier integration

Atlassian MCP Zapier integrationAutomate Atlassian MCP with Zapier.

The Atlassian MCP Zapier integration brings 2 triggers, 4 actions and 8 searches around your Jira issues: spot new or updated tickets, create, edit, comment on and move them, and look up projects, users and transitions on your Atlassian Cloud site.

See the 14 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Atlassian MCP Zapier integration does

Atlassian MCP is a cloud bridge between your Atlassian Cloud site and outside tools. On Zapier, it shows up as a Jira toolkit: it notices new and updated issues, writes to them, and answers questions about your projects, issue types, users and workflow transitions, so a Zap knows what it can do before it does it.

Three outcomes justify setting it up.

Tickets that triage themselves. New Jira Issue watches a project, and Comment on Jira Issue posts the checklist your team always forgets, or Transition Jira Issue moves the ticket into the right column.

Issues created from anywhere. A form, a support inbox or a chat message in another app becomes a proper ticket through Create Jira Issue. List Jira Projects and List Project Issue Types give you the keys it asks for.

Workflows that respect your board. Before moving a ticket, List Jira Issue Transitions tells the Zap which moves are allowed from its current status, so the step does not fail on a forbidden one.

What Zapier does not do here: both triggers are polling triggers, so nothing is instant; there is no delete action; and the only Confluence access is reading a page with Fetch Content with ARI. Nothing on Zapier writes to Confluence through this app. To weigh Zapier against the alternatives, n8n vs Zapier and Make vs Zapier set the criteria side by side.

Vocabulary

Zapier vocabulary in one minute

Seven Zapier words, plus Jira's own jargon, run through this page. The Zapier ones, in plain English:

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event before doing anything.
Action
What the Zap does once it has started: the step that creates, edits, comments or moves something for you.
Task
The unit Zapier bills: one action the Zap completed successfully. Your plan allowance counts those, and nothing else.
Polling vs instant
Zapier checks a polling trigger on a timer and keeps only what it has not seen. An instant trigger is pushed by the app the moment it happens.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set, and stops the run otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
Cost

What an Atlassian MCP Zap costs

Zapier checking Jira for new issues costs nothing. Only an action that succeeds uses a task.

  • Premium appNo, free plan accepted
  • Free plan100 tasks a month, two-step Zaps
  • Triggers2 polling, 0 instant
  • BilledEach successful action, separately

Atlassian MCP is not a premium app, so it runs on the free plan: 100 tasks a month, unlimited Zaps, two steps per Zap, and a check for new issues every 15 minutes. With eight searches on offer, watch the step count: adding a search, a filter or a second action makes a multi-step Zap, which needs a paid plan. Every successful action counts separately, so commenting and then transitioning a ticket is two tasks. A failed action is not counted.

Connect

Connect Atlassian MCP to Zapier

  1. 01

    Open the Apps page

    In Zapier, go to Apps and click + Add connection. A connection is your Atlassian account linked to Zapier once, then reused by every Zap that works on your Jira site.

  2. 02

    Find Atlassian MCP

    Search for Atlassian MCP in the dialog, pick it, and click Add connection. A new tab opens on the Atlassian side, where you sign in with your Atlassian account.

  3. 03

    Sign in and grant access

    Log in with the Atlassian account the Zap should act as, then allow Zapier access. You need your own account, plus read or write access on every project you do not own but want the Zap to touch.

First Zap

Your first Zap: bugs that arrive with a triage checklist

GoalWhen a new bug is created in your support project, post the triage checklist on it and move it to the triage status.

  1. 01

    Build: pick the trigger

    Create a Zap, choose Atlassian MCP and New Jira Issue. Enter your Cloud ID, then a JQL query (Jira's search language) that limits it to bugs in your support project.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent matching issues. Pick a real bug, since the comment and the move will be mapped on its key.

  3. 03

    Post the checklist

    Add Comment on Jira Issue, map the issue key from the trigger, and write the checklist in the comment body. Markdown formatting is accepted.

  4. 04

    Move it to triage

    Add Transition Jira Issue with the same key and the triage transition. This second action makes it a multi-step Zap, so a paid plan is needed.

  5. 05

    Test, then Publish

    Test both actions and check the bug in Jira: one comment, new status. Then click Publish to switch the Zap on and let it run.

Triggers

Atlassian MCP triggers on Zapier

2 events start a Zap when something happens in Atlassian MCP. Zapier checks for them at the interval your plan allows.

1

New Jira Issue

Polling trigger

In Zapier“Triggers when a new Jira issue is created. Use JQL for advanced filtering or leave blank for basic filtering.”

Picks up each issue created on your Jira site. You can narrow it with a JQL query, Jira's own search language, or leave that blank and settle for the basic filtering it offers.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
every new bug in the mobile app project should get a comment with the reproduction checklist.
Watch out
the Cloud ID is required; without a JQL query, the Zap may react to issues from projects you never meant to watch.
2

Updated Jira Issue

Polling trigger

In Zapier“Triggers when an existing Jira issue is updated.”

Fires when an existing issue changes on your Jira site. Any edit counts as an update, which makes it a wide net to cast across a busy board.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a product manager wants a message elsewhere each time a ticket on the roadmap board is edited.
Watch out
answering this trigger with Update Jira Issue on the same ticket edits it again, and the Zap can loop until your tasks run out.
Actions

Atlassian MCP actions on Zapier

Atlassian MCP gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Comment on Jira Issue

Action

In Zapier“Add a rich-text comment to an existing Jira issue.”

Adds a formatted comment to a ticket that already exists, written in Markdown so lists and links survive.

When to use it
a deployment tool reports a release, and the related tickets get a note saying which version shipped the fix.
Watch out
the issue ID or key is required; an issue key looks like a project key, a hyphen, then a number, as in ISSUE-1.
2

Create Jira Issue

Action

In Zapier“Create a new Jira issue with summary, assignee details, and custom fields.”

Opens a new ticket in the project you name, with a summary, an issue type, an assignee and custom fields if your project uses them.

When to use it
a bug report form on your site should become a Jira bug without anyone retyping it.
Watch out
the project key, issue type and summary are required; get the first two from List Jira Projects and List Project Issue Types.
3

Update Jira Issue

Action

In Zapier“Update an existing Jira issue's fields such as summary, description, or custom values.”

Edits an existing ticket: its summary, its description or its custom values, pointed to by the issue ID or key.

When to use it
a customer adds details to a support request in another tool, and the Jira description should catch up.
Watch out
inside a Zap triggered by Updated Jira Issue, editing the same issue restarts the Zap.
4

Transition Jira Issue

Action

In Zapier“Move a Jira issue to a new status and include any required transition fields.”

Moves a ticket to a new status through your workflow, filling any fields that transition demands.

When to use it
a merged pull request in another tool should push the ticket from in review to done.
Watch out
the moves on offer depend on the issue's current status; run List Jira Issue Transitions first if the status varies.
Searches

Atlassian MCP searches on Zapier

8 search steps look for data that already exists in Atlassian MCP, so a later step can use it.

A search step looks up something that already exists so the next steps can use it. Searches sit at the bottom of the action list, under SEARCH, and some fields offer + Add search step to slip one in just before. Each search is a step, so a Zap that uses one is multi-step and needs a paid plan. How close a match has to be is decided by Atlassian, not by Zapier. None of these eight searches has a find-or-create variant.

1

Fetch Content with ARI

Search

In Zapier“Fetch a Jira issue or Confluence page directly by its Atlassian Resource Identifier (ARI).”

Pulls a Jira issue or a Confluence page straight from its Atlassian Resource Identifier, the ARI.

When to use it
a Zap receives an ARI from another tool and needs the page or ticket behind it.
Watch out
it is the only operation here that reads Confluence, and it reads, it never writes.
2

Retrieve Jira Issue

Search

In Zapier“Retrieve the latest details for a Jira issue by key or ID.”

Gets the latest details of one ticket from its key or ID, with its update history on request.

When to use it
a client asks about ticket progress in your helpdesk, and the reply needs the current status from Jira.
Watch out
returning field names as keys reads better but may break steps that expect IDs, as Atlassian warns in the field help.
4

List Project Issue Types

Search

In Zapier“List the issue types available in a Jira project and review required fields for each type.”

Lists the issue types of a project and the required fields of each, which is what Create Jira Issue needs to succeed.

When to use it
your teams rename or add issue types, and a creation Zap must keep working.
Watch out
it takes a project key; the key is more readable than the numeric project ID.
5

List Jira Issue Transitions

Search

In Zapier“List the workflow transitions currently available for the selected Jira issue, including required fields.”

Shows which workflow moves are open for a given ticket right now, along with the fields each one asks for.

When to use it
right before Transition Jira Issue, when tickets reach the Zap in different statuses.
Watch out
it can also list moves that are not available yet, which a later step must not try to use.
6

List Jira Projects

Search

In Zapier“Discover Jira projects you can access along with their keys and details.”

Discovers the Jira projects your connected account can see, with their keys and, on request, their issue types.

When to use it
an agency running one project per client needs the right project key before creating a ticket.
Watch out
it only lists what the connected account can access, so check the account's rights if a project is missing.
7

Find Jira Users

Search

In Zapier“Search for Jira users by name or email to get their account IDs.”

Searches Jira users by display name or email and returns their account IDs.

When to use it
a form names the developer on duty, and the new ticket must be assigned to that person.
Watch out
partial matches work, so a short search term may match several people; set the multiple-results option carefully.
8

Search Jira Issues with JQL

Search

In Zapier“Run an advanced JQL query to find Jira issues that match your specific filters.”

Runs a JQL query and returns the tickets that match, from one project or across the whole site.

When to use it
when a customer writes in, the Zap checks whether an open ticket already exists for that account.
Watch out
the query is required and follows Jira's syntax, such as project = PROJ; test it in Jira first.

The three settings every search exposes

  1. Successful if no search results are found?
    On its default, a search that comes back empty stops the Zap there and skips the steps that rely on it. Switched on, the Zap carries on without a result.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create and asks for the fields needed to create the missing item. No Atlassian MCP search offers it.
  3. If multiple search results are found?
    Three exits when several items match: keep the first one, which is the default, stop the Zap, or pass them all on to the next step.
When it breaks

When an Atlassian MCP Zap breaks

Zapier links no help article to Atlassian MCP. The failures below come from the way Zapier works, applied to Jira.

On this app, watch two spots first: the update trigger, and transitions that do not exist from the current status. The Zapier troubleshooting page covers the general cases.

  • The update loop

    Updated Jira Issue followed by an edit on the same ticket changes it again, and the next check sees a new update. The Zap loops and burns tasks.

  • Old tickets never come through

    A Zap only reacts to issues created or updated after you publish it. The existing backlog is not picked up; moving it is a separate job.

  • A transition refused

    Available moves depend on the ticket's current status. A Zap that always asks for the same transition fails on tickets already elsewhere in the workflow.

  • A bulk import held back

    Importing or migrating a large batch of issues can make the trigger return a huge set at once, and Zapier's flood protection may hold those runs back.
Need help

Need help automating Atlassian MCP with Zapier?

A person reads every message.

FAQ

Atlassian MCP Zapier integration: frequent questions

01Is the Atlassian MCP Zapier integration free?
Yes, within the limits of the free plan. Atlassian MCP is not a premium app, so the free plan accepts it with 100 tasks a month and unlimited Zaps. The catch is the two-step rule: one trigger and one action. A Zap that comments and then moves a ticket uses two actions, so it needs a paid plan. The same goes for any of the eight searches, or a filter, since each one adds a step to the Zap.
02How many tasks does an Atlassian MCP Zap use?
One task per action that succeeds, each time the Zap runs. The trigger is free, and Zapier checking Jira for new or updated issues never costs a task either. A Zap that comments on a new bug and transitions it spends two tasks per bug. A failed action, such as a refused transition, is not counted. To estimate your usage, multiply the actions in the Zap by the tickets you expect it to handle.
03Are Atlassian MCP triggers real-time?
No. Both triggers, New Jira Issue and Updated Jira Issue, are polling triggers: Zapier asks Jira for news at a fixed interval set by your plan. That is every 15 minutes on Free, 2 minutes on Professional, and 1 minute on Team and Enterprise. Zapier keeps track of what it has already seen, so the same issue does not start the Zap twice. A paid plan can also run a check by hand from the editor.
04What do you need to connect Atlassian MCP to Zapier?
An Atlassian account with access to the Jira projects the Zap will work on, plus read or write access on any project you do not own. The connection starts on the Apps page with + Add connection, then you sign in to Atlassian in the tab that opens and grant access. Every operation then asks for your Atlassian Cloud ID, which can be the site UUID or its address, such as yoursite.atlassian.net.
05Why does Transition Jira Issue fail on some tickets?
Because the transitions available depend on the ticket's current status. A Jira workflow only allows certain moves from each status, so a Zap that always asks for the same transition breaks on tickets that already sit elsewhere. Put List Jira Issue Transitions just before the move to see what is allowed. Some transitions also require fields of their own, and that search lists them too, so the action can be filled correctly.
06What if the Atlassian MCP operation you need is not there?
Then Zapier does not offer it as a ready-made step today. This app covers Jira issues: two triggers, four actions to create, edit, comment and move tickets, and eight searches. There is no delete action and no way to write to Confluence; Confluence pages can only be read through Fetch Content with ARI. In that case, get help designing a workaround around the steps that do exist, or compare what other automation tools offer for Jira.
07Zapier, Make or n8n for Atlassian MCP?
Pick by criterion, not by ranking. Coverage first: on Zapier, this app gives two triggers, four actions and eight searches around Jira issues, so check that whatever tool you compare offers the same operations. Billing next: Zapier counts one task per successful action, and the trigger is free. Speed last: both triggers poll, so the free plan waits up to 15 minutes, which matters if your support process is time-sensitive.
Same platform

Other docs you might need on this stack.

Browse all integrations