Provides complete page management, advanced search with CQL, space management, attachment handling, and comment system capabilities for Confluence Cloud, allowing AI assistants to create, read, update, delete pages, explore spaces, manage attachments, and access page comments.
Supports containerized deployment with Docker for both HTTP and stdio transport modes, enabling consistent deployment across different environments.
Supports container-based deployment to Heroku for cloud hosting of the MCP server.
Supports direct deployment from GitHub to Railway platform for cloud hosting of the MCP server.
Confluence MCP Server
A universal, production-ready MCP (Model Context Protocol) server for Confluence integration. Built with FastMCP, this server provides AI assistants like Claude with direct access to Confluence Cloud functionality through multiple transport protocols and deployment options.
🌐 Universal Deployment Platform
NEW in v1.1.0: Multi-platform support with HTTP transport alongside the original stdio transport.
🚀 Deployment Options
Platform | Transport | Status | Use Case |
---|---|---|---|
Claude Desktop | stdio | ✅ 100% Compatible | Local development, personal use |
Smithery.ai | HTTP | 🔧 Optimized | Cloud deployment, team sharing (optimized server) |
Docker | HTTP/stdio | ✅ Production Ready | Containerized deployment |
Web Clients | HTTP | ✅ Production Ready | Browser-based AI tools |
Cloud Platforms | HTTP | ✅ Production Ready | Railway, Heroku, AWS, etc. |
✨ Features
- Complete Page Management: Create, read, update, delete Confluence pages
- Advanced Search: Search pages with CQL (Confluence Query Language) support
- Space Management: List and explore Confluence spaces with permissions
- Attachment Handling: Upload, download, and manage page attachments
- Comment System: Access and manage page comments and discussions
- Multi-Transport: stdio (Claude Desktop) + HTTP (web/cloud platforms)
- Universal Launcher: Auto-detects best transport mode for your environment
- Production Ready: Comprehensive error handling, logging, and monitoring
🚀 Quick Start
Option 1: Claude Desktop (stdio transport)
- Install Dependencies:
- Configure Claude Desktop:
- Restart Claude Desktop and look for the 🔨 hammer icon
Option 2: HTTP Server (new in v1.1.0)
- Install Dependencies:
- Set Environment Variables:
- Start HTTP Server:
- Test the Server:
Option 3: Docker Deployment (new in v1.1.0)
- Build Container:
- Run Container:
Option 4: Universal Launcher (new in v1.1.0)
The universal launcher automatically detects the best transport mode:
Option 5: Smithery.ai Deployment (new in v1.1.0)
- Upload Files: Upload
smithery.yaml
and server code to Smithery.ai - Configure Credentials: Set Confluence URL, username, and API token
- Deploy: Smithery.ai handles the rest automatically
🛠️ Available Tools
All 10 Confluence tools work across all transport modes (stdio and HTTP):
Tool | Description | Example Usage |
---|---|---|
get_confluence_page | Retrieve page content | "Show me the content of page ID 123456" |
create_confluence_page | Create new pages | "Create a meeting notes page in the PROJ space" |
update_confluence_page | Modify existing pages | "Add a new section to page 123456" |
delete_confluence_page | Remove pages | "Delete the outdated page 123456" |
search_confluence_pages | Search with CQL | "Find all pages in PROJ space modified this week" |
get_confluence_spaces | List available spaces | "What spaces do I have access to?" |
get_page_attachments | View page attachments | "Show attachments on page 123456" |
add_page_attachment | Upload files | "Upload this document to page 123456" |
delete_page_attachment | Remove files | "Delete the old attachment from page 123456" |
get_page_comments | Read page comments | "Show me comments on page 123456" |
🌐 HTTP API Endpoints (v1.1.0)
The HTTP transport provides these endpoints for web integration:
Endpoint | Method | Description |
---|---|---|
/ | GET | Server information and tool count |
/health | GET | Health check and status |
/mcp | GET | List available tools (lazy loading) |
/mcp | POST | Execute tools via JSON-RPC 2.0 |
/mcp | DELETE | Session cleanup |
Example HTTP Usage
💬 Example AI Assistant Conversations
Creating a Page (works on all platforms):
Searching Content:
🔧 Configuration Options
Platform Compatibility Notes
Cursor: Requires installation path with no spaces. Your current path C:/Users/chris/Documents/Confluence-MCP-Server_Claude
is compatible.
Windsurf: Full MCP support with both stdio and HTTP transports.
Smithery.ai: Uses HTTP transport with automatic configuration management.
Claude Desktop: Uses stdio transport with manual configuration.
Environment Variables (all platforms)
.env File Support
Smithery.ai Configuration
The server automatically handles base64-encoded configuration from Smithery.ai platform.
🔒 Security & Authentication
- API Tokens: Secure token-based authentication with Confluence
- HTTPS Only: All API requests use encrypted connections
- Permission Inheritance: Server inherits your Confluence user permissions
- No Data Storage: Direct API passthrough, no local data retention
- Container Security: Non-root user, minimal attack surface
Getting Confluence API Token
- Go to Atlassian Account Settings
- Click "Create API Token"
- Copy the generated token
- Use your email address as the username
🧪 Testing & Validation
Run Test Suite
Validate Dependencies
Health Checks
🔄 Migration from v1.0.x
100% Backward Compatible - no changes needed for existing Claude Desktop setups.
New capabilities in v1.1.0:
- ✅ HTTP transport for web/cloud deployment
- ✅ Docker containerization
- ✅ Smithery.ai integration
- ✅ Universal launcher
- ✅ Enhanced configuration management
- ✅ Production monitoring and health checks
🐛 Troubleshooting
Claude Desktop Issues
- No hammer icon: Check config file syntax and restart Claude Desktop
- Authentication fails: Verify API token and Confluence URL
- Tools fail: Check environment variables and network connectivity
Cursor Issues
- "No tools found": Ensure installation path contains no spaces
- ❌
node C:/my projects/mcpserver/build/index.js
(fails due to space) - ✅
node C:/projects/mcpserver/build/index.js
(works)
- ❌
- Windows paths: Use forward slashes or properly escaped backslashes
- Test manually first: Verify server starts without errors before adding to Cursor
- Check task manager: Look for briefly appearing node processes during refresh
HTTP Server Issues
- Port conflicts: Use
--port
flag to specify different port - CORS errors: Server includes CORS middleware for web clients
- Tool execution fails: Check environment variables and Confluence permissions
Docker Issues
- Container won't start: Check environment variables are properly set
- Health check fails: Verify Confluence connectivity from container
- Permission errors: Container runs as non-root user by default
General Debugging
📦 Production Deployment
Cloud Platforms
Railway:
Heroku:
AWS/GCP/Azure:
- Use Docker image for container services
- Set environment variables in platform configuration
- Use health check endpoint
/health
for monitoring
Monitoring
The HTTP server provides monitoring endpoints:
- Health:
GET /health
- Server status - Metrics:
GET /
- Tool count and server info - Logs: Structured logging for debugging and monitoring
🤝 Development
Project Structure
Contributing
- Fork the repository
- Create a feature branch
- Add tests for new functionality
- Ensure all tests pass (
pytest tests/ -v
) - Test both stdio and HTTP transports
- Submit a pull request
📄 License
This project is licensed under the MIT License - see the LICENSE file for details.
🚀 Ready to Get Started?
Choose your deployment option:
- 🖥️ Claude Desktop: Use the stdio transport for local development
- 🌐 Web/Cloud: Use the HTTP transport for scalable deployment
- 🐳 Docker: Use containers for consistent deployment
- ⚡ Smithery.ai: Use cloud platform for instant deployment
Transform your Confluence workflow with AI assistance today! 🎉
This server cannot be installed
A universal, production-ready MCP server that provides AI assistants like Claude with direct access to Confluence Cloud functionality for creating, reading, updating, and managing content through multiple transport protocols.
- 🌐 Universal Deployment Platform
- ✨ Features
- 🚀 Quick Start
- 🛠️ Available Tools
- 🌐 HTTP API Endpoints (v1.1.0)
- 💬 Example AI Assistant Conversations
- 🔧 Configuration Options
- 🔒 Security & Authentication
- 🧪 Testing & Validation
- 🔄 Migration from v1.0.x
- 🐛 Troubleshooting
- 📦 Production Deployment
- 🤝 Development
- 📄 License
- 🚀 Ready to Get Started?
Related MCP Servers
- AsecurityFlicenseAqualityEnables AI assistants to interact with Confluence Cloud for managing spaces, pages, and content via the Model Context Protocol (MCP).Last updated -1113TypeScript
- AsecurityFlicenseAqualityA high-performance MCP server that integrates Notion into AI workflows, enabling interaction with Notion pages, databases, and comments through a standardized protocol.Last updated -81013TypeScript
- -securityFlicense-qualityAn MCP server that enables AI agents to interact with Atlassian products (Confluence and Jira) for content management, issue tracking, and project management through a standardized interface.Last updated -2TypeScript
- AsecurityFlicenseAqualityAn MCP server implementation that enables AI assistants to interact with and manage Sakura Cloud infrastructure, including servers, disks, networks, and containerized applications.Last updated -462JavaScript