Enhanced Confluence Interaction Gateway

Synopsis

This gateway module implements the Model Context Protocol (MCP) specification for interfacing with Confluence services. This iteration incorporates crucial defect resolutions from the predecessor Confluence integration component, resulting in superior stability and dependability. It furnishes capabilities for running CQL searches and extracting page payload data from Confluence.

The component adheres strictly to the MCP client-server paradigm:

• Operates as an MCP server component exposing Confluence utilities.
• Establishes a secure connection to Confluence as its primary data repository.
• Communicates with MCP consumer agents via the established protocol specification.

Operational Guide

Deployment with Claude Applications, Cline, Roo Code

When employing this connector with the Claude Application environment, API credentials and endpoint configurations must be supplied directly.

{ "mcpServers": { "Atlassian Confluence Interface Engine": { "command": "npx", "args": ["-y", "@zereight/mcp-confluence"], "env": { "CONFLUENCE_URL": "https://XXXXXXXX.atlassian.net", "JIRA_URL": "https://XXXXXXXX.atlassian.net", "CONFLUENCE_API_MAIL": "Your electronic mail address", "CONFLUENCE_API_KEY": "Credential obtained from: https://id.atlassian.com/manage-profile/security/api-tokens", "CONFLUENCE_IS_CLOUD": "true" // Adjust to "false" for self-hosted Server/Data Center installations } } } }

Integration with Cursor IDE

Installation via Smithery Registry

To automate the setup of this Confluence interface module for Claude Desktop integration using Smithery:

bash npx -y @smithery/cli install @zereight/confluence-mcp --client claude

For Cursor usage, define necessary environment variables and launch the service as follows:

bash env CONFLUENCE_API_MAIL=your@email.com CONFLUENCE_API_KEY=your-key CONFLUENCE_URL=your-confluence-url JIRA_URL=your-jira-url npx -y @zereight/mcp-confluence

• CONFLUENCE_API_MAIL: Credentials email for the Confluence API access.
• CONFLUENCE_API_KEY: The secret API token for Confluence.
• CONFLUENCE_URL: The root URL pointing to your Confluence instance.
• JIRA_URL: The root URL for the associated JIRA instance.
• CONFLUENCE_IS_CLOUD: Specifies the deployment type.
• Default value is true (indicates Cloud deployment).
• Set explicitly to 'false' for Server or Data Center deployments.
• Influences API endpoint prefix structure:
  • Cloud: /wiki/rest/api
  • Server: /rest/api

Confluence Utility Set

• execute_cql_search: Executes a CQL expression against Confluence for resource discovery.

• Description: Runs a Confluence Query Language statement against the configured instance to locate knowledge base pages.

• Input Schema:

  { "type": "object", "properties": { "cql": { "type": "string", "description": "The CQL search predicate string" }, "limit": { "type": "integer", "description": "Maximum count of result entities to return", "default": 10 } }, "required": ["cql"] }

• get_page_content: Fetches the serialized content of a designated Confluence page.

• Description: Retrieves the body content of a Confluence artifact identified by its unique Page ID.

• Input Schema:

  { "type": "object", "properties": { "pageId": { "type": "string", "description": "The unique identifier for the Confluence Page" } }, "required": ["pageId"] }

• create_page: Provisions a novel Confluence page entity.

• Description: Generates a new documentation page within the specified organizational space.

• Input Schema:

  { "type": "object", "properties": { "spaceKey": { "type": "string", "description": "Key identifying the target Space for creation" }, "title": { "type": "string", "description": "The heading assigned to the new page" }, "content": { "type": "string", "description": "The page substance, formatted in storage markup" }, "parentId": { "type": "string", "description": "Identifier of the parent page (optional link)" } }, "required": ["spaceKey", "title", "content"] }

• update_page: Modifies the attributes of an extant Confluence page.

• Description: Overwrites the existing content or title of a specified Confluence page entity.

• Input Schema:

  { "type": "object", "properties": { "pageId": { "type": "string", "description": "The unique ID of the page targeted for modification" }, "content": { "type": "string", "description": "The revised page payload, in storage format" }, "title": { "type": "string", "description": "The updated page designation (optional)" } }, "required": ["pageId", "content"] }

Jira Integration Utilities

• execute_jql_search: Runs a JQL query against the linked Jira system to locate tickets.

• Description: Executes a Jira Query Language statement on the Jira platform to retrieve relevant issue records.

• Input Schema:

  { "type": "object", "properties": { "jql": { "type": "string", "description": "The JQL expression for searching" }, "limit": { "type": "integer", "description": "Maximum number of issues to fetch", "default": 10 } }, "required": ["jql"] }

• create_jira_issue: Provisions a new ticket item within Jira.

• Description: Constructs a new issue entity within the designated Jira project structure.

• Input Schema:

  { "type": "object", "properties": { "project": { "type": "string", "description": "Key identifier for the target Project" }, "summary": { "type": "string", "description": "Concise summary of the issue" }, "description": { "type": "string", "description": "Detailed narrative for the issue" }, "issuetype": { "type": "string", "description": "The category name for the issue type" }, "assignee": { "type": "string", "description": "Account ID of the entity to be assigned" }, "priority": { "type": "string", "description": "Numeric identifier for issue priority level" } }, "required": ["project", "summary", "issuetype"] }

• update_jira_issue: Modifies attributes on an existing Jira ticket.

• Description: Updates various fields associated with a pre-existing Jira issue entity.

• Input Schema:

  { "type": "object", "properties": { "issueKey": { "type": "string", "description": "The unique identifier for the issue (e.g., PROJ-123)" }, "summary": { "type": "string", "description": "Replacement issue title" }, "description": { "type": "string", "description": "Replacement issue body text" }, "assignee": { "type": "string", "description": "New Account ID for issue assignment" }, "priority": { "type": "string", "description": "The updated priority identifier" } }, "required": ["issueKey"] }

• transition_jira_issue: Executes a status advancement for a Jira ticket.

• Description: Changes the workflow state of a Jira issue utilizing a specific transition ID value.

• Input Schema:

  { "type": "object", "properties": { "issueKey": { "type": "string", "description": "Issue identifier (e.g. PROJ-123)" }, "transitionId": { "type": "string", "description": "The ID corresponding to the desired status progression step" } }, "required": ["issueKey", "transitionId"] }

• get_board_sprints: Retrieves sprint records associated with a Jira board.

• Description: Fetches the complete list of sprints linked to a designated Jira agile board.

• Input Schema:

  { "type": "object", "properties": { "boardId": { "type": "string", "description": "The unique ID of the Jira board" }, "state": { "type": "string", "description": "Constraint for sprint status filtering", "enum": ["active", "future", "closed"] } }, "required": ["boardId"] }

• get_sprint_issues: Fetches all tickets within a specific sprint boundary.

• Description: Retrieves all associated issues contained within a defined sprint identifier.

• Input Schema:

  { "type": "object", "properties": { "sprintId": { "type": "string", "description": "The unique ID of the sprint" }, "fields": { "type": "array", "items": { "type": "string" }, "description": "A catalogue of specific data fields requested for each issue object" } }, "required": ["sprintId"] }

• get_current_sprint: Queries the active sprint details and its contained tasks for a board.

• Description: Retrieves metadata for the presently active sprint on a board, optionally including its associated work items.

• Input Schema:

  { "type": "object", "properties": { "boardId": { "type": "string", "description": "The identifier for the relevant Jira board" }, "includeIssues": { "type": "boolean", "description": "Flag to mandate inclusion of sprint work items in the reply", "default": true } }, "required": ["boardId"] }

• get_epic_issues: Retrieves all work items categorized under a specific epic.

• Description: Lists every issue entity that maps directly to the specified Jira Epic key.

• Input Schema:

  { "type": "object", "properties": { "epicKey": { "type": "string", "description": "The identifier key for the Epic (e.g., CONNECT-1234)" }, "fields": { "type": "array", "items": { "type": "string" }, "description": "A selection of data attributes requested for the returned issues" } }, "required": ["epicKey"] }

• get_user_issues: Fetches tickets linked to a user on a specified board.

• Description: Returns a collection of issues either delegated to or reported by a designated user on a particular board context.

• Input Schema:

  { "type": "object", "properties": { "boardId": { "type": "string", "description": "The ID of the operational Jira board" }, "username": { "type": "string", "description": "The system identifier for the user to look up" }, "type": { "type": "string", "description": "Defines the relationship type between user and issue", "enum": ["assignee", "reporter"], "default": "assignee" }, "status": { "type": "string", "description": "Criteria to filter issues by current lifecycle state", "enum": ["open", "in_progress", "done", "all"], "default": "all" } }, "required": ["boardId", "username"] }