Confluence MCP Server Example

Created By
BootcampToProda year ago
A Spring Boot AI-powered Model Context Protocol Server for interacting with Confluence Cloud
Overview

What is spring-boot-ai-confluence-mcp-server?

The spring-boot-ai-confluence-mcp-server is a Spring Boot application designed to serve as an AI-powered Model Context Protocol Server, facilitating interactions with Confluence Cloud.

How to use spring-boot-ai-confluence-mcp-server?

To use this server, deploy it in your Spring Boot environment and configure it to connect with your Confluence Cloud instance. You can then send requests to the server to interact with Confluence data.

Key features of spring-boot-ai-confluence-mcp-server?

  • AI-powered interactions with Confluence Cloud.
  • Model Context Protocol for structured data handling.
  • Easy integration with existing Spring Boot applications.

Use cases of spring-boot-ai-confluence-mcp-server?

  1. Automating content management tasks in Confluence.
  2. Enhancing collaboration through AI-driven insights.
  3. Integrating Confluence with other applications using the Model Context Protocol.

FAQ from spring-boot-ai-confluence-mcp-server?

  • What programming language is used?

The server is developed in Java using the Spring Boot framework.

  • Is this project open-source?

Yes, the project is available on GitHub for public access and contributions.

  • How can I contribute to the project?

You can contribute by submitting issues, feature requests, or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
BootcampToProd
Star
1
Language
Java
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
Voyei

4 hours ago