get-issue

Retrieve Jira issues by key or JQL via MCP Atlassian integration.

2|Updated Apr 11, 2026

Search Tags:#integration #mcp #issues #jira #atlassian #jql

Ready to run

npx skills add https://github.com/JaimeJunr/context-mode --skill get-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: get-issue
Source: https://github.com/JaimeJunr/context-mode/tree/main/.claude/skills/get-issue
Command: npx skills add https://github.com/JaimeJunr/context-mode --skill get-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly locate Jira issues by key or via JQL, avoiding manual lookups and speeding up triage and planning.

Core Features & Use Cases

Lookup by issue key using the MCP Atlassian tools to retrieve fields such as summary, status, and assignee.
Perform JQL-based searches to list multiple issues across projects and boards.
Retrieve the necessary cloudId via getAccessibleAtlassianResources and handle common errors (401/403/404) gracefully.
Contextual guidance for CAP/InvestTools projects and typical issue workflows (Todo, Doing, Concluído).

Quick Start

Ask me to fetch a Jira issue by key such as CAP-123 or to run a JQL query to list matching issues.

Frequently Asked Questions about get-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fetch Jira issues by key or JQL using MCP?▼

To fetch Jira issues by key or JQL using MCP, retrieve the cloudId via getAccessibleAtlassianResources, then query a single issue by key or multiple issues via a JQL query to return fields like summary, status, and assignee.

Can I search multiple Jira projects with a JQL query through Atlassian MCP?▼

Yes, you can search multiple Jira projects with a JQL query through Atlassian MCP by executing JQL-based searches to list matching issues across projects and boards after obtaining the necessary cloudId.

What fields are returned when I retrieve a Jira issue with this MCP integration?▼

When you retrieve a Jira issue with this MCP integration, it provides fields like summary, status, and assignee when available, alongside standard contextual guidance for typical issue workflows.

Why does my Jira issue lookup fail with a 404 error using MCP?▼

Your Jira issue lookup fails with a 404 error using MCP when the requested issue key does not exist or the cloudId is invalid, which the skill handles gracefully alongside common 401 and 403 authentication errors.

Do I need to manually find my Atlassian cloudId before querying Jira issues?▼

No, you do not need to manually find your Atlassian cloudId before querying Jira issues, because the skill automatically retrieves it using the getAccessibleAtlassianResources MCP tool prior to executing your JQL search or key lookup.