How to integrate Confluence MCP with Claude Agent SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Confluence Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Confluence to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Confluence agent that can create a project documentation page in marketing space, add 'urgent' label to q3 planning page, publish team meeting summary as a blog post, create a private space for product roadmap drafts through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Confluence account through Composio's Confluence MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Confluence
  • Configure an AI agent that can use Confluence as a tool
  • Run a live chat session where you can ask the agent to perform Confluence operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Confluence MCP server, and what's possible with it?

The Confluence MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Confluence account. It provides structured and secure access to your Confluence spaces, pages, and content, so your agent can perform actions like creating pages, publishing blog posts, organizing spaces, and managing metadata on your behalf.

  • Automated page and space creation: Instantly create new Confluence pages or entire spaces, empowering your agent to generate project documentation, wikis, or knowledge bases as needed.
  • Effortless blog post publishing: Let your agent draft and publish new blog posts within specified Confluence spaces to keep your team up-to-date and share knowledge seamlessly.
  • Content labeling and metadata management: Have your agent add labels and custom properties to pages, blog posts, or spaces, making it easy to organize, tag, and categorize information for better discoverability.
  • Private space setup and management: Direct your agent to create private, isolated workspaces for sensitive projects or teams, ensuring only authorized collaborators have access.
  • Custom content property automation: Empower your agent to attach or update custom metadata on pages, blog posts, spaces, or whiteboards, streamlining your internal documentation workflows.

Supported Tools & Triggers

Tools
Add Content LabelTool to add labels to a piece of content.
Get Space by IDTool to retrieve a confluence space by its id.
Create BlogpostTool to create a new confluence blog post.
Create Blogpost PropertyTool to create a property on a specified blog post.
Create Whiteboard PropertyTool to create a new content property on a whiteboard.
Create PageTool to create a new confluence page in a specified space.
Create Page PropertyTool to create a property on a confluence page.
Create Private SpaceTool to create a private confluence space.
Create SpaceTool to create a new confluence space.
Create Space PropertyTool to create a new property on a confluence space.
Create WhiteboardTool to create a new confluence whiteboard.
Delete Blogpost PropertyTool to delete a blog post property.
Delete Page Content PropertyTool to delete a content property from a page by property id.
Delete Whiteboard Content PropertyTool to delete a content property from a whiteboard by property id.
Delete PageTool to delete a confluence page.
Delete SpaceTool to delete a confluence space by its key.
Delete Space PropertyTool to delete a space property.
Get Attachment LabelsTool to list labels on an attachment.
Get AttachmentsTool to retrieve attachments of a confluence page.
Get Audit LogsTool to retrieve confluence audit records.
Get Blogpost by IDTool to retrieve a specific confluence blog post by its id.
Get Blogpost LabelsTool to retrieve labels of a specific confluence blog post by id.
Get Blogpost Like CountTool to get like count for a confluence blog post.
Get Blogpost OperationsTool to retrieve permitted operations for a confluence blog post.
Get BlogpostsTool to retrieve a list of blog posts.
Get Blog PostsTool to retrieve a list of blog posts.
Get Blog Posts For LabelTool to list all blog posts under a specific label.
Get Blogpost Version DetailsTool to retrieve details for a specific version of a blog post.
Get Blogpost VersionsTool to retrieve all versions of a specific blog post.
Get Child PagesTool to list all direct child pages of a given confluence page.
Get Blog Post Content PropertiesTool to retrieve all content properties on a blog post.
Get Page Content PropertiesTool to retrieve all content properties on a page.
Get Content RestrictionsTool to retrieve restrictions on a confluence content item.
Get Current UserTool to get information about the currently authenticated user.
Get Inline Comments for Blog PostTool to retrieve inline comments for a confluence blog post.
Get LabelsTool to retrieve all labels in a confluence site.
Get Page LabelsTool to retrieve labels of a specific confluence page by id.
Get Labels for SpaceTool to list labels on a space.
Get Labels for Space ContentTool to list labels on all content in a space.
Get Page AncestorsTool to retrieve all ancestors for a given confluence page by its id.
Get Page by IDTool to retrieve a confluence page by its id.
Get Page Like CountTool to get like count for a confluence page.
Get PagesTool to retrieve a list of pages.
Get Page VersionsTool to retrieve all versions of a specific confluence page.
Get Space by IDTool to retrieve a confluence space by its id.
Get Space ContentsTool to retrieve content in a confluence space.
Get Space PropertiesTool to get properties of a confluence space.
Get SpacesTool to retrieve a list of confluence spaces.
Get Anonymous UserTool to retrieve information about the anonymous user.
Search ContentSearches for content by filtering pages from the confluence v2 api with intelligent ranking.
Search UsersSearches for users using user-specific queries from the confluence query language (cql).
Update BlogpostTool to update a confluence blog post's title or content.
Update Blogpost PropertyTool to update a property of a specified blog post.
Update Page Content PropertyTool to update a content property on a confluence page.
Update Whiteboard Content PropertyTool to update a content property on a whiteboard.
Update PageTool to update an existing confluence page.
Update Space PropertyTool to update a space property.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Confluence account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Confluence functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Confluence
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["confluence"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Confluence
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Confluence tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Confluence
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Confluence and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Confluence
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["confluence"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Confluence tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Confluence through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Confluence MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Confluence MCP with OpenAI Agents SDK

Google ADK

Google ADK

Use Confluence MCP with Google ADK

LangChain

LangChain

Use Confluence MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Confluence MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Confluence MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Confluence MCP with LlamaIndex

CrewAI

CrewAI

Use Confluence MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Confluence MCP?

With a standalone Confluence MCP server, the agents and LLMs can only access a fixed set of Confluence tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Confluence and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Agent SDK?

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Confluence tools.

Can I manage the permissions and scopes for Confluence while using Tool Router?

Yes, absolutely. You can configure which Confluence scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Confluence data and credentials are handled as safely as possible.

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free