Confluence MCP Server v2.0 - Selective Editing

Created By
Erato949a year ago
Revolutionary MCP server with surgical precision editing for Confluence - industry's first XML-aware selective content modification MCP system for AI assistants
Overview

What is Confluence MCP Server v2.0?

Confluence MCP Server v2.0 is a revolutionary server that enables selective editing capabilities for AI assistants, allowing for precise modifications in Confluence documents without disrupting existing content.

How to use Confluence MCP Server?

To use the server, you can deploy it via Docker, HTTP server, or Claude Desktop. After installation, configure it with your Confluence credentials and start using the available tools for targeted editing.

Key features of Confluence MCP Server?

  • Selective editing capabilities for specific sections, text patterns, and table cells.
  • XML-aware operations that preserve document structure and macros.
  • Rollback capability for safe editing operations.
  • A complete tool suite for managing Confluence content.

Use cases of Confluence MCP Server?

  1. Updating project statuses without altering meeting notes.
  2. Fixing typos across multiple documentation pages.
  3. Modifying individual table cells in status dashboards.

FAQ from Confluence MCP Server?

  • Can I use this server for all Confluence documents?

Yes! It is designed to work with any Confluence document while preserving its structure.

  • Is there a tutorial available for new users?

Yes! A complete step-by-step tutorial is provided to help users get started with selective editing.

  • What deployment options are available?

You can deploy it using Docker, HTTP server, or Claude Desktop.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Erato949
Star
1
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago