Confluence MCP Server

Created By
minhoyooDEVa year ago
confluence-mcp-server for 8
Overview

what is Confluence MCP Server?

Confluence MCP Server is a Model Context Protocol server system designed to access the Confluence API using a Personal Access Token. It acts as a proxy server to facilitate communication with the Confluence API within a VPN environment.

how to use Confluence MCP Server?

To use the Confluence MCP Server, clone the repository, install dependencies, set up environment variables, and run the MCP and proxy servers in your development or production environment.

key features of Confluence MCP Server?

  • Access to all Confluence spaces and pages.
  • Create and update pages in Confluence.
  • RESTful API for seamless integration.
  • Proxy server for handling requests from MCP clients.

use cases of Confluence MCP Server?

  1. Integrating Confluence API with other applications securely.
  2. Managing Confluence content programmatically.
  3. Facilitating access to Confluence API from restricted networks.

FAQ from Confluence MCP Server?

  • What is the purpose of the MCP server?

The MCP server communicates with the Confluence API to process data and handle requests.

  • How do I set up the environment?

Create a .env file with the necessary configuration variables as outlined in the documentation.

  • What should I do if I encounter connection errors?

Check your Personal Access Token, network settings, and ensure the MCP server is running correctly.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
minhoyooDEV
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)

2 days ago