Atlassian Confluence MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Atlassian Confluence MCP Server?

The Atlassian Confluence MCP Server is a Model Context Protocol (MCP) server that connects AI assistants to your Atlassian Confluence instance, allowing real-time access to Confluence content.

How to use the Atlassian Confluence MCP Server?

To use the server, set up your Atlassian API token, configure the server credentials, and connect your AI assistant to the server. You can interact with Confluence using various commands through your AI assistant or directly via the command line.

Key features of the Atlassian Confluence MCP Server?

  • Real-time access to Confluence content for AI assistants.
  • Elimination of manual copy/paste between Confluence and AI.
  • Enhanced AI capabilities for searching, summarizing, and analyzing documentation.
  • Secure access control via API tokens.

Use cases of the Atlassian Confluence MCP Server?

  1. AI assistants can retrieve and summarize documentation from Confluence.
  2. Automating the search for specific content within Confluence.
  3. Facilitating real-time collaboration and information retrieval for teams.

FAQ from Atlassian Confluence MCP Server?

  • What is MCP?
    MCP stands for Model Context Protocol, an open standard for AI models to connect securely to external tools.

  • Is the server secure?
    Yes, access is controlled via API tokens, ensuring sensitive operations remain secure.

  • What are the prerequisites?
    You need Node.js, npm, and an active Atlassian account with access to your Confluence instance.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
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