confluence-mcp
Enables AI assistants to search, retrieve, and manage Confluence pages, and generate weekly status drafts from Jira activity.
README
Confluence MCP Server
A Model Context Protocol (MCP) server that enables AI assistants to search and retrieve content from Confluence pages. This allows AI to understand context and design documentation before making changes.
Features
- Search Confluence Pages: Search for pages by title, content, or keywords
- Retrieve Page Content: Get full page content including body, metadata, and attachments
- List Spaces: Browse available Confluence spaces
- Get Page by ID: Retrieve specific pages by their Confluence ID
- Context-Aware Operations: AI can understand existing documentation before suggesting changes
- Weekly status drafting (full-stack): Generate weekly progress and weekly manager review drafts from Jira activity, edit in a small web UI, and copy/paste into Confluence
Problem this solves
Weekly updates are easy to forget and hard to write consistently. This project turns your Jira activity (optionally combined with a few Confluence “context” pages) into manager-ready weekly drafts with a repeatable structure: highlights, progress, risks, next steps, and asks.
Screenshot

Prerequisites
- Python 3.11+ recommended (works with your existing MCP setup)
- Confluence Cloud or Server instance
- Confluence API token or username/password for authentication
- Node.js 18+ (for the web UI)
Installation
Option A: Using venv (recommended)
- Create a venv and install dependencies:
python3 -m venv .venv
.venv/bin/python -m pip install -r requirements.txt
- Configure by creating a
.envfile:
cp env.example .env
# Edit .env with your Confluence credentials
Option B: Docker Compose
docker compose -f docker-compose.yml up --build
Configuration
The server requires the following environment variables:
CONFLUENCE_URL: Your Confluence instance URL- For Cloud:
https://your-domain.atlassian.net - For Server:
https://confluence.your-domain.com
- For Cloud:
CONFLUENCE_EMAIL: Your Confluence email/usernameCONFLUENCE_API_TOKEN: Your Confluence API token (preferred) or password
Note: The server automatically detects Confluence Cloud vs Server and uses the correct API endpoints (/wiki/rest/api/ for Cloud, /rest/api/ for Server).
Getting a Confluence API Token
- Go to https://id.atlassian.com/manage-profile/security/api-tokens
- Click "Create API token"
- Copy the token and use it in your configuration
Quick Start
- Test your connection:
python3 python/test_connection.py
- Start the weekly draft backend API:
PYTHONPATH="python/backend:python:." .venv/bin/python -m uvicorn app.main:app --host 0.0.0.0 --port 8000
- Start the web UI:
cd frontend
npm install
npm run dev
Then open http://localhost:5173.
- Configure your MCP client (see
docs/CONFIGURATION.mdfor details)
Usage
Testing the Connection
Before configuring your MCP client, test that everything works:
# Set environment variables or use .env file
export CONFLUENCE_URL="https://your-domain.atlassian.net"
export CONFLUENCE_EMAIL="your-email@example.com"
export CONFLUENCE_API_TOKEN="your-api-token"
# Run the test script
python3 python/test_connection.py
Running as MCP Server
The server implements the MCP protocol and can be used with MCP-compatible clients like Cursor, Claude Desktop, etc.
Configure in your MCP client settings:
{
"mcpServers": {
"confluence": {
"command": "python",
"args": ["/path/to/confluence-mcp/python/server.py"],
"env": {
"CONFLUENCE_URL": "https://your-domain.atlassian.net",
"CONFLUENCE_EMAIL": "your-email@example.com",
"CONFLUENCE_API_TOKEN": "your-api-token"
}
}
}
}
Available Tools
-
search_pages: Search for Confluence pages by query
- Parameters:
query(string),space_key(optional),limit(optional, default: 10)
- Parameters:
-
get_page: Get a specific page by ID
- Parameters:
page_id(string)
- Parameters:
-
get_page_content: Get the full content of a page
- Parameters:
page_id(string),expand(optional, default: "body.storage,version,space")
- Parameters:
-
list_spaces: List all accessible Confluence spaces
- Parameters:
limit(optional, default: 50)
- Parameters:
-
search_by_title: Search pages by exact or partial title match
- Parameters:
title(string),space_key(optional),limit(optional)
- Parameters:
-
get_jira_summary: Get a summary of Jira tickets assigned to you from the last N days
- Parameters:
days(optional, default: 14),save_to_file(optional, default: true) - Returns a formatted summary grouped by status and issue type
- Automatically saves to
2026/YYYYMM/jira_summary_YYYYMMDD.mdifsave_to_fileis true - Uses the same Atlassian credentials as Confluence (CONFLUENCE_URL, CONFLUENCE_EMAIL, CONFLUENCE_API_TOKEN)
- Parameters:
-
get_jira_weekly_report: Generate a high-level weekly report with business benefits
- Parameters:
days(optional, default: 14),save_to_file(optional, default: true) - Analyzes tickets to extract value propositions and formats them for stakeholders
- Categorizes into "This Week" (Done/In Progress/In Review) and "Next Week" (To Do)
- Automatically saves to
2026/YYYYMM/weekly_report_YYYYMMDD.mdifsave_to_fileis true - Perfect for weekly status updates to management
- Parameters:
-
search_jira_tickets_by_email: Search for Jira tickets by a specific user's email address
- Parameters:
email(required),days(optional, default: 14),search_type(optional, default: "assignee") - Automatically looks up the user's Account ID from their email, then searches for their tickets
search_typecan be: "assignee" (tickets assigned to user), "reporter" (tickets reported by user), or "all" (both)- Returns a formatted summary grouped by status
- Useful for understanding what a team member has been working on
- Note: Jira Cloud requires Account ID (not email) for searches. This tool handles the lookup automatically.
- Parameters:
-
generate_weekly_drafts: Generate two markdown drafts (weekly progress + manager review)
- Parameters:
week_start(optional ISO date),week_end(optional ISO date),jira_days_lookback(optional),confluence_page_ids(optional array),save_to_files(optional),save_to_db(optional) - Saves markdown to
2026/YYYYMM/and (optionally) stores drafts in SQLite for the web UI
- Parameters:
Example Usage
Once configured, AI assistants can use the server like this:
User: "Search for pages about database design"
AI: [Uses search_pages tool to find relevant pages]
User: "What does the Beta Pipeline design document say?"
AI: [Uses search_pages to find the document, then get_page_content to retrieve it]
User: "Summarize my Jira tickets from the last 2 weeks"
AI: [Uses get_jira_summary to fetch and summarize tickets, saves to 2026/YYYYMM folder]
User: "Generate a weekly report with business benefits from my Jira tickets"
AI: [Uses get_jira_weekly_report to create stakeholder-friendly weekly update]
User: "What has user@example.com been working on in the last 2 weeks?"
AI: [Uses search_jira_tickets_by_email to find and summarize their tickets]
User: "Generate my weekly progress and manager review drafts for last week"
AI: [Uses generate_weekly_drafts tool, returns two markdown drafts]
Security Notes
- Never commit your
.envfile or API tokens to version control - Use API tokens instead of passwords when possible
- The server respects Confluence permissions - users can only access pages they have permission to view
- If you accidentally shared a token in docs or chat, rotate it immediately in Atlassian and replace with placeholders
Troubleshooting
Authentication Errors
- Verify your API token is correct
- Check that your email matches your Confluence account
- Ensure your Confluence URL is correct (include https://)
Permission Errors
- The API token must belong to a user with appropriate Confluence permissions
- Some pages may be restricted and require specific permissions
Connection Errors
- Verify your Confluence URL is accessible
- Check network connectivity
- For Confluence Server, ensure the REST API is enabled
Development
To extend the server with additional functionality:
- Add new tools in
python/server.pyfollowing the MCP tool format - Implement the Confluence API calls in
python/confluence_client.py - Update this README with new tool documentation
License
MIT
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。