# MCP Server for Jira and Confluence
A Model Context Protocol (MCP) server that integrates with Atlassian's Jira and Confluence, enabling AI assistants to interact with these tools directly.
## Features
- **Jira Integration**
- List recent issues
- View issue details including comments
- Create new issues
- Add comments to issues
- Transition issues between statuses
- **Get assigned issues** - Retrieve your assigned tickets ordered by priority and date
- **Summarize issues** - Get comprehensive issue summaries with comments and history
- **Extract Confluence and Git links** - Find all Confluence page references and Git repository URLs in issues
- **Agile/Scrum Support** - Board management, sprint tracking, daily standup summaries
- **AI-Powered Assistance** - Smart task assignment recommendations and story point estimation
- **Confluence Integration**
- List recent pages
- View page content
- Create new pages
- Update existing pages
- Add comments to pages
- Search pages using CQL (Confluence Query Language)
- Get specific pages by ID or title
- Ask questions about page content
- **AI-Powered Prompts**
- Summarize Jira issues
- Create structured Jira issue descriptions
- Summarize Confluence pages
- Generate structured Confluence content
## Installation
1. Clone the repository
2. Install dependencies using `uv`:
```bash
pip install uv
uv pip install -e .
```
## Configuration
### Environment Variables
Set the following environment variables to configure the server:
#### Jira Configuration
- `JIRA_URL`: Base URL of your Jira instance (e.g., `https://yourcompany.atlassian.net`)
- `JIRA_USERNAME`: Your Jira username/email
- `JIRA_API_TOKEN`: Your Jira API token or password
- `JIRA_PERSONAL_TOKEN`: Personal access token (alternative to username/API token)
#### Confluence Configuration
- `CONFLUENCE_URL`: Base URL of your Confluence instance (e.g., `https://yourcompany.atlassian.net/wiki`)
- `CONFLUENCE_USERNAME`: Your Confluence username/email
- `CONFLUENCE_API_TOKEN`: Your Confluence API token or password
- `CONFLUENCE_PERSONAL_TOKEN`: Personal access token (alternative to username/API token)
### Quick Setup
1. Create API tokens from your Atlassian account settings
2. Set environment variables in your shell:
```bash
export JIRA_URL="https://yourcompany.atlassian.net"
export JIRA_USERNAME="your-email@company.com"
export JIRA_API_TOKEN="your-jira-api-token"
export CONFLUENCE_URL="https://yourcompany.atlassian.net/wiki"
export CONFLUENCE_USERNAME="your-email@company.com"
export CONFLUENCE_API_TOKEN="your-confluence-api-token"
```
3. Or use the provided `run.sh` script with environment variables
## Usage
### Starting the Server
Run the server directly:
```bash
python -m mcp_jira_confluence.server
```
### VSCode MCP Extension
If using with the VSCode MCP extension, the server is automatically configured via `.vscode/mcp.json`.
### Claude Desktop
To use with Claude Desktop, add the following configuration:
On MacOS: `~/Library/Application\ Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
<details>
<summary>Development/Unpublished Servers Configuration</summary>
```json
"mcpServers": {
"mcp-jira-confluence": {
"command": "uv",
"args": [
"--directory",
"/Users/annmariyajoshy/vibecoding/mcp-jira-confluence",
"run",
"mcp-jira-confluence"
]
}
}
```
</details>
<details>
<summary>Published Servers Configuration</summary>
```json
"mcpServers": {
"mcp-jira-confluence": {
"command": "uvx",
"args": [
"mcp-jira-confluence"
]
}
}
```
</details>
## Resources
The server exposes the following types of resources:
- `jira://issue/{ISSUE_KEY}` - Jira issues
- `confluence://page/{PAGE_ID}` - Confluence pages
- `confluence://space/{SPACE_KEY}/page/{PAGE_ID}` - Confluence pages with space key
## Usage
### Available Tools
#### Jira Tools
- **`create-jira-issue`**: Create a new Jira issue
- **`comment-jira-issue`**: Add a comment to an issue
- **`transition-jira-issue`**: Change an issue's status (supports transition names like "In Progress", "Done")
- **`get-jira-transitions`**: Get available transitions for an issue
- **`get-jira-issue`**: Get detailed information about a specific Jira issue
- **`get-my-assigned-issues`**: Get issues assigned to you, ordered by priority and date
- **`summarize-jira-issue`**: Get comprehensive issue summary with comments and history
- **`extract-confluence-links`**: Find all Confluence and Git repository links in an issue
#### Agile/Scrum Tools (NEW!)
- **`get-agile-boards`**: Get all agile boards or filter by project - essential for scrum masters
- **`get-board-sprints`**: Get sprints for a specific board (active, closed, future, or all)
- **`get-daily-standup-summary`**: Comprehensive daily standup report with sprint progress, team status, and blockers
- **`get-task-assignment-recommendations`**: AI-powered assignment suggestions based on historical data and expertise
- **`estimate-story-points`**: AI-powered story point estimation using complexity analysis and historical patterns
#### Confluence Tools
- **`create-confluence-page`**: Create a new Confluence page
- **`update-confluence-page`**: Update an existing page (version auto-fetched if not provided)
- **`comment-confluence-page`**: Add a comment to a page
- **`get-confluence-page`**: Get a specific page with optional comments/history
- **`search-confluence`**: Search pages using CQL queries
- **`ask-confluence-page`**: Ask questions about page content
### Usage Examples
#### Getting Your Assigned Issues
```
Get issues assigned to you ordered by priority (highest first) and creation date (newest first):
Default (25 issues, exclude completed):
- No parameters needed
Custom parameters:
- max_results: 50 (max: 100)
- include_done: true (includes closed/resolved issues)
The tool returns issues with:
- Issue key, summary, status, priority
- Issue type, creation date, due date
- Formatted for easy reading
```
#### Getting a Specific Jira Issue
```
Get detailed information about any Jira issue by its key:
Basic issue info:
- issue_key: "PROJ-123" (required)
- include_comments: false (default)
With comments:
- issue_key: "PROJ-123"
- include_comments: true (includes last 3 comments)
Returns:
- Complete issue details (status, priority, assignee, dates)
- Full description
- Optional recent comments
- Formatted for easy reading
```
#### Summarizing a Jira Issue
```
Get comprehensive issue information including:
- Basic details (status, priority, assignee, dates)
- Full description
- Recent comments (last 5)
- Confluence page references
- Status history
Parameters:
- issue_key: "PROJ-123" (required)
Returns formatted markdown summary perfect for AI analysis.
```
#### Transitioning Issue Status
```
Change an issue's status using human-readable transition names:
Using transition name (recommended):
- issue_key: "PROJ-123"
- transition_name: "In Progress" // or "Done", "To Do", etc.
Using transition ID (advanced):
- issue_key: "PROJ-123"
- transition_id: "21"
The tool automatically:
- Finds the correct transition ID from the name
- Provides helpful error messages with available options
- Shows the new status after transition
Common transition names: "To Do", "In Progress", "Done", "Closed"
```
#### Getting Available Transitions
```
See what status changes are possible for an issue:
Parameters:
- issue_key: "PROJ-123" (required)
Returns:
- List of available transitions with names and target statuses
- Transition IDs for advanced usage
- Usage examples for each transition
- Clear formatting for easy reading
Use this before transitioning to see available options.
```
#### Extracting Links from Issues
```
Find all Confluence and Git repository links in a Jira issue from:
- Issue description text
- Comments from all users
- Remote links attached to the issue
Parameters:
- issue_key: "PROJ-123" (required)
- include_git_urls: true (default, set to false to exclude Git links)
Supported Git platforms:
- GitHub, GitLab, Bitbucket (cloud and self-hosted)
- Azure DevOps / Visual Studio Team Services
- Generic Git hosting platforms
- SSH Git URLs (git@server:org/repo.git)
Returns:
- Confluence page links with titles and context
- Git repository URLs with source location
- Organized by category (Confluence vs Git)
- Source information (description, comment, remote link)
```
#### Agile Board Management
```
Get all agile boards or filter by project:
All boards:
- No parameters needed
Project-specific boards:
- project_key: "PROJ" (optional filter)
Returns:
- Board ID, name, type (Scrum/Kanban)
- Associated project information
- Essential for scrum masters managing multiple teams
```
#### Sprint Management
```
Get sprints for a specific agile board:
Active sprints only (default):
- board_id: "123" (required)
All sprint states:
- board_id: "123"
- state: "all" (options: "active", "closed", "future", "all")
Returns:
- Sprint ID, name, state, dates
- Sprint goals and progress information
- Perfect for sprint planning and retrospectives
```
#### Daily Standup Summary (Scrum Masters)
```
Get comprehensive daily standup report for active sprint:
Parameters:
- board_id: "123" (required - get from get-agile-boards)
Returns detailed analysis:
- Sprint progress (issues & story points completion %)
- Status breakdown (To Do, In Progress, Done, etc.)
- Team member workload and current tasks
- Potential blockers (high priority unresolved issues)
- In-progress tasks by assignee
- Key metrics for standup discussion
Perfect for scrum masters to quickly assess sprint health!
```
#### AI-Powered Task Assignment
```
Get smart recommendations for who should work on a task:
Parameters:
- issue_key: "PROJ-123" (required)
AI analyzes:
- Historical data from similar resolved issues
- Team member expertise in components/labels
- Current workload of potential assignees
- Average resolution times for similar work
- Component and technology experience
Returns:
- Ranked list of recommended assignees
- Confidence scores and reasoning
- Current workload information
- Historical performance data
```
#### AI-Powered Story Point Estimation
```
Get intelligent story point estimates based on complexity and history:
Parameters:
- issue_key: "PROJ-123" (required)
AI analyzes:
- Issue complexity (description length, components, labels)
- Historical data from similar resolved issues
- Story point patterns in your project
- Component and issue type complexity
Returns:
- Primary recommendation with confidence level
- Alternative estimates for team discussion
- Complexity analysis breakdown
- Similar issues for reference
- Historical patterns and distribution
Perfect for sprint planning and effort estimation!
```
#### Getting a Confluence Page
```
You can retrieve a page using either its ID or title + space key:
By ID:
- page_id: "123456789"
- include_comments: true
- include_history: false
By title and space:
- title: "API Documentation"
- space_key: "DEV"
- include_comments: false
```
#### Searching Confluence Pages
```
Search using CQL (Confluence Query Language):
Simple text search:
- query: "API Documentation"
- max_results: 10
Search by title:
- query: "title ~ 'API Documentation'"
- max_results: 10
Search in specific space:
- query: "space.key = 'DEV'"
- space_key: "DEV"
- max_results: 5
Recent pages:
- query: "lastmodified >= now('-7d')"
Note: The system automatically adds "type = page" to queries that don't specify a content type.
```
#### Asking Questions About Pages
```
Ask specific questions about page content:
- page_id: "123456789"
- question: "What are the main features described?"
- context_type: "summary" | "details" | "specific"
Or using title + space:
- title: "User Guide"
- space_key: "DOCS"
- question: "How do I configure authentication?"
- context_type: "details"
```
#### Common CQL Query Examples
- Simple text search: `"API Documentation"` (searches in content and title)
- Search by title: `title ~ "API Documentation"`
- Search in space: `space.key = "DEV"`
- Recent pages: `lastmodified >= now("-7d")`
- By author: `creator = "john.doe"`
- Combined: `title ~ "API" AND space.key = "DEV" AND lastmodified >= now("-30d")`
- Text in content: `text ~ "authentication method"`
Note: All queries automatically include `type = page` unless explicitly specified otherwise.
### Available Prompts
#### AI-Powered Analysis
- **`summarize-jira-issue`**: Create a summary of a Jira issue
- **`create-jira-description`**: Generate a structured issue description
- **`summarize-confluence-page`**: Create a summary of a Confluence page
- **`create-confluence-content`**: Generate structured Confluence content
- **`answer-confluence-question`**: Answer questions about specific page content
### Context Types for Question Answering
- **`summary`**: Quick answers using first 1000-1500 characters
- **`details`**: Comprehensive answers using full page content
- **`specific`**: Full content with enhanced filtering (future feature)
For detailed Confluence tool documentation and advanced CQL examples, see [CONFLUENCE_TOOLS.md](CONFLUENCE_TOOLS.md).
## Practical Examples
### Workflow: Research and Documentation
1. **Search for relevant pages**: Use `search-confluence` to find pages related to your topic
2. **Get page details**: Use `get-confluence-page` to retrieve full content with comments
3. **Ask specific questions**: Use `ask-confluence-page` to extract specific information
4. **Create summaries**: Use `summarize-confluence-page` prompt for quick overviews
### Common Use Cases
#### Finding Documentation
```
"Search for all API documentation in the DEV space that was updated in the last month"
→ Use search-confluence with query: "type = page AND space.key = 'DEV' AND title ~ 'API' AND lastmodified >= now('-30d')"
```
#### Getting Page Information
```
"Get the User Guide page from DOCS space with all comments"
→ Use get-confluence-page with title: "User Guide", space_key: "DOCS", include_comments: true
```
#### Content Analysis
```
"What authentication methods are supported according to the API documentation?"
→ Use ask-confluence-page with the API doc page ID and your specific question
```
#### Knowledge Extraction
```
"Summarize the key points from the deployment guide"
→ Use summarize-confluence-page prompt with the deployment guide page ID
```
## Development
### Building and Publishing
To prepare the package for distribution:
1. Sync dependencies and update lockfile:
```bash
uv sync
```
2. Build package distributions:
```bash
uv build
```
This will create source and wheel distributions in the `dist/` directory.
3. Publish to PyPI:
```bash
uv publish
```
Note: You'll need to set PyPI credentials via environment variables or command flags:
- Token: `--token` or `UV_PUBLISH_TOKEN`
- Or username/password: `--username`/`UV_PUBLISH_USERNAME` and `--password`/`UV_PUBLISH_PASSWORD`
### Debugging
Since MCP servers run over stdio, debugging can be challenging. For the best debugging
experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector).
You can launch the MCP Inspector via [`npm`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) with this command:
```bash
npx @modelcontextprotocol/inspector uv --directory /Users/annmariyajoshy/vibecoding/mcp-jira-confluence run mcp-jira-confluence
```
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
## Changelog
### Version 0.2.8 (2025-08-22)
**Critical Bug Fix - Daily Standup Summary:**
- **🐛 Fixed NoneType Error** - Resolved "NoneType object has no attribute 'get'" error in daily standup summary:
- **Enhanced null checking**: Added comprehensive null checks for all API responses (sprints, issues, nested objects)
- **Safe object access**: Implemented safe access patterns for nested objects (status, assignee, priority, issuetype)
- **Better error handling**: Added type checking for dictionaries and lists throughout the analysis
- **Improved debugging**: Added traceback logging for better error diagnosis
- **Robust data validation**: Validate sprint data, issue data, and all nested structures before processing
- **Graceful degradation**: Return meaningful error messages instead of crashing on invalid data
**Technical Improvements:**
- Added defensive programming patterns for all data access in daily standup analysis
- Enhanced error messages with specific context about what data is missing or invalid
- Improved logging with full traceback information for debugging
- Better handling of edge cases (empty responses, malformed data, missing fields)
### Version 0.2.7 (2025-08-22)
**Critical Agile API Fixes:**
- **🔧 Fixed Jira Agile API Endpoints** - Resolved 404 errors with legacy Jira instances:
- **Corrected greenhopper URLs**: Fixed `/rest/api/2/greenhopper/1.0/rapidview` → `/rest/greenhopper/1.0/rapidviews/list`
- **Added sprint query endpoint**: Implemented `/rest/greenhopper/1.0/sprintquery/{board_id}` for legacy Jira
- **Enhanced API fallbacks**: Better error handling with graceful degradation from modern to legacy APIs
- **Direct session calls**: Improved control over HTTP requests for agile endpoints
- **JQL fallback**: Added JQL search fallback for sprint issues when agile API unavailable
- **Response normalization**: Convert legacy API responses to modern format for consistency
**Technical Improvements:**
- Fixed argument validation in server.py to allow empty parameters for some tools
- Enhanced error messages with specific API endpoint information
- Added comprehensive API documentation (AGILE_API_FIX.md)
- Better compatibility with both Jira Cloud and Server instances
- Improved debugging information for API endpoint issues
### Version 0.2.6 (2025-08-22)
**Major Agile/Scrum Features:**
- **🏃♂️ Complete Agile/Scrum Toolset** - Full suite of tools for scrum masters and agile teams:
- **`get-agile-boards`** - Get all agile boards or filter by project with board types and project info
- **`get-board-sprints`** - Get sprints for any board (active, closed, future, or all) with goals and dates
- **`get-daily-standup-summary`** - Comprehensive daily standup reports for scrum masters with:
- Sprint progress metrics (issues & story points completion %)
- Team status breakdown with current workloads
- Potential blockers identification
- In-progress tasks by assignee
- **`get-task-assignment-recommendations`** - AI-powered assignment suggestions using:
- Historical data from similar resolved issues
- Team member expertise analysis
- Current workload considerations
- Component and technology experience
- **`estimate-story-points`** - AI-powered story point estimation using:
- Complexity analysis (description, components, labels)
- Historical patterns from similar issues
- Confidence scoring and alternatives
- Reference to most similar resolved issues
**Technical Enhancements:**
- Added comprehensive agile API support with fallback to greenhopper for older Jira versions
- Implemented sophisticated AI analysis algorithms for assignment and estimation
- Enhanced error handling for cases with no active sprints or insufficient data
- Rich markdown formatting for all agile tool outputs
- Embedded resource support for better MCP integration
### Version 0.2.5 (2025-08-22)
**Enhanced Jira Transitions:**
- **Enhanced `transition-jira-issue`** - Now supports transition by name instead of cryptic IDs:
- **Human-readable transitions** - Use "In Progress", "Done", "To Do" instead of numeric IDs
- **Automatic ID resolution** - Finds the correct transition ID from user-friendly names
- **Smart matching** - Matches both transition names and target status names
- **Helpful error messages** - Shows available transitions when invalid names are used
- **Backwards compatibility** - Still supports transition_id parameter for advanced users
- **New `get-jira-transitions` tool** - Discover available transitions for any issue:
- **Complete transition list** - Shows all possible status changes for an issue
- **Rich information** - Displays transition names, target statuses, and IDs
- **Usage guidance** - Provides examples for using each transition
- **User-friendly format** - Clear markdown formatting for easy reading
**Technical Improvements:**
- Added `transition_issue_by_name()` method with intelligent transition matching
- Enhanced error handling with available transitions in error messages
- Case-insensitive transition name matching for better user experience
- Updated tool schemas to support both name and ID parameters
- Comprehensive validation and helpful error messages
### Version 0.2.4 (2025-07-27)
**Enhanced Confluence Search:**
- **Smart CQL Query Builder** - Automatically enhances simple search queries with proper CQL syntax:
- **Simple text queries** - "API docs" becomes `(title ~ "API docs" OR text ~ "API docs")`
- **Phrase detection** - Longer queries become `text ~ "your search phrase"`
- **Advanced CQL preservation** - Complex queries with operators (AND, OR, ~, =) are used as-is
- **Space integration** - Automatically adds space constraints when specified
- **Query transparency** - Shows the enhanced CQL query in search results
**Technical Improvements:**
- Added `build_smart_cql_query()` function for intelligent query enhancement
- Enhanced search-confluence tool description to explain automatic query enhancement
- Better user experience with query transformation visibility
- Improved search accuracy for both novice and advanced users
### Version 0.2.3 (2025-07-27)
**Enhanced Link Extraction:**
- **Enhanced `extract-confluence-links`** - Now extracts both Confluence pages AND Git repository URLs:
- **Git Repository Support** - Detects URLs from GitHub, GitLab, Bitbucket, Azure DevOps, and other Git platforms
- **Smart Pattern Matching** - Uses regex patterns to identify repository URLs in issue descriptions, comments, and remote links
- **Comprehensive Coverage** - Scans all issue text fields for both Confluence and Git references
- **Rich Output** - Returns organized lists of both Confluence pages and Git repositories with context
**Technical Improvements:**
- Added `_extract_git_urls_from_text()` method with support for major Git platforms
- Enhanced URL extraction patterns for better accuracy
- Improved tool description and documentation
- Better organization of extracted links by type (Confluence vs Git)
### Version 0.2.2 (2025-07-27)
**New Jira Tools:**
- **`get-my-assigned-issues`** - Get issues assigned to you ordered by priority (highest first) and creation date (newest first)
- Configurable max results (default: 25, max: 100)
- Option to include completed/closed issues
- Rich formatting with status, priority, type, dates
- **`summarize-jira-issue`** - Comprehensive issue analysis including:
- Complete issue details (status, priority, assignee, dates)
- Full description and recent comments (last 5)
- Confluence page references from remote links
- Formatted as markdown for easy AI processing
- **`extract-confluence-links`** - Find all Confluence page references in issues:
- Scans issue description, all comments, and remote links
- Supports multiple Confluence URL patterns (atlassian.net, custom domains)
- Returns link titles, URLs, and source context
**Technical Enhancements:**
- Added `get_current_user()` API method for user context
- Enhanced JQL queries with proper field selection and ordering
- Robust URL extraction with regex pattern matching
- Improved error handling for missing or invalid issues
- Better date formatting for human readability
### Version 0.2.1 (2025-07-27)
**Formatting Fixes:**
- **Fixed 400 Bad Request errors** with complex markdown formatting in Confluence pages
- **Implemented intelligent complexity detection** - automatically chooses conversion strategy
- **Added robust error handling** with graceful fallbacks for conversion failures
- **Enhanced list processing** with proper HTML grouping and nesting
### Version 0.2.0 (2025-07-27)
**Major Improvements:**
- **Fixed EmbeddedResource validation errors** - All tools now use the correct MCP structure with `type: "resource"` and proper `TextResourceContents` format
- **Enhanced Confluence formatting** - Dramatically improved markdown to Confluence conversion:
- Proper list handling (grouped `<ul>`/`<ol>` tags instead of individual ones)
- Better code block formatting with language support
- Improved inline formatting (bold, italic, code, links)
- Smarter paragraph handling
- More robust markdown detection patterns
- **Fixed HTTP 409 conflicts** - Made version parameter optional in `update-confluence-page` with automatic version fetching
- **Added missing Confluence tools** - Implemented `get-confluence-page` and `search-confluence-pages` with proper CQL support
- **Improved error handling** - Better error messages and validation throughout
**Technical Changes:**
- Rewrote `ConfluenceFormatter.markdown_to_confluence()` with line-by-line processing
- Added regex-based markdown detection with multiple pattern matching
- Enhanced `_process_inline_formatting()` helper for consistent formatting
- Improved version conflict resolution in page updates
- Added comprehensive logging for format detection and conversion
### Version 0.1.9 (2025-07-26)
- Initial PyPI release with basic Jira and Confluence functionality
- Fixed basic EmbeddedResource structure issues
- Added core tool implementations
Raw data
{
"_id": null,
"home_page": null,
"name": "mcp-jira-confluence",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.12",
"maintainer_email": null,
"keywords": "atlassian, confluence, jira, mcp, model-context-protocol",
"author": null,
"author_email": "akhilthomas236 <akhilthomas236@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/78/33/af5dae10db6b67ca63f0d4e9cbe397fc7c722916d590868a8e358a4182ec/mcp_jira_confluence-0.2.10.tar.gz",
"platform": null,
"description": "# MCP Server for Jira and Confluence\n\nA Model Context Protocol (MCP) server that integrates with Atlassian's Jira and Confluence, enabling AI assistants to interact with these tools directly.\n\n## Features\n\n- **Jira Integration**\n - List recent issues\n - View issue details including comments\n - Create new issues\n - Add comments to issues\n - Transition issues between statuses\n - **Get assigned issues** - Retrieve your assigned tickets ordered by priority and date\n - **Summarize issues** - Get comprehensive issue summaries with comments and history\n - **Extract Confluence and Git links** - Find all Confluence page references and Git repository URLs in issues\n - **Agile/Scrum Support** - Board management, sprint tracking, daily standup summaries\n - **AI-Powered Assistance** - Smart task assignment recommendations and story point estimation\n\n- **Confluence Integration**\n - List recent pages\n - View page content\n - Create new pages\n - Update existing pages\n - Add comments to pages\n - Search pages using CQL (Confluence Query Language)\n - Get specific pages by ID or title\n - Ask questions about page content\n\n- **AI-Powered Prompts**\n - Summarize Jira issues\n - Create structured Jira issue descriptions\n - Summarize Confluence pages\n - Generate structured Confluence content\n\n## Installation\n\n1. Clone the repository\n2. Install dependencies using `uv`:\n\n```bash\npip install uv\nuv pip install -e .\n```\n\n## Configuration\n\n### Environment Variables\n\nSet the following environment variables to configure the server:\n\n#### Jira Configuration\n- `JIRA_URL`: Base URL of your Jira instance (e.g., `https://yourcompany.atlassian.net`)\n- `JIRA_USERNAME`: Your Jira username/email\n- `JIRA_API_TOKEN`: Your Jira API token or password\n- `JIRA_PERSONAL_TOKEN`: Personal access token (alternative to username/API token)\n\n#### Confluence Configuration\n- `CONFLUENCE_URL`: Base URL of your Confluence instance (e.g., `https://yourcompany.atlassian.net/wiki`)\n- `CONFLUENCE_USERNAME`: Your Confluence username/email\n- `CONFLUENCE_API_TOKEN`: Your Confluence API token or password\n- `CONFLUENCE_PERSONAL_TOKEN`: Personal access token (alternative to username/API token)\n\n### Quick Setup\n\n1. Create API tokens from your Atlassian account settings\n2. Set environment variables in your shell:\n\n```bash\nexport JIRA_URL=\"https://yourcompany.atlassian.net\"\nexport JIRA_USERNAME=\"your-email@company.com\"\nexport JIRA_API_TOKEN=\"your-jira-api-token\"\n\nexport CONFLUENCE_URL=\"https://yourcompany.atlassian.net/wiki\"\nexport CONFLUENCE_USERNAME=\"your-email@company.com\"\nexport CONFLUENCE_API_TOKEN=\"your-confluence-api-token\"\n```\n\n3. Or use the provided `run.sh` script with environment variables\n\n## Usage\n\n### Starting the Server\n\nRun the server directly:\n\n```bash\npython -m mcp_jira_confluence.server\n```\n\n### VSCode MCP Extension\n\nIf using with the VSCode MCP extension, the server is automatically configured via `.vscode/mcp.json`.\n\n### Claude Desktop\n\nTo use with Claude Desktop, add the following configuration:\n\nOn MacOS: `~/Library/Application\\ Support/Claude/claude_desktop_config.json`\nOn Windows: `%APPDATA%/Claude/claude_desktop_config.json`\n\n<details>\n <summary>Development/Unpublished Servers Configuration</summary>\n \n```json\n\"mcpServers\": {\n \"mcp-jira-confluence\": {\n \"command\": \"uv\",\n \"args\": [\n \"--directory\",\n \"/Users/annmariyajoshy/vibecoding/mcp-jira-confluence\",\n \"run\",\n \"mcp-jira-confluence\"\n ]\n }\n }\n ```\n</details>\n\n<details>\n <summary>Published Servers Configuration</summary>\n \n```json\n\"mcpServers\": {\n \"mcp-jira-confluence\": {\n \"command\": \"uvx\",\n \"args\": [\n \"mcp-jira-confluence\"\n ]\n }\n}\n```\n</details>\n\n## Resources\n\nThe server exposes the following types of resources:\n\n- `jira://issue/{ISSUE_KEY}` - Jira issues\n- `confluence://page/{PAGE_ID}` - Confluence pages\n- `confluence://space/{SPACE_KEY}/page/{PAGE_ID}` - Confluence pages with space key\n\n## Usage\n\n### Available Tools\n\n#### Jira Tools\n- **`create-jira-issue`**: Create a new Jira issue\n- **`comment-jira-issue`**: Add a comment to an issue\n- **`transition-jira-issue`**: Change an issue's status (supports transition names like \"In Progress\", \"Done\")\n- **`get-jira-transitions`**: Get available transitions for an issue\n- **`get-jira-issue`**: Get detailed information about a specific Jira issue\n- **`get-my-assigned-issues`**: Get issues assigned to you, ordered by priority and date\n- **`summarize-jira-issue`**: Get comprehensive issue summary with comments and history\n- **`extract-confluence-links`**: Find all Confluence and Git repository links in an issue\n\n#### Agile/Scrum Tools (NEW!)\n- **`get-agile-boards`**: Get all agile boards or filter by project - essential for scrum masters\n- **`get-board-sprints`**: Get sprints for a specific board (active, closed, future, or all)\n- **`get-daily-standup-summary`**: Comprehensive daily standup report with sprint progress, team status, and blockers\n- **`get-task-assignment-recommendations`**: AI-powered assignment suggestions based on historical data and expertise\n- **`estimate-story-points`**: AI-powered story point estimation using complexity analysis and historical patterns\n\n#### Confluence Tools\n- **`create-confluence-page`**: Create a new Confluence page\n- **`update-confluence-page`**: Update an existing page (version auto-fetched if not provided)\n- **`comment-confluence-page`**: Add a comment to a page\n- **`get-confluence-page`**: Get a specific page with optional comments/history\n- **`search-confluence`**: Search pages using CQL queries\n- **`ask-confluence-page`**: Ask questions about page content\n\n### Usage Examples\n\n#### Getting Your Assigned Issues\n```\nGet issues assigned to you ordered by priority (highest first) and creation date (newest first):\n\nDefault (25 issues, exclude completed):\n- No parameters needed\n\nCustom parameters:\n- max_results: 50 (max: 100)\n- include_done: true (includes closed/resolved issues)\n\nThe tool returns issues with:\n- Issue key, summary, status, priority\n- Issue type, creation date, due date\n- Formatted for easy reading\n```\n\n#### Getting a Specific Jira Issue\n```\nGet detailed information about any Jira issue by its key:\n\nBasic issue info:\n- issue_key: \"PROJ-123\" (required)\n- include_comments: false (default)\n\nWith comments:\n- issue_key: \"PROJ-123\"\n- include_comments: true (includes last 3 comments)\n\nReturns:\n- Complete issue details (status, priority, assignee, dates)\n- Full description\n- Optional recent comments\n- Formatted for easy reading\n```\n\n#### Summarizing a Jira Issue\n```\nGet comprehensive issue information including:\n- Basic details (status, priority, assignee, dates)\n- Full description\n- Recent comments (last 5)\n- Confluence page references\n- Status history\n\nParameters:\n- issue_key: \"PROJ-123\" (required)\n\nReturns formatted markdown summary perfect for AI analysis.\n```\n\n#### Transitioning Issue Status\n```\nChange an issue's status using human-readable transition names:\n\nUsing transition name (recommended):\n- issue_key: \"PROJ-123\"\n- transition_name: \"In Progress\" // or \"Done\", \"To Do\", etc.\n\nUsing transition ID (advanced):\n- issue_key: \"PROJ-123\" \n- transition_id: \"21\"\n\nThe tool automatically:\n- Finds the correct transition ID from the name\n- Provides helpful error messages with available options\n- Shows the new status after transition\n\nCommon transition names: \"To Do\", \"In Progress\", \"Done\", \"Closed\"\n```\n\n#### Getting Available Transitions\n```\nSee what status changes are possible for an issue:\n\nParameters:\n- issue_key: \"PROJ-123\" (required)\n\nReturns:\n- List of available transitions with names and target statuses\n- Transition IDs for advanced usage\n- Usage examples for each transition\n- Clear formatting for easy reading\n\nUse this before transitioning to see available options.\n```\n\n#### Extracting Links from Issues\n```\nFind all Confluence and Git repository links in a Jira issue from:\n- Issue description text\n- Comments from all users \n- Remote links attached to the issue\n\nParameters:\n- issue_key: \"PROJ-123\" (required)\n- include_git_urls: true (default, set to false to exclude Git links)\n\nSupported Git platforms:\n- GitHub, GitLab, Bitbucket (cloud and self-hosted)\n- Azure DevOps / Visual Studio Team Services\n- Generic Git hosting platforms\n- SSH Git URLs (git@server:org/repo.git)\n\nReturns:\n- Confluence page links with titles and context\n- Git repository URLs with source location\n- Organized by category (Confluence vs Git)\n- Source information (description, comment, remote link)\n```\n\n#### Agile Board Management\n```\nGet all agile boards or filter by project:\n\nAll boards:\n- No parameters needed\n\nProject-specific boards:\n- project_key: \"PROJ\" (optional filter)\n\nReturns:\n- Board ID, name, type (Scrum/Kanban)\n- Associated project information\n- Essential for scrum masters managing multiple teams\n```\n\n#### Sprint Management\n```\nGet sprints for a specific agile board:\n\nActive sprints only (default):\n- board_id: \"123\" (required)\n\nAll sprint states:\n- board_id: \"123\"\n- state: \"all\" (options: \"active\", \"closed\", \"future\", \"all\")\n\nReturns:\n- Sprint ID, name, state, dates\n- Sprint goals and progress information\n- Perfect for sprint planning and retrospectives\n```\n\n#### Daily Standup Summary (Scrum Masters)\n```\nGet comprehensive daily standup report for active sprint:\n\nParameters:\n- board_id: \"123\" (required - get from get-agile-boards)\n\nReturns detailed analysis:\n- Sprint progress (issues & story points completion %)\n- Status breakdown (To Do, In Progress, Done, etc.)\n- Team member workload and current tasks\n- Potential blockers (high priority unresolved issues)\n- In-progress tasks by assignee\n- Key metrics for standup discussion\n\nPerfect for scrum masters to quickly assess sprint health!\n```\n\n#### AI-Powered Task Assignment\n```\nGet smart recommendations for who should work on a task:\n\nParameters:\n- issue_key: \"PROJ-123\" (required)\n\nAI analyzes:\n- Historical data from similar resolved issues\n- Team member expertise in components/labels\n- Current workload of potential assignees\n- Average resolution times for similar work\n- Component and technology experience\n\nReturns:\n- Ranked list of recommended assignees\n- Confidence scores and reasoning\n- Current workload information\n- Historical performance data\n```\n\n#### AI-Powered Story Point Estimation\n```\nGet intelligent story point estimates based on complexity and history:\n\nParameters:\n- issue_key: \"PROJ-123\" (required)\n\nAI analyzes:\n- Issue complexity (description length, components, labels)\n- Historical data from similar resolved issues\n- Story point patterns in your project\n- Component and issue type complexity\n\nReturns:\n- Primary recommendation with confidence level\n- Alternative estimates for team discussion\n- Complexity analysis breakdown\n- Similar issues for reference\n- Historical patterns and distribution\n\nPerfect for sprint planning and effort estimation!\n```\n\n#### Getting a Confluence Page\n```\nYou can retrieve a page using either its ID or title + space key:\n\nBy ID:\n- page_id: \"123456789\"\n- include_comments: true\n- include_history: false\n\nBy title and space:\n- title: \"API Documentation\"\n- space_key: \"DEV\"\n- include_comments: false\n```\n\n#### Searching Confluence Pages\n```\nSearch using CQL (Confluence Query Language):\n\nSimple text search:\n- query: \"API Documentation\"\n- max_results: 10\n\nSearch by title:\n- query: \"title ~ 'API Documentation'\"\n- max_results: 10\n\nSearch in specific space:\n- query: \"space.key = 'DEV'\"\n- space_key: \"DEV\"\n- max_results: 5\n\nRecent pages:\n- query: \"lastmodified >= now('-7d')\"\n\nNote: The system automatically adds \"type = page\" to queries that don't specify a content type.\n```\n\n#### Asking Questions About Pages\n```\nAsk specific questions about page content:\n\n- page_id: \"123456789\"\n- question: \"What are the main features described?\"\n- context_type: \"summary\" | \"details\" | \"specific\"\n\nOr using title + space:\n- title: \"User Guide\"\n- space_key: \"DOCS\"\n- question: \"How do I configure authentication?\"\n- context_type: \"details\"\n```\n\n#### Common CQL Query Examples\n- Simple text search: `\"API Documentation\"` (searches in content and title)\n- Search by title: `title ~ \"API Documentation\"`\n- Search in space: `space.key = \"DEV\"`\n- Recent pages: `lastmodified >= now(\"-7d\")`\n- By author: `creator = \"john.doe\"`\n- Combined: `title ~ \"API\" AND space.key = \"DEV\" AND lastmodified >= now(\"-30d\")`\n- Text in content: `text ~ \"authentication method\"`\n\nNote: All queries automatically include `type = page` unless explicitly specified otherwise.\n\n### Available Prompts\n\n#### AI-Powered Analysis\n- **`summarize-jira-issue`**: Create a summary of a Jira issue\n- **`create-jira-description`**: Generate a structured issue description\n- **`summarize-confluence-page`**: Create a summary of a Confluence page\n- **`create-confluence-content`**: Generate structured Confluence content\n- **`answer-confluence-question`**: Answer questions about specific page content\n\n### Context Types for Question Answering\n- **`summary`**: Quick answers using first 1000-1500 characters\n- **`details`**: Comprehensive answers using full page content\n- **`specific`**: Full content with enhanced filtering (future feature)\n\nFor detailed Confluence tool documentation and advanced CQL examples, see [CONFLUENCE_TOOLS.md](CONFLUENCE_TOOLS.md).\n\n## Practical Examples\n\n### Workflow: Research and Documentation\n1. **Search for relevant pages**: Use `search-confluence` to find pages related to your topic\n2. **Get page details**: Use `get-confluence-page` to retrieve full content with comments\n3. **Ask specific questions**: Use `ask-confluence-page` to extract specific information\n4. **Create summaries**: Use `summarize-confluence-page` prompt for quick overviews\n\n### Common Use Cases\n\n#### Finding Documentation\n```\n\"Search for all API documentation in the DEV space that was updated in the last month\"\n\u2192 Use search-confluence with query: \"type = page AND space.key = 'DEV' AND title ~ 'API' AND lastmodified >= now('-30d')\"\n```\n\n#### Getting Page Information\n```\n\"Get the User Guide page from DOCS space with all comments\"\n\u2192 Use get-confluence-page with title: \"User Guide\", space_key: \"DOCS\", include_comments: true\n```\n\n#### Content Analysis\n```\n\"What authentication methods are supported according to the API documentation?\"\n\u2192 Use ask-confluence-page with the API doc page ID and your specific question\n```\n\n#### Knowledge Extraction\n```\n\"Summarize the key points from the deployment guide\"\n\u2192 Use summarize-confluence-page prompt with the deployment guide page ID\n```\n\n## Development\n\n### Building and Publishing\n\nTo prepare the package for distribution:\n\n1. Sync dependencies and update lockfile:\n```bash\nuv sync\n```\n\n2. Build package distributions:\n```bash\nuv build\n```\n\nThis will create source and wheel distributions in the `dist/` directory.\n\n3. Publish to PyPI:\n```bash\nuv publish\n```\n\nNote: You'll need to set PyPI credentials via environment variables or command flags:\n- Token: `--token` or `UV_PUBLISH_TOKEN`\n- Or username/password: `--username`/`UV_PUBLISH_USERNAME` and `--password`/`UV_PUBLISH_PASSWORD`\n\n### Debugging\n\nSince MCP servers run over stdio, debugging can be challenging. For the best debugging\nexperience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector).\n\n\nYou can launch the MCP Inspector via [`npm`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) with this command:\n\n```bash\nnpx @modelcontextprotocol/inspector uv --directory /Users/annmariyajoshy/vibecoding/mcp-jira-confluence run mcp-jira-confluence\n```\n\n\nUpon launching, the Inspector will display a URL that you can access in your browser to begin debugging.\n\n## Changelog\n\n### Version 0.2.8 (2025-08-22)\n\n**Critical Bug Fix - Daily Standup Summary:**\n\n- **\ud83d\udc1b Fixed NoneType Error** - Resolved \"NoneType object has no attribute 'get'\" error in daily standup summary:\n - **Enhanced null checking**: Added comprehensive null checks for all API responses (sprints, issues, nested objects)\n - **Safe object access**: Implemented safe access patterns for nested objects (status, assignee, priority, issuetype)\n - **Better error handling**: Added type checking for dictionaries and lists throughout the analysis\n - **Improved debugging**: Added traceback logging for better error diagnosis\n - **Robust data validation**: Validate sprint data, issue data, and all nested structures before processing\n - **Graceful degradation**: Return meaningful error messages instead of crashing on invalid data\n\n**Technical Improvements:**\n\n- Added defensive programming patterns for all data access in daily standup analysis\n- Enhanced error messages with specific context about what data is missing or invalid\n- Improved logging with full traceback information for debugging\n- Better handling of edge cases (empty responses, malformed data, missing fields)\n\n### Version 0.2.7 (2025-08-22)\n\n**Critical Agile API Fixes:**\n\n- **\ud83d\udd27 Fixed Jira Agile API Endpoints** - Resolved 404 errors with legacy Jira instances:\n - **Corrected greenhopper URLs**: Fixed `/rest/api/2/greenhopper/1.0/rapidview` \u2192 `/rest/greenhopper/1.0/rapidviews/list`\n - **Added sprint query endpoint**: Implemented `/rest/greenhopper/1.0/sprintquery/{board_id}` for legacy Jira\n - **Enhanced API fallbacks**: Better error handling with graceful degradation from modern to legacy APIs\n - **Direct session calls**: Improved control over HTTP requests for agile endpoints\n - **JQL fallback**: Added JQL search fallback for sprint issues when agile API unavailable\n - **Response normalization**: Convert legacy API responses to modern format for consistency\n\n**Technical Improvements:**\n\n- Fixed argument validation in server.py to allow empty parameters for some tools\n- Enhanced error messages with specific API endpoint information\n- Added comprehensive API documentation (AGILE_API_FIX.md)\n- Better compatibility with both Jira Cloud and Server instances\n- Improved debugging information for API endpoint issues\n\n### Version 0.2.6 (2025-08-22)\n\n**Major Agile/Scrum Features:**\n\n- **\ud83c\udfc3\u200d\u2642\ufe0f Complete Agile/Scrum Toolset** - Full suite of tools for scrum masters and agile teams:\n - **`get-agile-boards`** - Get all agile boards or filter by project with board types and project info\n - **`get-board-sprints`** - Get sprints for any board (active, closed, future, or all) with goals and dates\n - **`get-daily-standup-summary`** - Comprehensive daily standup reports for scrum masters with:\n - Sprint progress metrics (issues & story points completion %)\n - Team status breakdown with current workloads\n - Potential blockers identification\n - In-progress tasks by assignee\n - **`get-task-assignment-recommendations`** - AI-powered assignment suggestions using:\n - Historical data from similar resolved issues\n - Team member expertise analysis\n - Current workload considerations\n - Component and technology experience\n - **`estimate-story-points`** - AI-powered story point estimation using:\n - Complexity analysis (description, components, labels)\n - Historical patterns from similar issues\n - Confidence scoring and alternatives\n - Reference to most similar resolved issues\n\n**Technical Enhancements:**\n\n- Added comprehensive agile API support with fallback to greenhopper for older Jira versions\n- Implemented sophisticated AI analysis algorithms for assignment and estimation\n- Enhanced error handling for cases with no active sprints or insufficient data\n- Rich markdown formatting for all agile tool outputs\n- Embedded resource support for better MCP integration\n\n### Version 0.2.5 (2025-08-22)\n\n**Enhanced Jira Transitions:**\n\n- **Enhanced `transition-jira-issue`** - Now supports transition by name instead of cryptic IDs:\n - **Human-readable transitions** - Use \"In Progress\", \"Done\", \"To Do\" instead of numeric IDs\n - **Automatic ID resolution** - Finds the correct transition ID from user-friendly names\n - **Smart matching** - Matches both transition names and target status names\n - **Helpful error messages** - Shows available transitions when invalid names are used\n - **Backwards compatibility** - Still supports transition_id parameter for advanced users\n\n- **New `get-jira-transitions` tool** - Discover available transitions for any issue:\n - **Complete transition list** - Shows all possible status changes for an issue\n - **Rich information** - Displays transition names, target statuses, and IDs\n - **Usage guidance** - Provides examples for using each transition\n - **User-friendly format** - Clear markdown formatting for easy reading\n\n**Technical Improvements:**\n\n- Added `transition_issue_by_name()` method with intelligent transition matching\n- Enhanced error handling with available transitions in error messages \n- Case-insensitive transition name matching for better user experience\n- Updated tool schemas to support both name and ID parameters\n- Comprehensive validation and helpful error messages\n\n### Version 0.2.4 (2025-07-27)\n\n**Enhanced Confluence Search:**\n\n- **Smart CQL Query Builder** - Automatically enhances simple search queries with proper CQL syntax:\n - **Simple text queries** - \"API docs\" becomes `(title ~ \"API docs\" OR text ~ \"API docs\")`\n - **Phrase detection** - Longer queries become `text ~ \"your search phrase\"`\n - **Advanced CQL preservation** - Complex queries with operators (AND, OR, ~, =) are used as-is\n - **Space integration** - Automatically adds space constraints when specified\n - **Query transparency** - Shows the enhanced CQL query in search results\n\n**Technical Improvements:**\n\n- Added `build_smart_cql_query()` function for intelligent query enhancement\n- Enhanced search-confluence tool description to explain automatic query enhancement\n- Better user experience with query transformation visibility\n- Improved search accuracy for both novice and advanced users\n\n### Version 0.2.3 (2025-07-27)\n\n**Enhanced Link Extraction:**\n\n- **Enhanced `extract-confluence-links`** - Now extracts both Confluence pages AND Git repository URLs:\n - **Git Repository Support** - Detects URLs from GitHub, GitLab, Bitbucket, Azure DevOps, and other Git platforms\n - **Smart Pattern Matching** - Uses regex patterns to identify repository URLs in issue descriptions, comments, and remote links\n - **Comprehensive Coverage** - Scans all issue text fields for both Confluence and Git references\n - **Rich Output** - Returns organized lists of both Confluence pages and Git repositories with context\n\n**Technical Improvements:**\n\n- Added `_extract_git_urls_from_text()` method with support for major Git platforms\n- Enhanced URL extraction patterns for better accuracy\n- Improved tool description and documentation\n- Better organization of extracted links by type (Confluence vs Git)\n\n### Version 0.2.2 (2025-07-27)\n\n**New Jira Tools:**\n\n- **`get-my-assigned-issues`** - Get issues assigned to you ordered by priority (highest first) and creation date (newest first)\n - Configurable max results (default: 25, max: 100)\n - Option to include completed/closed issues\n - Rich formatting with status, priority, type, dates\n- **`summarize-jira-issue`** - Comprehensive issue analysis including:\n - Complete issue details (status, priority, assignee, dates)\n - Full description and recent comments (last 5)\n - Confluence page references from remote links\n - Formatted as markdown for easy AI processing\n- **`extract-confluence-links`** - Find all Confluence page references in issues:\n - Scans issue description, all comments, and remote links\n - Supports multiple Confluence URL patterns (atlassian.net, custom domains)\n - Returns link titles, URLs, and source context\n\n**Technical Enhancements:**\n\n- Added `get_current_user()` API method for user context\n- Enhanced JQL queries with proper field selection and ordering\n- Robust URL extraction with regex pattern matching\n- Improved error handling for missing or invalid issues\n- Better date formatting for human readability\n\n### Version 0.2.1 (2025-07-27)\n\n**Formatting Fixes:**\n\n- **Fixed 400 Bad Request errors** with complex markdown formatting in Confluence pages\n- **Implemented intelligent complexity detection** - automatically chooses conversion strategy\n- **Added robust error handling** with graceful fallbacks for conversion failures\n- **Enhanced list processing** with proper HTML grouping and nesting\n\n### Version 0.2.0 (2025-07-27)\n\n**Major Improvements:**\n\n- **Fixed EmbeddedResource validation errors** - All tools now use the correct MCP structure with `type: \"resource\"` and proper `TextResourceContents` format\n- **Enhanced Confluence formatting** - Dramatically improved markdown to Confluence conversion:\n - Proper list handling (grouped `<ul>`/`<ol>` tags instead of individual ones)\n - Better code block formatting with language support\n - Improved inline formatting (bold, italic, code, links)\n - Smarter paragraph handling\n - More robust markdown detection patterns\n- **Fixed HTTP 409 conflicts** - Made version parameter optional in `update-confluence-page` with automatic version fetching\n- **Added missing Confluence tools** - Implemented `get-confluence-page` and `search-confluence-pages` with proper CQL support\n- **Improved error handling** - Better error messages and validation throughout\n\n**Technical Changes:**\n\n- Rewrote `ConfluenceFormatter.markdown_to_confluence()` with line-by-line processing\n- Added regex-based markdown detection with multiple pattern matching\n- Enhanced `_process_inline_formatting()` helper for consistent formatting\n- Improved version conflict resolution in page updates\n- Added comprehensive logging for format detection and conversion\n\n### Version 0.1.9 (2025-07-26)\n\n- Initial PyPI release with basic Jira and Confluence functionality\n- Fixed basic EmbeddedResource structure issues\n- Added core tool implementations",
"bugtrack_url": null,
"license": "MIT",
"summary": "Model Context Protocol server for Jira and Confluence",
"version": "0.2.10",
"project_urls": {
"Documentation": "https://github.com/akhilthomas236/mcp-jira-confluence/blob/main/README.md",
"Homepage": "https://github.com/akhilthomas236/mcp-jira-confluence",
"Issues": "https://github.com/akhilthomas236/mcp-jira-confluence/issues",
"Repository": "https://github.com/akhilthomas236/mcp-jira-confluence"
},
"split_keywords": [
"atlassian",
" confluence",
" jira",
" mcp",
" model-context-protocol"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "2770d3e5015706955344fcea850747044fbad0ceb790f655a47a75f25bf7ee1b",
"md5": "f2e215eee82a6e6e281862ad050de025",
"sha256": "defdbef77eec52de0a059d1336bd971d87c3be41fd2fbe5f824e536ee083408a"
},
"downloads": -1,
"filename": "mcp_jira_confluence-0.2.10-py3-none-any.whl",
"has_sig": false,
"md5_digest": "f2e215eee82a6e6e281862ad050de025",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.12",
"size": 43920,
"upload_time": "2025-08-22T12:43:09",
"upload_time_iso_8601": "2025-08-22T12:43:09.402367Z",
"url": "https://files.pythonhosted.org/packages/27/70/d3e5015706955344fcea850747044fbad0ceb790f655a47a75f25bf7ee1b/mcp_jira_confluence-0.2.10-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "7833af5dae10db6b67ca63f0d4e9cbe397fc7c722916d590868a8e358a4182ec",
"md5": "d0f7816152b3eb4023c90166850a6240",
"sha256": "7326d2ac4fc3bc1aa11d4f41344a04d884aa54705221bc9ec2bdf8e32ee9d4da"
},
"downloads": -1,
"filename": "mcp_jira_confluence-0.2.10.tar.gz",
"has_sig": false,
"md5_digest": "d0f7816152b3eb4023c90166850a6240",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.12",
"size": 60818,
"upload_time": "2025-08-22T12:43:10",
"upload_time_iso_8601": "2025-08-22T12:43:10.751674Z",
"url": "https://files.pythonhosted.org/packages/78/33/af5dae10db6b67ca63f0d4e9cbe397fc7c722916d590868a8e358a4182ec/mcp_jira_confluence-0.2.10.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-08-22 12:43:10",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "akhilthomas236",
"github_project": "mcp-jira-confluence",
"github_not_found": true,
"lcname": "mcp-jira-confluence"
}
JSON
