A Node.js/TypeScript MCP server for Atlassian Confluence that enables AI systems to interact with Confluence pages, spaces, and content.
Critical failure across all 22 tools. Descriptions are present but generic (10-50 chars), below the 50-200 char LLM-optimized baseline. No parameter descriptions visible in schema definitions. Tool names follow verb_noun convention (positive), but lack of actual schema definitions means parameters cannot be validated or understood by LLMs. This server is non-functional for agent use.
Add a comment to a Confluence page.
Add a label to a Confluence page.
Create a new Confluence page.
Delete an attachment from a Confluence page.
Delete (trash) a Confluence page.
Download an attachment from a Confluence page.
All 22 tools have empty input schemas ({}). LLMs cannot understand what parameters each tool accepts, their types, constraints, or descriptions.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 37 | <=2025-11-25 | v2 |
Download all attachments from a Confluence page content.
Get attachments for a Confluence page.
Get comments on a Confluence page.
Get labels for a Confluence page.
Get content of a specific Confluence page by its ID, or by title and space key.
Get direct children of a Confluence page.
Get version history of a Confluence page.
Get images embedded in a Confluence page.
Get page view analytics for a Confluence page.
Move a Confluence page under a different parent.
Reply to an existing comment on a Confluence page.
Search Confluence content using simple terms or CQL (Confluence Query Language).
Search for users in Confluence.
Update an existing Confluence page.
Upload an attachment to a Confluence page.
Upload multiple attachments to a Confluence page.
Tool descriptions are generic and under 50 characters (e.g., 'Get content of a specific Confluence page by its ID, or by title and space key.' is 80 chars but lacks WHEN to use, prerequisites, or return structure). Baseline for LLM-optimized descriptions is 50-200 chars with explicit context.
No parameter descriptions visible in any tool schema. LLMs cannot infer what 'page_id', 'space_key', 'title', or other parameters mean without explicit descriptions. This violates the rule that every parameter must have a non-empty description.
Destructive tools (confluence_delete_page, confluence_delete_attachment) lack confirmation or dry-run support. No error handling guidance for recovery. Agents cannot safely plan irreversible operations.
No output schema documentation visible. LLMs cannot plan downstream tool calls or extract required fields (e.g., page_id from confluence_create_page to pass to confluence_add_comment). Breaks tool composition.