Reported issues for mcp-atlassian-extended

Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to mcp-atlassian-extended.

Most discussed

API gap coverage: Jira metadata + Confluence navigation gaps

Summary

Gap analysis against Jira REST API v3 and Confluence REST API v2 identified tools missing from mcp-atlassian-extended that are NOT covered by base mcp-atlassian. Current tool count: 23 (17 Jira + 6 Confluence).

Base mcp-atlassian (v0.16.1) already covers: 52 Jira tools (including get_project_components, watchers, get_issue_images, service desk, ProForma, dev info) + 16 Confluence tools (including get_page_images).

Jira Gaps

HIGH Priority (10 tools)

The biggest g

Read the thread · 2026-02-27 · open · 0 comments

feat: Add MCP prompts for multi-tool workflow templates

Summary

Add MCP prompts — reusable message templates that clients surface as slash commands. The server currently has 23 tools and 15 resources but zero prompts. Prompts provide opinionated multi-tool workflows that guide users through common Jira and Confluence operations.

Motivation

MCP prompts let server authors define structured, multi-step workflows that compose existing tools. Instead of users manually orchestrating tool calls for ticket creation with custom fields, sprint plannin

Read the thread · 2026-02-24 · closed · 0 comments

MCP Builder Compliance: Nice-to-Have Polish

Context

Quality-of-life improvements from MCP Builder skill gap analysis.

Scope

1. Pagination Wrapper

Standardize list responses with {items, count, total, has_more}.

2. openWorldHint Annotation

Add "openWorldHint": True to all tool annotations.

3. README Enrichment

Add: Usage Examples, Security Considerations, Rate Limits, Required Permissions.

4. Evaluation Suite

10 read-only eval questions for Jira/Confluence tool composition.

Acceptance Criteria

• Al

Read the thread · 2026-02-23 · closed · 0 comments

MCP Builder Compliance: Immediate Fixes

Context

Gap analysis against the Anthropic MCP Builder skill identified gaps affecting correctness, security, and quality of service.

Scope

1. Resource Content Enrichment

Enrich all 15 resource constants in src/mcp_atlassian_extended/servers/resources.py with missing operational sections (error recovery, edge cases, operational guidance).

2. Input Validation

Add Field() constraints across server modules:

• issue_key: min_length=1, pattern=r"^[A-Z]+-\d+$"
• project_key

Read the thread · 2026-02-23 · closed · 0 comments

feat: Add Homebrew tap support for mcp-atlassian-extended

Summary

Add Homebrew tap support so users can install mcp-atlassian-extended via brew install vish288/tap/mcp-atlassian-extended instead of requiring uvx or pip install.

Motivation

• Homebrew is the standard package manager on macOS — brew taps integrate with the existing developer workflow
• uvx mcp-atlassian-extended requires uv to be installed; pip install has global env pollution concerns
• A brew formula with proper dependency pinning provides reproducible installs
• Shar

Read the thread · 2026-02-23 · open · 0 comments

Add one-click install badges for VS Code and Windsurf

Summary

The README currently has a Cursor one-click install badge and a Claude Code CLI command, but VS Code and Windsurf only show a manual JSON config block.

Changes

• Add VS Code one-click install badge using vscode:mcp/install deeplink
• Split Windsurf and VS Code into separate sections with their own install methods
• Add VS Code Insiders badge variant

References

• VS Code MCP install handler docs
• [vscodemcp.com

Read the thread · 2026-02-22 · closed · 0 comments

Most recent

The remaining reports are on the project's issue tracker.