Skip to main content
Glama
deenesjakoruzh
KS-GEN-AI

Confluence Communication Server

by KS-GEN-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Confluence 커뮤니케이션 서버 MCP 서버

대장간 배지

Confluence와 상호 작용

Confluence와 상호 작용하는 도구를 제공하는 TypeScript 기반 MCP 서버입니다. 다음을 통해 핵심 MCP 개념을 보여줍니다.

  • 검색 페이지에 CQL 쿼리를 실행하기 위한 도구

  • Confluence 페이지의 콘텐츠를 검색하기 위한 도구

  • Confluence 페이지의 콘텐츠를 업데이트하기 위한 도구

특징

Related MCP server: Confluence MCP Server

Confluence 도구

execute_cql_search

  • 목적 : Confluence 페이지를 검색하기 위해 CQL 쿼리를 실행합니다.

  • 매개변수 : cql , limit (기본값: 10).

get_page_content

  • 목적 : Confluence 페이지의 내용을 가져옵니다.

  • 매개변수 : pageId .

update_page_content

  • 목적 : Confluence 페이지의 콘텐츠를 업데이트합니다.

  • 매개변수 : pageId , content , title (선택 사항, 변경하려는 경우).

개발

종속성 설치:

지엑스피1

서버를 빌드하세요:

npm run build

자동 재빌드를 사용한 개발의 경우:

npm run watch

설치

Smithery를 통해 설치

Smithery를 통해 Claude Desktop용 Confluence Communication Server MCP 서버를 자동으로 설치하려면:

npx -y @smithery/cli install @KS-GEN-AI/confluence-mcp-server --client claude

Claude Desktop과 함께 사용하려면 서버 구성을 추가하세요.

MacOS의 경우: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows의 경우: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "Confluence communication server": {
      "command": "node",
      "args": ["/PATH_TO_THE_PROJECT/build/index.js"],
      "env": {
        "CONFLUENCE_URL": "https://XXXXXXXX.atlassian.net/wiki",
        "CONFLUENCE_API_MAIL": "Your email",
        "CONFLUENCE_API_KEY": "KEY_FROM: https://id.atlassian.com/manage-profile/security/api-tokens"
      }
    }
  }
}

디버깅

MCP 서버는 stdio를 통해 통신하므로 디버깅이 어려울 수 있습니다. 패키지 스크립트로 제공되는 MCP Inspector를 사용하는 것이 좋습니다.

npm run inspector

검사기는 브라우저에서 디버깅 도구에 액세스할 수 있는 URL을 제공합니다.

Available Tools

3 tools
get_page_contentB

Get the content of a Confluence page

ParametersJSON Schema
NameRequiredDescriptionDefault
pageIdYesConfluence Page ID

TDQS

B3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description must carry the burden of behavioral disclosure. It only says 'Get the content', failing to mention read-only nature, permissions, or return format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but it omits important context, making it underinformative despite its brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema, the description should clarify what 'content' entails (e.g., body, metadata, attachments) and whether it is read-only, but it provides no such details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds no additional meaning beyond the schema's 'Confluence Page ID' for the pageId parameter, meeting the baseline but not exceeding it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'the content of a Confluence page', distinguishing it from sibling tools that operate on Jira issues or create/update pages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like create_page or update_page, nor does it mention any prerequisites or context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

update_page_contentC

Update the content of a Confluence page

ParametersJSON Schema
NameRequiredDescriptionDefault
pageIdYesConfluence Page ID
contentYesHTML content to update the page with
titleNoPage title (optional, if you want to change it)

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'update' which implies a mutation, but doesn't disclose critical traits like required permissions, whether changes are reversible, rate limits, or what happens on success/failure. This leaves significant gaps for a tool that modifies content.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral context (e.g., permissions, side effects), usage guidelines, and details on return values or errors. For updating page content, this leaves too many unknowns for effective tool selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with clear descriptions for all parameters (pageId, content, title). The description adds no additional meaning beyond what the schema provides, such as format details for content or title constraints. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'update' and resource 'content of a Confluence page', making the purpose immediately understandable. It distinguishes from sibling tools like 'get_page_content' (read vs. write) and 'execute_cql_search' (search vs. update), though it doesn't explicitly mention these distinctions in the description itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing page ID), exclusions, or compare it to sibling tools like 'get_page_content' for reading or 'execute_cql_search' for finding pages. Usage is implied by the action but not explicitly defined.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updates
    • First observedexecute_cql_search
    • First observedget_page_content
    • First observedupdate_page_content
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

B3.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: execute_cql_search handles search queries, get_page_content retrieves page content, and update_page_content modifies page content. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (execute_cql_search, get_page_content, update_page_content) with clear action verbs and descriptive nouns. This uniformity enhances readability and predictability across the tool set.

Tool Count3/5

With only 3 tools, the set feels thin for a Confluence server, lacking operations like creating or deleting pages, managing comments, or handling attachments. While the tools cover basic read/update/search, the scope is limited and may require workarounds for full domain coverage.

Completeness2/5

The tool set is significantly incomplete for Confluence communication, missing essential CRUD operations such as create_page and delete_page, as well as functionalities for comments, spaces, or user management. This will likely cause agent failures when attempting comprehensive workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches