Confluence

Created By
MahithChigurupatia year ago
Overview

what is Confluence MCP Server?

Confluence MCP Server is a FastMCP-based server that provides seamless integration with Confluence's REST API, allowing programmatic access to Confluence spaces, pages, and content search functionality.

how to use Confluence MCP Server?

To use the Confluence MCP Server, clone the repository, set up a virtual environment, install dependencies, configure environment variables, and start the server using the command python confluence.py.

key features of Confluence MCP Server?

  • Space Management: List and filter Confluence spaces
  • Page Operations: Retrieve and manage page content
  • Search Functionality: Execute CQL (Confluence Query Language) searches
  • Space Navigation: List all pages within specific spaces
  • Authentication: Secure API token-based access

use cases of Confluence MCP Server?

  1. Automating content retrieval from Confluence pages
  2. Integrating Confluence data into other applications
  3. Performing advanced searches across Confluence spaces

FAQ from Confluence MCP Server?

  • What are the system requirements?

Python 3.8+, pip, and an active Confluence instance with API access are required.

  • How do I obtain a Confluence API token?

Visit Atlassian API Tokens, create a token, and copy it immediately after creation.

  • What should I do if I encounter authentication errors?

Ensure your username matches your Atlassian account email and verify that your API token is correctly copied.

Server Config

{
  "mcpServers": {
    "confluence": {
      "command": "python",
      "args": [
        "confluence.py"
      ],
      "cwd": "/path/to/Confluence-MCP-Server"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MahithChigurupati
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

a day ago