Jira MCP in Cursor

Purpose

Model Context Protocol (MCP) lets an AI assistant in Cursor read Jira issues and related context while you work. That helps you align drafts with the Jira user story skill and the User story layout: pull live summaries, acceptance criteria, or links without copy-pasting everything.

The exact MCP server (name, package, or binary) depends on how your organisation runs Jira and which server you choose. This page describes how to wire a server safely in Cursor; it does not pin a single third-party implementation.

Prerequisites

• Access to Jira (Cloud or Data Center) with the permissions you need for the issues you want the agent to see.
• API credentials as required by your MCP server: often a Personal Access Token (PaaS/Cloud) or API token plus site URL; some setups use OAuth. Follow the server’s documentation.
• Cursor with MCP support enabled (see Cursor MCP documentation).

Cursor MCP basics

1. Open Cursor Settings and find MCP (or Features → Model Context Protocol), or edit your MCP config file as described in the Cursor MCP docs.
2. Add a server entry. Typical pattern:
   • Command: path to npx, node, or a dedicated binary, depending on the server.
   • Args: package name or script path, as documented by the server.
   • Environment variables: set JIRA_* or names the server documents (site URL, email, token, etc.). Prefer environment or Cursor’s secret storage; never commit values to git.

Server-specific setup

1. Choose an MCP server that integrates with Jira and your deployment model (Cloud vs on‑prem). Check Atlassian’s documentation and developer.atlassian.com for Jira REST API and authentication options.
2. If your organisation provides a standard MCP server for Jira, use that and its env vars.
3. If you use a community or npm package, read its README for required env keys and scopes; rotate tokens if you change servers.

Security

• Store tokens and passwords only in environment variables, Cursor’s secret store, or your OS keychain—not in the repo.
• Do not commit .env, mcp.json fragments with secrets, or screenshots of tokens.
• Rotate credentials immediately if they are exposed or leaked.
• Grant least privilege: tokens should only access the Jira projects and operations the MCP server needs.

Troubleshooting

Related

• Analysis introduction
• User story layout
• Jira user story skill
• Figma MCP in Cursor