# Jira setup for PopMCP You enter three values into PopMCP: your Jira Cloud site (yourcompany.atlassian.net), the email you sign in to Atlassian with, and an Atlassian API token, either a classic one or one with scopes. - Auth: API credentials - Setup time: 4 min - API base URL: https://YOUR-SITE.atlassian.net/rest/api/3 - Credentials screen: https://id.atlassian.com/manage-profile/security/api-tokens - Provider docs: https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/ ## Before you begin - A Jira Cloud site on atlassian.net. Jira Server and Jira Data Center are not supported - An Atlassian account that can open Jira on that site. The MCP works as this account and sees only what it can see - Access to the inbox of your Atlassian email: if you sign in with a password or a third-party login, Atlassian emails a one-time code before it lets you create a token - Permission to create API tokens. An organization admin can block them for managed accounts through an authentication policy ## Get your credentials ### 1. Copy your Jira site address Open Jira in your browser and copy the host from the address bar, for example `yourcompany.atlassian.net`. The name on its own (`yourcompany`) is enough for PopMCP. Older sites that still answer on `yourcompany.jira.com` work too. Screen: https://YOUR-SITE.atlassian.net (replace YOUR-SITE with your Jira site) ### 2. Open API tokens in your Atlassian account Go to `id.atlassian.com`, open Security and click Create and manage API tokens, or use the direct link. If Atlassian asks you to verify your identity, enter the one-time code it emails you. Screen: https://id.atlassian.com/manage-profile/security/api-tokens ### 3. Create a classic API token Click Create API token. Name it `PopMCP`, choose an expiry date between 1 and 365 days from today, and click Create. When the token expires, the connection stops working until you paste a new one. Screen: https://id.atlassian.com/manage-profile/security/api-tokens ### 4. Copy the token Click Copy to clipboard in the dialog. Tokens created now start with `ATATT`. Atlassian does not show the token again, so paste it somewhere safe or straight into PopMCP. Screen: https://id.atlassian.com/manage-profile/security/api-tokens ### 5. Or create a token with scopes To limit what the MCP can do, click Create API token with scopes instead. Name it and set its expiry, choose Jira as the app, then tick the scopes the tools need: `read:jira-work` and `read:jira-user` for reading, `write:jira-work` to create and change issues, the Jira Software scopes such as `read:board-scope:jira-software` and `read:sprint:jira-software` for boards and sprints, and `read:servicedesk-request` for service desks. Click Create and copy the token. PopMCP detects a scoped token when you connect and sends it through Atlassian's API gateway, which is the only place Atlassian accepts it. Screen: https://id.atlassian.com/manage-profile/security/api-tokens ### 6. Enter the three values in PopMCP In PopMCP, fill in Jira site with your site address, Atlassian email with the email you sign in to Atlassian with, and API token with the token you copied. Connect, and PopMCP checks the token against your site (and Atlassian's API gateway for a scoped token) straight away. ## Fields PopMCP asks for - Jira site (site) [required]: The address you open Jira at. The name on its own (yourcompany) works too. - Atlassian email (email) [required]: The email you sign in to Atlassian with. The MCP works as this person and sees only what they can see in Jira. - API token (apiToken) [required]: At id.atlassian.com go to Security, then Create and manage API tokens, then Create API token. Name it PopMCP, choose when it expires (a year at most) and copy it. A token with scopes works too: give it the Jira scopes the MCP should use. Stored encrypted. ## Verify PopMCP marks the Jira connection Verified, labelled with your site (yourcompany.atlassian.net) and a note saying which Atlassian user it acts as. For a scoped token it also notes that Jira only allows what the scopes cover. Asking the AI for your open issues returns real issue keys such as PAY-142. ## Troubleshooting ### "Jira rejected that email and API token for yourcompany.atlassian.net." Cause: The email is not the one the Atlassian account signs in with, the token was copied incompletely or has expired, or the account cannot open Jira on that site. Fix: Check the email under **Email** in your Atlassian account, create a fresh token and paste it in one piece, and confirm you can open Jira on that site in your browser. ### "There is no Jira Cloud site at yourcompany.atlassian.net." Cause: The site name is mistyped or belongs to a different Atlassian organization. Fix: Copy the host from your browser's address bar while Jira is open and paste it into **Jira site**. ### "yourcompany.atlassian.net is an Atlassian site, but Jira did not answer there." Cause: The site exists but has no Jira product on it, for example a Confluence-only site. Fix: Use the site where your Jira projects live. Its address is in the browser when you open a Jira board or issue. ### The site address is refused as "not a Jira Cloud site" Cause: The address is a Jira Server or Data Center host, or anything other than an atlassian.net (or older jira.com) site. Fix: This connector works with Jira Cloud only. Enter your site's atlassian.net address. ### Some tools answer 401 while others work Cause: The connection uses a token with scopes, and those tools need a scope it was not given. Fix: Create a new token with the missing scopes (or a classic token) and reconnect Jira with it. ### 403 on a project, board or admin tool Cause: Your Atlassian account lacks the Jira permission that operation needs, such as Browse projects, Administer projects or Jira administrator. Fix: Ask a Jira admin to grant the permission, or connect with the account of someone who has it. jira_describe_tool shows the permission a tool needs. ### There is no way to create an API token, or a working token suddenly stops Cause: Your organization admin blocks API tokens for managed accounts through an authentication policy, or the token reached its expiry date (one year at most). Fix: Ask your Atlassian organization admin to allow API tokens for your account, or create a new token and reconnect. --- Source: https://www.docs.popmcp.com/docs/integrations/jira/