Confluence MCP Server

Created By
pawankumar94a year ago
Confluence MCP server providing API tools for Atlassian Confluence operations including page management, space handling, and content search with built-in rate limiting and error handling.
Overview

what is Confluence MCP Server?

Confluence MCP Server is a Model Context Protocol (MCP) server implementation for Atlassian Confluence, designed to facilitate interaction with Confluence content through the MCP protocol, enabling AI agents to work seamlessly with Confluence.

how to use Confluence MCP Server?

To use the Confluence MCP Server, clone the repository, install the dependencies, configure the environment variables, and run the server locally or deploy it to Cloud Run.

key features of Confluence MCP Server?

  • Search pages and spaces using Confluence Query Language (CQL)
  • List all available Confluence spaces
  • Create, read, update, and delete Confluence pages
  • Rich metadata support for Confluence resources
  • Flask-based server for easy deployment to Cloud Run
  • MCP tools for AI agent integration

use cases of Confluence MCP Server?

  1. Automating content management in Confluence.
  2. Integrating AI agents for enhanced content interaction.
  3. Building applications that require dynamic access to Confluence data.

FAQ from Confluence MCP Server?

  • How do I get an access token for Confluence?

Log in to your Atlassian account, go to Account Settings > Security > Create and manage API tokens, and create a new API token.

  • Can I run this server locally?

Yes! You can run the server locally by executing the provided Python script after setting up the environment.

  • Is there support for error handling?

Yes, all tools include proper error handling and return appropriate error messages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pawankumar94
Star
2
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago