Documentation Index
Fetch the complete documentation index at: https://developer.suki.ai/llms.txt
Use this file to discover all available pages before exploring further.
Jira MCP Setup Guide for Cursor
This guide helps you add the Atlassian Jira MCP server to Cursor so you can create and manage Jira tickets from the AI assistant.Prerequisites
- Node.js 18 or higher
- Jira Cloud account (this MCP supports Jira Cloud only, not self-hosted)
- Atlassian API token
Step 1: Create an Atlassian API Token
- Go to Atlassian API Tokens
- Click Create API token
- Give it a label (e.g.,
Cursor MCPorJira AI) - Click Create
- Copy the token immediately — you won’t be able to see it again
Step 2: Find Your Jira Site Name
Your site name is the first part of your Jira URL:| Jira URL | Site Name |
|---|---|
https://mycompany.atlassian.net | mycompany |
https://acme-corp.atlassian.net | acme-corp |
Step 3: Add Jira MCP to Cursor
Option A: Edit config file directly
-
Open your Cursor MCP config:
- macOS/Linux:
~/.cursor/mcp.json - Windows:
%USERPROFILE%\.cursor\mcp.json
- macOS/Linux:
-
Add the
jiraserver to themcpServersobject. Your config should look like:
- Replace the placeholders:
your-company→ Your Jira site name (e.g.,sukiforsuki.atlassian.net)your.email@company.com→ Your Atlassian account emailyour_api_token→ The API token from Step 1
Option B: Use Cursor Settings UI
- Open Cursor Settings (Cmd+, or Ctrl+,)
- Go to Tools & Integrations → MCP Servers
- Click Add new MCP server
- Configure the Jira server with the same values as above
Step 4: Restart Cursor
Restart Cursor (or reload the window) for the new MCP to load.What You Can Do
Once configured, you can ask the AI to:- Create tickets: “Create a Jira task in project DEV: Fix login bug”
- Search issues: “Find all high priority issues in the PLATFORM project”
- Get issue details: “Show me details about PROJ-123”
- Add comments: “Add a comment to PROJ-456: Code review completed”
- Update issues: “Update status of PROJ-123 to In Progress”
Troubleshooting
”Authentication failed” or “403 Forbidden”
- Verify your API token is active at Atlassian API Tokens
- Ensure site name is correct (no
.atlassian.net, just the subdomain)
“Resource not found” or “404”
- Use project keys (e.g.,
DEV) not project names - Issue keys include the project prefix (e.g.,
DEV-123)
Test your connection
Run this in terminal to verify credentials:Alternative: Full Atlassian MCP (Confluence + Jira)
If you need Confluence as well as Jira, use mcp-atlassian. It requires running a separate server:- Clone and run the server:
- Add to config with
streamable-http: