Skip to main content
Glama
xiandan-erizo

Confluence MCP Server

by xiandan-erizo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CONFLUENCE_URLNoYour Confluence URL
CONFLUENCE_TOKENNoYour Confluence API token (alternative to username/password)
CONFLUENCE_PASSWORDNoYour Confluence password
CONFLUENCE_USERNAMENoYour Confluence username

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_confluenceC
    搜索 Confluence 页面内容

    Args:
        query: 搜索关键词（支持字符串、数字等格式，会自动转换为字符串）
        limit: 返回结果数量限制，默认10条
        ctx: MCP 上下文

    Returns:
        Dict: 包含搜索结果的字典
get_confluence_pageC
    获取 Confluence 页面详细信息

    Args:
        page_id: 页面ID
        ctx: MCP 上下文

    Returns:
        Dict: 包含页面信息的字典

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: get_confluence_page retrieves a specific page by ID, while search_confluence performs a broader content search. There is no overlap in functionality, making it easy for an agent to select the appropriate tool based on whether it needs a known page or wants to find pages matching a query.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (get_confluence_page and search_confluence) with snake_case naming. The verbs 'get' and 'search' are appropriate and distinct, and the naming scheme is predictable across the set.

Tool Count2/5

With only 2 tools, this server feels severely under-scoped for a Confluence integration. A typical Confluence server would need tools for creating, updating, deleting pages, managing spaces, and handling attachments, among others. This minimal set limits agents to read-only operations, which is inadequate for most workflows.

Completeness2/5

The tool surface is significantly incomplete for a Confluence domain. It only supports retrieving and searching pages, missing essential CRUD operations (create, update, delete), space management, user operations, and content manipulation. Agents will face dead ends when trying to perform basic tasks like editing or organizing content.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources