Skip to content

Add bitwarden-atlassian-tools plugin with MCP server and sprint analysis#54

Draft
SaintPatrck wants to merge 6 commits intomainfrom
plugins/sprint-tools
Draft

Add bitwarden-atlassian-tools plugin with MCP server and sprint analysis#54
SaintPatrck wants to merge 6 commits intomainfrom
plugins/sprint-tools

Conversation

@SaintPatrck
Copy link
Contributor

@SaintPatrck SaintPatrck commented Feb 20, 2026

🎟️ Tracking

N/A - Proposing a new addition to the plugin marketplace

📔 Objective

Tip

Best reviewed in chunks by viewing each commit individually.
Reference MCP servers as code and MCP composition as pipeline infrastructure for in-depth benchmarking metrics and practical use-case examples.

Summary

  • Replaces the old atlassian-reader plugin with a new bitwarden-atlassian-tools plugin that provides read-only Atlassian access via a custom MCP server instead of curl-based commands
  • Adds 14 MCP tools for Jira and Confluence (issues, sprints, boards, pages, search via JQL/CQL, attachments)
  • Adds sprint workability analysis with parallel ticket investigation, workability categorization (BLOCKED, STALLED, NEEDS_CLARIFICATION, IN_PROGRESS), and flexible reporting
  • Includes 7 skills, 2 agents (ticket-investigator, curl-ticket-investigator), and a /sprint-review slash command

What changed

Removed:

  • plugins/atlassian-reader/ - old curl-based plugin

Added:

  • plugins/bitwarden-atlassian-tools/ - new MCP-based plugin (v1.0.0)
    • MCP server (mcp/bitwarden-atlassian-mcp-server/): TypeScript MCP server with Jira and Confluence API clients, authentication, 14 read-only tools, input validation, and filesystem utilities
    • Skills: atlassian-reader, sprint-workability, parsing-sprint-data, categorizing-workability, analyzing-requirements, generating-report (with reference docs)
    • Agents: ticket-investigator (MCP-based) and curl-ticket-investigator (curl based investigator for benchmark comparisons) for parallel ticket analysis
    • Command: /sprint-review with source, sprint, platform, status, output, and file arguments
  • Updated marketplace registry and root README

Test plan

  • Set Jira/Confluence env vars and verify MCP server starts (npx tsx src/index.ts)
  • Test individual MCP tools (get_issue, search_issues, get_confluence_page, etc.)
  • Run /sprint-review against a real Confluence sprint planning page
  • Verify ticket-investigator agent can analyze tickets in parallel
  • Confirm atlassian-reader skill triggers on Jira ticket mentions
  • Validate plugin structure: ./scripts/validate-plugin-structure.sh bitwarden-atlassian-tools
  • Validate marketplace: ./scripts/validate-marketplace.sh bitwarden-atlassian-tools

SaintPatrck and others added 6 commits February 19, 2026 13:44
Replaced by the new bitwarden-atlassian-tools plugin which provides
MCP-based Atlassian access instead of curl-based commands.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Foundation for the bitwarden-atlassian-mcp-server with Jira and
Confluence API clients, authentication modules, type definitions,
and shared utilities for validation and filesystem operations.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
14 read-only tools: get_issue, search_issues, get_issue_comments,
download_attachment, list_boards, get_sprints, get_sprint_issues,
list_projects, get_confluence_page, search_confluence,
search_confluence_cql, get_confluence_page_comments, get_child_pages,
and list_spaces.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Plugin configuration with v1.0.0 manifest, MCP server binding,
ticket-investigator and curl-ticket-investigator agents for parallel
ticket analysis, and /sprint-review slash command.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Seven skills: atlassian-reader for Jira/Confluence data access,
sprint-workability for orchestration, plus supporting skills for
parsing sprint data, categorizing workability, analyzing requirements,
and generating reports with reference materials.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Plugin documentation, consolidated v1.0.0 changelog, and marketplace
registry entry for the new bitwarden-atlassian-tools plugin.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions
Copy link

Logo
Checkmarx One – Scan Summary & Details29c7ef3b-1cb8-4591-ad93-0b248b207343

New Issues (2)

Checkmarx found the following issues in this Pull Request

# Severity Issue Source File / Package Checkmarx Insight
1 HIGH CVE-2025-66414 Npm-@modelcontextprotocol/sdk-0.6.1
detailsRecommended version: 1.26.0
Description: MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. Prior to 1.24.0, The Model Context Protocol (MCP)...
Attack Vector: NETWORK
Attack Complexity: LOW
Vulnerable Package
2 HIGH CVE-2026-0621 Npm-@modelcontextprotocol/sdk-0.6.1
detailsRecommended version: 1.26.0
Description: Anthropic's MCP TypeScript SDK versions through 1.25.1 contain a Regular Expression Denial-of-Service (ReDoS) vulnerability in the "UriTemplate" cl...
Attack Vector: NETWORK
Attack Complexity: LOW
Vulnerable Package

Copy link
Contributor

@theMickster theMickster left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really like the direction here—would you be open to narrowing this PR to a Jira-focused MVP (ticket retrieval/read operations) and then layering in Confluence plus sprint-analysis skills/agents in follow-up PRs so we can ship value faster with smaller review scope?

SaintPatrck added a commit that referenced this pull request Mar 2, 2026
Introduce bitwarden-atlassian-tools alongside atlassian-reader, providing
a custom MCP server with read-only Jira access. First PR in a stacked
series per review feedback on PR #54. The atlassian-reader plugin is
retained until the MCP server reaches feature parity (Confluence, boards,
sprints).

Includes:
- MCP server with explicit tool registration
- Jira client layer (auth, client, types) using ATLASSIAN_* env vars
- 4 Jira tools: get_issue, get_issue_comments, search_issues, list_projects
- Plugin manifest, MCP config, README, and marketplace registry updates
SaintPatrck added a commit that referenced this pull request Mar 2, 2026
Introduce bitwarden-atlassian-tools alongside atlassian-reader, providing
a custom MCP server with read-only Jira access. First PR in a stacked
series per review feedback on PR #54. The atlassian-reader plugin is
retained until the MCP server reaches feature parity (Confluence, boards,
sprints).

Includes:
- MCP server with explicit tool registration
- Jira client layer (auth, client, types) using ATLASSIAN_* env vars
- 4 Jira tools: get_issue, get_issue_comments, search_issues, list_projects
- Plugin manifest, MCP config, README, and marketplace registry updates
SaintPatrck added a commit that referenced this pull request Mar 2, 2026
Introduce bitwarden-atlassian-tools alongside atlassian-reader, providing
a custom MCP server with read-only Jira access. First PR in a stacked
series per review feedback on PR #54. The atlassian-reader plugin is
retained until the MCP server reaches feature parity (Confluence, boards,
sprints).

Includes:
- MCP server with explicit tool registration
- Jira client layer (auth, client, types) using ATLASSIAN_* env vars
- 4 Jira tools: get_issue, get_issue_comments, search_issues, list_projects
- Plugin manifest, MCP config, README, and marketplace registry updates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants