Skip to main content
Glama

Jira + Confluence MCP

An MCP server for self-hosted Atlassian Jira and Confluence Server/Data Center. Each person configures their own internal instance URL and personal access token. The repository contains no company-specific URL or credential.

What it supports

Convenience tools cover common read/write workflows:

  • Jira: current user, JQL issue search, get/create/update/delete issues, projects, comments, workflow transitions, worklogs, Agile boards and sprints, and issue links.

  • Confluence: current user, CQL search, spaces, get/create/update/delete pages, comments, and attachment listing.

  • jira_rest and confluence_rest expose JSON REST endpoints for additional Server/Data Center features, including Jira Service Management and installed REST plugins. Paths are restricted to the configured product host and its /rest/ tree.

The user's Jira/Confluence permissions still govern every operation. The generic REST tools can perform writes and deletes; use them carefully. This project targets Server/Data Center, not Atlassian Cloud.

Related MCP server: Atlassian Data Center MCP

How it works

This MCP server connects to Jira and Confluence through their REST APIs; it does not connect to either product's database. The flow is:

  1. An MCP client (for example, an AI assistant) starts this server over the local stdio transport.

  2. The client calls a named tool, such as jira_search_issues or confluence_get_page.

  3. The server sends the matching REST API request to the configured internal Jira or Confluence URL, authenticating with that user's personal access token.

  4. Jira or Confluence checks the user's permissions, performs the requested read or write, and returns a response through the MCP server to the client.

For write tools, the change is made in Jira or Confluence itself and remains subject to the configured user's permissions. The MCP process must run on a machine that can reach the company's internal hosts, such as a workstation connected to the company network or VPN.

Requirements

  • Node.js 20 or newer

  • Jira Core/Software 8.14+ for personal access tokens

  • Confluence 7.9+ for personal access tokens

  • Network access from the MCP host to the company's Jira and Confluence hosts

Atlassian Server/Data Center personal access tokens are sent as Authorization: Bearer …. Tokens belong in the MCP client's private environment configuration, never in this repository, tool arguments, logs, or committed .env files.

Configure

  1. Create one personal access token in Jira and one in Confluence. Give each account only the permissions it needs. The products can use the same token only if your installation explicitly supports that token for both.

  2. Copy .env.example to a private location or place the values directly in your MCP client's server configuration. Do not commit real values.

  3. Set each product's base URL. A context path is allowed and must be included, e.g. https://jira.sitename.ir/jira or https://wiki.sitename.ir/confluence. The two products may also be on the same domain.

Example environment:

JIRA_BASE_URL=https://jira.sitename.ir
JIRA_PERSONAL_ACCESS_TOKEN=your-own-jira-token
CONFLUENCE_BASE_URL=https://confluence.sitename.ir
CONFLUENCE_PERSONAL_ACCESS_TOKEN=your-own-confluence-token
MCP_ALLOW_INSECURE_HTTP=false

Use HTTPS. If an internal server uses a private CA, configure Node with NODE_EXTRA_CA_CERTS=/path/to/company-ca.pem; TLS verification remains enabled. Set MCP_ALLOW_INSECURE_HTTP=true only when the internal service is intentionally HTTP-only and the network is trusted.

Build and run

npm install
npm run build
node dist/index.js

For local development, npm run dev runs the TypeScript entry point through tsx.

MCP client example

Configure the MCP host to launch the built server and inject secrets through its private environment configuration. Example shape for clients that use JSON MCP settings:

{
  "mcpServers": {
    "jira-confluence": {
      "command": "node",
      "args": ["/absolute/path/to/jira-confluence-mcp/dist/index.js"],
      "env": {
        "JIRA_BASE_URL": "https://jira.sitename.ir",
        "JIRA_PERSONAL_ACCESS_TOKEN": "<enter-your-own-token-in-your-local-settings>",
        "CONFLUENCE_BASE_URL": "https://confluence.sitename.ir",
        "CONFLUENCE_PERSONAL_ACCESS_TOKEN": "<enter-your-own-token-in-your-local-settings>"
      }
    }
  }
}

