Confluence MCP Server

Created By
pawankumar94a year ago
Confluence MCP server providing API tools for Atlassian Confluence operations including page management, space handling, and content search with built-in rate limiting and error handling.
Overview

what is Confluence MCP Server?

Confluence MCP Server is a Model Context Protocol (MCP) server implementation for Atlassian Confluence, designed to facilitate interaction with Confluence content through the MCP protocol, enabling AI agents to work seamlessly with Confluence.

how to use Confluence MCP Server?

To use the Confluence MCP Server, clone the repository, install the dependencies, configure the environment variables, and run the server locally or deploy it to Cloud Run.

key features of Confluence MCP Server?

  • Search pages and spaces using Confluence Query Language (CQL)
  • List all available Confluence spaces
  • Create, read, update, and delete Confluence pages
  • Rich metadata support for Confluence resources
  • Flask-based server for easy deployment to Cloud Run
  • MCP tools for AI agent integration

use cases of Confluence MCP Server?

  1. Automating content management in Confluence.
  2. Integrating AI agents for enhanced content interaction.
  3. Building applications that require dynamic access to Confluence data.

FAQ from Confluence MCP Server?

  • How do I get an access token for Confluence?

Log in to your Atlassian account, go to Account Settings > Security > Create and manage API tokens, and create a new API token.

  • Can I run this server locally?

Yes! You can run the server locally by executing the provided Python script after setting up the environment.

  • Is there support for error handling?

Yes, all tools include proper error handling and return appropriate error messages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pawankumar94
Star
2
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