Jira & Confluence MCP Server
Enables AI assistants to interact with Jira and Confluence via natural language, supporting 37 Jira tools and 16 Confluence tools.
README
Jira & Confluence MCP Server
An MCP (Model Context Protocol) server that lets AI assistants interact with Jira and Confluence via natural language. Works with Claude, GitHub Copilot, and any MCP-compatible client.
Quick Start (Recommended)
Install via uvx (no clone needed)
# 1. Get your Atlassian API token at:
# https://id.atlassian.com/manage-profile/security/api-tokens
# 2. Add to your MCP client config:
{
"mcpServers": {
"atlassian-mcp": {
"type": "local",
"command": "uvx",
"args": ["atlassian-mcp"],
"env": {
"ATLASSIAN_URL": "https://your-domain.atlassian.net",
"ATLASSIAN_EMAIL": "your-email@example.com",
"ATLASSIAN_API_TOKEN": "your-api-token"
}
}
}
}
That's it — uvx automatically downloads and runs the package in an isolated environment.
uvxnot installed? Run:pip install uvor see uv installation docs.
MCP Client Config Locations
| Client | Config file |
|---|---|
| GitHub Copilot CLI | ~/.copilot/mcp-config.json |
| Claude Desktop (macOS) | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Claude Desktop (Windows) | %APPDATA%\Claude\claude_desktop_config.json |
| Claude Desktop (Linux) | ~/.config/claude/claude_desktop_config.json |
Features
Jira Tools (37 tools)
| Category | Tools |
|---|---|
| Projects | jira_list_projects, jira_get_project |
| Issues | jira_get_issue, jira_search_issues, jira_create_issue, jira_update_issue, jira_delete_issue |
| Workflow | jira_get_transitions, jira_transition_issue |
| Comments | jira_get_comments, jira_add_comment, jira_update_comment, jira_delete_comment |
| Assignment | jira_assign_issue |
| Users | jira_search_users, jira_get_current_user |
| Boards | jira_list_boards, jira_get_board, jira_get_board_issues, jira_get_board_backlog |
| Sprints | jira_list_sprints, jira_get_sprint, jira_create_sprint, jira_update_sprint, jira_get_sprint_issues, jira_move_issues_to_sprint, jira_move_issues_to_backlog |
| Metadata | jira_get_issue_types, jira_get_priorities, jira_get_fields, jira_get_labels |
| Worklogs | jira_add_worklog, jira_get_worklogs |
| Watchers | jira_get_watchers, jira_add_watcher |
| Links | jira_get_link_types, jira_link_issues |
Confluence Tools (16 tools)
| Category | Tools |
|---|---|
| Spaces | confluence_list_spaces, confluence_get_space, confluence_get_space_by_key |
| Pages | confluence_get_page, confluence_list_pages_in_space, confluence_get_child_pages, confluence_create_page, confluence_update_page, confluence_delete_page |
| Labels | confluence_get_page_labels, confluence_add_page_labels, confluence_delete_page_label |
| Search | confluence_search |
| Hierarchy | confluence_get_page_ancestors |
| Comments | confluence_get_page_comments, confluence_add_page_comment |
Alternative: Run from Source
git clone https://github.com/halim-23/jira-mcp-server.git
cd jira-mcp-server
pip install -r requirements.txt
cp .env.example .env
# Edit .env with your credentials
python3 main.py
Then point your MCP client to:
{
"mcpServers": {
"atlassian-mcp": {
"type": "local",
"command": "python3",
"args": ["atlassian-mcp"],
}
}
}
Environment Variables
| Variable | Description |
|---|---|
ATLASSIAN_URL |
Your Atlassian base URL, e.g. https://yourco.atlassian.net |
ATLASSIAN_EMAIL |
Your Atlassian account email |
ATLASSIAN_API_TOKEN |
API token from id.atlassian.com |
All three variables are required. They can be set in a .env file (for local dev) or passed via the env block in your MCP client config (recommended for uvx usage).
Example Usage
Once configured, ask your AI assistant:
- "Show me all open issues in project MYPROJ"
- "Create a bug ticket: Login page throws 500 error on Safari"
- "Move PROJ-42 to In Progress and assign it to me"
- "Log 2 hours on PROJ-42 with comment 'code review'"
- "Show the active sprint on board 123"
- "Search Confluence for pages about deployment"
- "Create a Confluence page in space ENG titled 'API Design Guidelines'"
Technical Notes
This server targets Jira Cloud and Confluence Cloud REST APIs:
- Jira:
REST API v3(/rest/api/3/) + Agile API (/rest/agile/1.0/) - Confluence:
REST API v2(/wiki/api/v2/) with v1 fallback for CQL search - Search uses
POST /rest/api/3/search/jql(the current Jira Cloud search endpoint) - All API calls are async via
httpx
Contributing
See CONTRIBUTING.md for guidelines on reporting bugs, requesting features, and submitting pull requests.
License
MIT — see LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。