Do not paste tokens into chat or source control. A token is only revealed once when created; revoke it in Atlassian if it is exposed.

Tool usage notes

  • Jira search uses JQL. startAt and maxResults control pagination.

  • Jira writes use the Jira Server/Data Center REST API v2; Agile tools require Jira Software.

  • Confluence search uses CQL. start and limit control pagination.

  • Confluence page bodies use the Confluence Storage Format. Updates read the current version, increment it, and can check expectedVersion for conflicts.

  • Generic REST paths are relative to /rest/. Examples: api/2/issue/ABC-1, agile/1.0/board, servicedeskapi/request, api/content/123, and your-plugin/1.0/resource.

  • Endpoints requiring binary multipart uploads are not exposed through the JSON generic REST tools.

  • Large REST responses are capped at 100,000 characters in tool output.

Security

  • No hard-coded Jira/Confluence URL, token, username, or password.

  • HTTPS is required by default. HTTP requires an explicit opt-in.

  • TLS certificate validation stays enabled; use the company's CA certificate with Node's NODE_EXTRA_CA_CERTS when needed.

  • Request paths cannot select another hostname or escape the configured context path.

  • Tokens are sent only in the Authorization header and are redacted from API error bodies.

  • Write tools act with the configured user's permissions. Use read-only PATs unless write access is required.

References

License

MIT. See LICENSE.

Available Tools

27 tools
confluence_add_commentAdd Confluence page commentC

Add a comment to a Confluence content item as the authenticated user.

Inputs: contentId (required), bodyStorage (required).

confluence_create_pageCreate Confluence pageA

Create a page in a space. bodyStorage must be Confluence Storage Format markup, commonly HTML with Confluence macros. Optionally set parentPageId to create a child page.

Inputs: title (required), spaceKey (required), bodyStorage (required), parentPageId.

confluence_delete_pageDelete Confluence pageC
Destructive

Delete or archive a Confluence content item according to the server's REST API and permissions. This is destructive.

Inputs: contentId (required).

confluence_get_current_userGet Confluence current userA
Read-only

Return the authenticated Confluence user.

Inputs: no named parameters.

confluence_get_pageGet Confluence pageB
Read-only

Read a Confluence content item by ID, including body, version, space, and ancestors by default.

Inputs: contentId (required), expand.

confluence_list_attachmentsList Confluence attachmentsC
Read-only

List attachments on a Confluence content item. Use start and limit for pagination.

Inputs: contentId (required), limit, start, expand.

confluence_list_commentsList Confluence page commentsC
Read-only

List comments on a content item. Use start and limit for pagination.

Inputs: contentId (required), limit, start, expand.

confluence_list_spacesList Confluence spacesB
Read-only

List spaces visible to the authenticated user. Use start and limit for pagination.

Inputs: type, limit, start, expand, +1 more.

confluence_restCall Confluence REST APIA
Destructive

Call any JSON Confluence Server/Data Center REST endpoint on the configured Confluence host. apiPath is relative to /rest/, for example api/content, api/content/123/child/attachment, or api/search. Supports GET, POST, PUT, PATCH, DELETE. Never put credentials in apiPath, query, or body. Write and delete calls act as the configured user.

Inputs: method (required), apiPath (required), body, query.

confluence_update_pageUpdate Confluence pageA

Update a page's title and/or storage-format body. The server reads the current version and increments it. Set expectedVersion to prevent overwriting a page that changed since you read it.

Inputs: contentId (required), title, bodyStorage, versionMessage, +1 more.

jira_add_commentAdd Jira issue commentB

Add a comment to an issue as the authenticated Jira user.

Inputs: body (required), issueKey (required).

jira_add_worklogAdd Jira worklogB

Record work against an issue. Use Jira's duration syntax for timeSpent and an ISO date-time for started.

Inputs: started (required), issueKey (required), timeSpent (required), comment.

jira_create_issueCreate Jira issueB

Create an issue. Provide Jira's fields object, including project, issuetype, and summary as required by your configuration.

Inputs: fields (required).

jira_delete_issueDelete Jira issueA
Destructive

Permanently delete an issue. This is destructive and depends on the user's Jira permissions.

Inputs: issueKey (required), deleteSubtasks.

jira_get_current_userGet Jira current userA
Read-only

Return the authenticated Jira user. The Jira server and personal access token are read from this MCP process's private environment.

Inputs: no named parameters.

jira_get_issueGet Jira issueB
Read-only

Read one issue by key or numeric ID.

Inputs: issueKey (required), expand, fields.

jira_list_boardsList Jira Agile boardsB
Read-only

List visible Jira Software boards. Jira Software must be installed for this endpoint.

Inputs: name, startAt, maxResults, projectKeyOrId.

jira_list_commentsList Jira issue commentsC
Read-only

List comments visible to the authenticated Jira user.

Inputs: issueKey (required), startAt, maxResults.

jira_list_projectsList Jira projectsC
Read-only

List visible Jira projects with pagination.

Inputs: query, startAt, maxResults.

jira_list_sprintsList Jira board sprintsC
Read-only

List sprints for a Jira Software board. Optionally filter by active, future, or closed state.

Inputs: boardId (required), state, startAt, maxResults.

jira_list_transitionsList Jira issue transitionsB
Read-only

Return workflow transitions currently available for an issue.

Inputs: issueKey (required).

jira_restCall Jira REST APIA
Destructive

Call any JSON Jira Data Center REST endpoint on the configured Jira host. apiPath is relative to /rest/, for example api/2/issue/ABC-1, agile/1.0/board, or servicedeskapi/request. Supports GET, POST, PUT, PATCH, DELETE. Never put credentials in apiPath, query, or body. Write and delete calls act as the configured user.

Inputs: method (required), apiPath (required), body, query.

jira_search_issuesSearch Jira issuesB
Read-only

Search issues using Jira Query Language (JQL). Use startAt and maxResults for pagination; fields can restrict returned data.

Inputs: jql (required), expand, fields, startAt, +1 more.

jira_transition_issueTransition Jira issueA

Move an issue through a currently available workflow transition. Call jira_list_transitions first to find a valid transition ID.

Inputs: issueKey (required), transitionId (required), fields, comment.

jira_update_issueUpdate Jira issueC

Update an issue's fields. Jira applies the authenticated user's permissions and workflow rules.

Inputs: fields (required), issueKey (required), notifyUsers.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target a clear resource/action pair, and the jira_/confluence_ prefixes keep domains separate. The main ambiguity is the two generic *_rest tools, which overlap with every dedicated tool, though their escape-hatch role is clearly described.

    Naming Consistency5/5

    All tools use snake_case with a domain prefix and predictable verb_noun phrasing (list/get/create/update/delete/add/search). The generic REST tools are the only nonstandard action but still fit the prefix convention.

    Tool Count3/5

    27 tools is on the heavy side, especially with generic REST catch-alls that can perform many of the same operations as dedicated tools. The dual Jira+Confluence scope makes the breadth defensible, but it is still borderline heavy.

    Completeness4/5

    Core issue/page CRUD, search, comments, transitions, projects, spaces, boards, sprints, worklogs, and attachments listing are covered. Gaps like comment update/delete, worklog listing/removal, issue-link removal, and attachment mutation exist but are workable through the generic REST tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage self-hosted Atlassian Jira Server/Data Center issues and Bitbucket Server/Data Center repositories, pull requests, branches, commits, and files through MCP tools.
      44 npm
      4
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables MCP clients to work with self-hosted Jira Server / Data Center 8.x through entity-based core tools, JSON-declared plugin tools, and bundled Zephyr Scale. It supports issue, comment, worklog, attachment, project, user, link, watcher, agile, and test management operations using Basic Auth or PAT with runtime field discovery.
      97
      26 npm
      MIT