NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI · #4729 most downloaded on PyPI
The Model Context Protocol (MCP) Atlassian integration is an open-source implementation that bridges Atlassian products (Jira and Confluence) with AI language models following Anthropic's MCP specification. This project enables secure, contextual AI interactions with Atlassian tools while maintaining data privacy and security. Key features include:
Last release 1 months ago
19 Aug 2026
Release timing varies
gaps range from 9 days to 5 months
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
83 releases · first in 2024
Maintenance release cut from v0.23.0 . It contains exactly two fixes — a security patch and a dependency compatibility pin — and none of the ongoing v
Maintenance release cut from v0.23.0. It contains exactly two fixes — a security patch and a dependency compatibility pin — and none of the ongoing v0.24.0 development on main.
/sse and /messages endpoints of --transport sse now enforce the same per-request authentication as the streamable-HTTP transport. Full details in the security advisory published alongside this release. Upgrading is strongly recommended for anyone running the SSE transport.atlassian-python-api below v5 (#1585, #1589): atlassian-python-api 5.0 removed core Confluence Cloud methods (get_page_by_id, create_page, update_page), so fresh installs that resolved the new major failed with AttributeError on basic page operations. The dependency is now bounded to >=4.0.0,<5.0.0 and a regression test guards the contract. Thanks @breezeFur for the fix and @mihnatova for the detailed report.Thanks to @breezeFur for the dependency fix and @mihnatova for the report that pinpointed #1585.
Full Changelog: v0.23.0...v0.23.1
One column per month.
Upgraded the bundled FastMCP framework from 2.x to 3.x, clearing known vulnerabilities in the 2.x line ( #1234 , #1348 ). The migration preserves the…
This release adds JSM customer-request and internal-comment support, epic hierarchy and dependency tools, PAC/WPAD and mTLS connectivity, external auth passthrough, and Live Docs page creation, plus a broad batch of Jira/Confluence content fixes and security updates to Starlette and FastMCP.
jira_get_request_types, jira_get_request_type_fields, and jira_create_customer_request — let clients list request types, inspect their visible fields, and raise customer requests with participants, base64 attachments, and on-behalf-of support (#1241)jira_get_project_epic_hierarchy groups a project's epics under their cross-project parent issues with direction-aware link classification, and jira_get_cross_project_dependencies maps issue links by target project and link type (#1286)jira_get_issue and jira_search accept use_display_names to return human-readable custom field keys such as Story Points instead of opaque IDs like customfield_10243; conflicting names safely fall back to the raw ID (#1156)browse_url pointing at the issue's /browse/ page, for quick open-ticket-in-browser workflows (#1471)jira_update_issue accepts return_fields to trim the post-update re-fetch and cut response tokens; the full-issue default is unchanged (#1466){expand:Title} blocks in issue descriptions convert to native collapsible sections on Cloud, including nested headings, lists, and code blocks (#1309)application_type is omitted, so custom connectors are found without guessing exact casing (#1329)- [ ] / - [x]) convert to native Confluence task macros instead of literal checkbox text, and new page template tools let you list Cloud templates, fetch them, and create pages from them (#1180)subtype — including live for Live Docs — on Cloud, and page responses expose the subtype (#1479)MCP_ALLOWED_URL_DOMAINS to prevent credential exfiltration (#1457)cert auth type for Server/DC deployments that use mutual TLS: a client certificate/key pair alone now authenticates — previously setting JIRA_CLIENT_CERT / CONFLUENCE_CLIENT_CERT without a username or token left the service silently disabled (#1196)jira_get_issue_comments no longer crashes with a TypeError on Cloud, where REST v3 returns comment bodies as ADF — bodies are converted to text the same way the add/edit comment paths already do (#1489)jira_download_attachments returns non-image attachments as TextContent with a JSON envelope (base64 payload, filename, MIME type) instead of an EmbeddedResource blob that some MCP clients reject; images keep the embedded form (#1469)/browse/ URL when converted to ADF (#1468)jira_add_comment accepts comment as a compatibility alias for the body parameter, so clients sending the older shape no longer fail argument validation (#1467)B7-214-68901 (Server/DC) pass validation and are preserved by smart-link extraction (#1476)jira_get_issue and jira_search are offloaded from the MCP event loop and bounded by JIRA_FETCHER_MAX_WORKERS (default 8), keeping the server responsive under concurrent issue reads (#1459)Epic issue type match, so custom types like Program Epic are no longer selected by accident (#1370)created / updated timestamps are routed through format_timestamp, returning localized timestamps instead of raw ISO strings (#1236)type=space return results instead of an empty list — space-type result items are now mapped and matched for excerpts (#1119, closes #907)created / updated / author metadata again by expanding nested content history and version fields (#1480)ancestors, and Cloud OAuth/PAT route through v2 with a storage-body fallback (#1485)markdown-to-confluence 0.6 while preserving attachment handling, code-language normalization, table-layout conversion, and task-list behavior (#1486)confluence_set_page_restrictions list parameters now declare an items schema, unblocking VS Code Agent mode, which rejected the generated tool schema entirely (#1487, closes #1455)<time datetime="..."> elements survive storage-to-Markdown conversion (#1107)*_SSL_VERIFY and proxy settings instead of hardcoding SSL verification on and disabling proxies (#1211)NO_PROXY bypass the proxy even when proxies are explicitly configured on the session (#1191)ToolErrors instead of generic masked errors, and Confluence search helpers no longer return empty success results for API/network failures (#1316, closes #1315)MCP_ATLASSIAN_VALIDATION_CACHE_TTL, default 300s; 0 disables), cutting a validation round-trip from every request. Cache keys are SHA-256 material scoped by service and credential, so raw tokens are never stored (#1481, closes #1405)>=1.0.1) for GHSA-86qp-5c8j-p5mr, with a malformed Host header regression test covering the path-based middleware gates (#1470)ENABLED_TOOLS, or toolset filtering remain both unlisted and uncallable, and denials are indistinguishable from unknown tools (#1442, supersedes #1388)projects_filter values are quoted as JQL literals and grouped so they cannot escape the configured allowlist, caller-controlled destinations stay on the direct DNS-pinned connection path when deployment proxies are configured, and relative redirect locations are resolved before SSRF validation (#1450)JIRA_INTERNAL_ONLY_PROJECTS configured, comments created through the add, edit, transition, and issue-link paths in those projects are enforced as internal, so AI-authored comments cannot leak to service-desk customers. The guard fails closed unless Jira explicitly reports the comment as non-public (#1478)JIRA_INTERNAL_ONLY_PROJECTS handling against invisible characters — zero-width characters or a BOM in configured project keys or incoming issue keys could previously make the guard fail open. Keys are now normalized, and entries that cannot match a valid project-key shape produce a warning (#1491)Expanded regression coverage for Jira REST API v3 (#1110, closes #338), web and Confluence remote links (#1108), dynamic Epic Link fields (#1113), JSM queue request contracts (#1115), custom field option values (#1464, closes #673), and jira issues/epics (#1497); a deterministic rate-limit throttle test (#1449); a TruffleHog secret-scanning CI workflow (#1265); and setup docs for Autohand Code (#1472).
Thanks to @trentzeigler (#1442, #1388), @sanjibani (#1489, #1487), @saidelike (#1367, #1459), @keithxm23 (#1196), @WZHBEDZ (#1316), @Troubladore (#1119, #1107), and @cblacknygc (#1497)!
Additional thanks to the contributors whose original work was carried into this release: @faizbawa, @kbichave, @deniszagitov, @slinkardbrandon, @cedrickcom, @trevorh, @jcbportela, @NickLoeza, @abhinavgaba, @tony-davis, @Niicolaa, @timwinders, and @balcsida.
Full Changelog: v0.22.1...v0.23.0
Prevented caller-supplied projects_filter values from injecting JQL operators that could escape the configured project allowlist. Filter values with J
projects_filter values from injecting JQL operators that could escape the configured project allowlist. Filter values with JQL syntax are now quoted as literals, and generated project clauses are explicitly grouped. (#1450)Full Changelog: v0.22.0...v0.22.1
…eliminating the DNS-rebinding TOCTOU against the CVE-2026-27826 fix. Hosts from your configured JIRA_URL / CONFLUENCE_URL and MCP_ALLOWED_URL_DOMAINS…
This release bundles three months of community contributions with a coordinated security hardening pass across the attachment, transport, SSRF-validation, filtering, and OAuth layers.
A security audit (37 advisories, consolidated into root-cause families) was resolved in this release. Advisories are being published with "fixed in 0.22.0" — highlights:
upload_attachment / download_attachment (Jira & Confluence) and the new content_file page input now validate every caller-supplied path against the workspace via validate_safe_path, closing arbitrary file read/exfiltration and an intra-CWD overwrite RCE variant. Note: paths passed to these tools must now resolve inside the server's working directory. (GHSA-wm45-qh3g-v83f, GHSA-vc25-24vv-fxxm, GHSA-93xw-j965-9mx3, GHSA-6cr4-ccf3-x7h4, GHSA-f4p7-qx46-wc5j, GHSA-f6pj-qv47-g96w, GHSA-2xj6-xx86-cwwc, GHSA-mrq8-fv7v-hhjg, GHSA-wv8v-v4c5-v75j, GHSA-p6hp-93wp-fh6p, GHSA-h7wj-5v37-59r2, GHSA-mfv2-4wvm-9pgp, GHSA-f26r-j276-ggg4, GHSA-g5r6-gv6m-f5jv, GHSA-6vmq-24h2-pj7j)ALLOW_GLOBAL_CRED_FALLBACK (default off), and unauthenticated requests are rejected with 401 at the transport boundary. (GHSA-wrhw-j3f9-8vc6, GHSA-vc8m-84rp-53hx, GHSA-cc5h-2pwp-pvcc)JIRA_URL / CONFLUENCE_URL and MCP_ALLOWED_URL_DOMAINS are exempt from the non-global-address rejection, so on-prem DC instances on private networks keep working; caller-supplied URLs (multi-user HTTP headers) remain fully guarded. (GHSA-6529-c226-h328, GHSA-hgcf-4mq8-5266, GHSA-v9m3-wfh8-5646, GHSA-5wf4-jqxh-8gm3, GHSA-49xv-9743-pw8w, GHSA-72fm-whvq-jghf, GHSA-489g-7rxv-6c8q, GHSA-6rrj-86cw-gg9j)ENABLED_TOOLS / toolset / read-only mode can no longer be invoked by name; authorization is enforced at dispatch, not just listing. (GHSA-3r68-hf9h-887v)JIRA_PROJECTS_FILTER / CONFLUENCE_SPACES_FILTER are now a hard boundary: always ANDed into queries (callers can narrow but never widen), covering search and board issues. Sprint IDs are validated numeric to prevent JQL injection. (GHSA-w66g-j6c4-hcfc, GHSA-rqwg-9346-fjjv)Each fix ships with permanent regression tests. Thanks to everyone who reported — including @rainfantry for GHSA-g5r6-gv6m-f5jv, and overlapping public reports from @failsafesecurity and @rober15.
assign_issue tool (#1152) and search_assignable_users for free-form user lookup (#1358)jira_move_issue for cross-project moves (#1273) and move_issues_to_backlog (#1333)jira_search_projects using the projects picker API (#1247)update_version tool (#1349)get_issue gains an include param for inline enrichments (#1125)- [ ] → taskList (#1280), [~accountid:UUID] mentions (#1307), display-name mentions (#1228)account_id exposed in simplified user profiles (#1347)confluence_update_page_section for lossless partial page updates (#1141)content_file input for create/update page (#1275)content_base64 input for upload_attachment — upload from in-memory content when the server can't read host file paths (#1366)get_page resolves Confluence tiny links and page URLs (#1222)update_issue: null values clear fields (#1140); loud failure when assignee can't be resolved (#1380); tolerate default comment fields (#1334)get_worklogs returns all entries (#1223); newest comments first when limiting (#1218)'me' identifier in get_user_profile (#1120); sub-task name match preference (#1331); version field allowed in issue field selection (#1227)get_all_projects output (#1291)/wiki prefix on upload/delete (#1386); v1 REST endpoint for downloads (#1369)get_page_content expand (#1117)ri:userkey / ri:username handling (#1298); bare-filename img tags become attachment macros (#1176)Full Changelog: v0.21.1...v0.22.0
This release fixes a critical startup crash caused by an upstream dependency break and ships a few community-contributed features that landed on main
This release fixes a critical startup crash caused by an upstream dependency break and ships a few community-contributed features that landed on main since v0.21.0.
uvx installs: fakeredis 2.35.0 renamed FakeConnection without a backward-compatible alias, breaking pydocket's runtime import and making FastMCP's lifespan fail with ImportError: cannot import name 'FakeConnection' from 'fakeredis.aioredis'. Pinned fakeredis>=2.32.1,<2.35.0 as a downstream constraint until upstream ships a fix. Users no longer need the --with fakeredis==2.34.1 workaround (#1250, fixes #1248).include_content test coverage and descriptions: Follow-up hardening for the new include_content option (#1099).include_content on create/update: confluence_create_page and confluence_update_page now accept an include_content flag so callers can skip echoing full page bodies back in responses (#1098).confluence_get_space_page_tree: New tool for discovering a space's page hierarchy in a single call (#1090).Thanks to @kimoto, @Poggen, and @Troubladore!
Full Changelog: v0.21.0...v0.21.1
This release adds 4 new tools (sprint management, page moves, page diffs, comment replies), OAuth proxy support, markdown table rendering, and multipl
This release adds 4 new tools (sprint management, page moves, page diffs, comment replies), OAuth proxy support, markdown table rendering, and multiple content processing fixes.
jira_add_issues_to_sprint tool (#1078)jira_search now returns next_page_token for cursor-based pagination on Cloud (#1079)jira_get_field_options supports contains, return_limit, and values_only params for targeted lookups (#1074)confluence_move_page tool (#1080)confluence_get_page_diff tool (#1083)confluence_reply_to_comment tool (#1070)default / full-width) on Cloud. Available via the Confluence fetcher API; MCP tool integration planned for a future release (#1091)confluence_search_user now supports Server/DC via group member fallback (#1081)IGNORE_HEADER_AUTH env var to ignore proxy-injected Authorization headers and use server-configured credentials (#1073){code} and {noformat} blocks in Server/DC wiki markup are now protected from markup conversion corruption (#1059){panel} blocks and bare URLs in wiki markup are now correctly converted to markdown (#1055)fixVersions, issuetype, and other API field names are now correctly recognized in should_include_field checks, fixing field exclusion when users request specific fields (#1076)<code>) are no longer broken by HTML content truncation (#1094)evil-atlassian.net could match the atlassian.net domain check — now uses strict .{domain} suffix matching (#1087)Thanks to @Poggen, @Troubladore, @djb2c, @Lama9, @iiiokojiadbi, @Arbuzov, @solganik, @johnny, @pibylick, @nulvox, @yliu, and @reneleonhardt!
Full Changelog: v0.20.1...v0.21.0
This release fixes error handling for the ServiceDesk comment API on non-JSM projects.
This release fixes error handling for the ServiceDesk comment API on non-JSM projects.
public parameter for internal/external comments. The error message now clearly indicates the issue is not a JSM service desk project or the user lacks permission (#1051)Full Changelog: v0.20.0...v0.20.1
This release adds JSM internal comment support, a Kubernetes Helm chart, and fixes for worklog ADF handling and tool parameter naming.
This release adds JSM internal comment support, a Kubernetes Helm chart, and fixes for worklog ADF handling and tool parameter naming.
public parameter on add_comment tool for Jira Service Management issues. Set public=true for customer-visible comments or public=false for internal agent-only comments. Routes through the ServiceDesk API with plain text body (#1049, fixes #867)_markdown_to_jira() were posted to the v2 API which ignores them. Now routes through v3 API when the comment is ADF, matching the existing pattern in comments (#1047, fixes #1045)comment_body → body, issue_description → description, etc. (#1044)Thanks to @antweiss, @baumgold, and @hteichmann-strato!
Full Changelog: v0.19.0...v0.20.0
This release adds toolset-based tool filtering for granular control over which tools are exposed, OS native trust store support for enterprise SSL env
This release adds toolset-based tool filtering for granular control over which tools are exposed, OS native trust store support for enterprise SSL environments, and Jira issue watcher tools.
TOOLSETS env var groups 68 tools into 21 named toolsets (15 Jira, 6 Confluence) for granular control. Supports all, default, and comma-separated names. All toolsets enabled by default — in v0.22.0 the default will change to 6 core toolsets only (#1041, #1043)jira_get_issue_watchers, jira_add_watcher, and jira_remove_watcher tools for managing issue watchers. Write operations respect READ_ONLY_MODE (#1039, fixes #1032)truststore, enabling enterprise environments with internal CAs to connect without disabling SSL verification. Opt out with MCP_ATLASSIAN_USE_SYSTEM_TRUSTSTORE=false (#976)JiraUser.from_api_response() was mapping displayName to both display_name and name, discarding the login username needed for Server/DC [~username] mentions. Now preserves username and user_key fields separately (#1038, fixes #1031)D_DEV-123 were not recognized in both server tools and preprocessing due to missing _ in regex character classes (#1030, #1035)OverflowError/OSError on Windows. parse_date now catches these and returns None gracefully (#1037, fixes #1033)AttributeError when .env contains a bare key (no = sign) — dotenv_values() returns None which broke .lower() at import time (#1036)ALLOWED_DOMAINS now bypass DNS resolution checks, fixing false rejections for internal hostnames (#1005)Thanks to @tsondergaard, @fatherlinux, @alvaroEset, and @bbkmike!
Full Changelog: v0.18.0...v0.19.0
This release fixes allowlisted domains being incorrectly blocked by the SSRF DNS resolution check.
This release fixes allowlisted domains being incorrectly blocked by the SSRF DNS resolution check.
MCP_ALLOWED_URL_DOMAINS was set, internal hosts resolving to private IPs (e.g. 10.x.x.x) were still blocked by the DNS check. Allowlisted domains now return early before DNS resolution, while hard-blocked hostnames (localhost, metadata.google.internal) and IP literal checks remain enforced (#1005, fixes #1002)Thanks to @autumnjava for reporting!
Full Changelog: v0.18.0...v0.18.1
This release adds inline image rendering for both Jira and Confluence, ADF write support for Jira Cloud, and fixes several bugs including stateless HT
This release adds inline image rendering for both Jira and Confluence, ADF write support for Jira Cloud, and fixes several bugs including stateless HTTP mode and Server/DC user lookup.
jira_get_issue_images tool returns issue image attachments as base64 ImageContent for direct LLM vision processing. Shared MIME detection extracted to utils/media.py (#1001)confluence_get_page_images tool returns page image attachments as base64 ImageContent with two-tier MIME detection and 50MB size limit (#992)<ac:image> XML tags are now converted to standard markdown image syntax during page preprocessing, with support for both attachment references and external URLs (#991)atlassian-python-api sends to /rest/api/2/ by default, which rejects ADF dict payloads. Added _post_api3()/_put_api3() helpers to route create/update/comment operations through /rest/api/3/ when the payload contains ADF (#1003, fixes #994)j-smith2 as Jira keys. Email identifiers now resolve via /rest/api/2/user/search before profile fetch (#999, #998)schema.type: "array" are now passed through unchanged instead of being incorrectly formatted as strings (#993)fetch_attachment_content() to Confluence, eliminating duplicated inline download logic in server tools (#989)stateless_http was broken since v0.13.1 because the global settings mutation happened after FastMCP.__init__() had already snapshotted them. Now passed explicitly via run_kwargs (#1000, fixes #997)Thanks to @kalabj, @TerminalGravity, @sigismund, @miwamoto, and @gudim!
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.17.0...v0.18.0
This release fixes two security vulnerabilities, adds new Jira features, and includes multiple bug fixes and hardening improvements.
This release fixes two security vulnerabilities, adds new Jira features, and includes multiple bug fixes and hardening improvements.
validate_safe_path() with symlink resolution. Jira guards refactored to use the same shared utility. Fixes GHSA-xjgw-4wvw-rgm4 (#987)X-Atlassian-*-Url) are now validated against SSRF — blocks private IPs, DNS rebinding, and redirect-based attacks. Optional domain allowlist via MCP_ALLOWED_URL_DOMAINS. Fixes GHSA-7r34-79r5-rcc9 (#986)jira_get_service_desk_queues, jira_get_queue_issues, and jira_get_queue_details tools for Server/DC (#979)jira_get_project_components tool to retrieve project components (#873)epicKey, epic_link, epicLink, and "Epic Link" now resolve correctly in create/update operations (#970)IF, AND) are now auto-quoted (#967)/wiki twice on Cloud (#964)uv lock --upgrade to resolve Trivy scan vulnerabilities (#977)>=0.3.4 to prevent ModuleNotFoundError on md2conf.metadata (#980)Thanks to @elisa-tfager, @hteichmann-strato, @JakubAnderwald, @legard, @ilgaur, and @yotampe-pluto!
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.16.1...v0.17.0
This release fixes Confluence Cloud URL construction, adds AI platform schema compatibility, and patches a ReDoS vulnerability.
This release fixes Confluence Cloud URL construction, adds AI platform schema compatibility, and patches a ReDoS vulnerability.
/wiki Prefix in Cloud URLs: base_url already includes /wiki for Cloud instances (auto-appended by atlassian-python-api), but five URL constructions in v2_adapter.py and analytics.py were prepending it again — producing 404s for analytics views, page attachments, and attachment CRUD operations (#964, fixes #962)jira_get_issue used overlapping alternation that caused catastrophic backtracking on unmatched ?? markers — replaced with non-overlapping linear-time pattern (#948)anyOf flattening to fix JSON Schema incompatibilities with Vertex AI / Google ADK, Gemini, LiteLLM, and other AI platforms — 314 compatibility tests validate all tool schemas (d57b7fd, fixes #640, #733, #541, #484)e0beb97, a00fa4e)Thanks to @johnny, @wallacekabum, @XinyueZ, @CatsMiaow, and @stephen-galea-weavr!
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.16.0...v0.16.1
This release adds OAuth 2.0 for Atlassian Data Center, Basic Auth multi-user support for MCP gateways, and several auth reliability fixes.
This release adds OAuth 2.0 for Atlassian Data Center, Basic Auth multi-user support for MCP gateways, and several auth reliability fixes.
JIRA_OAUTH_CLIENT_ID, CONFLUENCE_OAUTH_CLIENT_ID), DC-specific token/authorize URLs, and keyring key namespacing (#952, fixes #527)Authorization: Basic <base64(email:api_token)> headers in middleware for multi-user MCP gateway scenarios, creating per-request fetchers with individual Atlassian Cloud credentials (#955, fixes #380)ATLASSIAN_OAUTH_ENABLE=true now works as a fallback when no service URL is configured, enabling Bring Your Own Token mode where users provide OAuth tokens via per-request headers (#956, fixes #698)JIRA_TIMEOUT and CONFLUENCE_TIMEOUT env vars (default 75s) propagated to atlassian-python-api client constructors (#950, fixes #891)~/.netrc entries — trust_env=False is set when explicit auth is provided (#951, fixes #860)/issue/createmeta/{project}/issuetypes) for Jira 9.x+, fixing jira_get_field_options, get_required_fields, and get_project_issue_types returning empty results on modern Server/DC (#958)ATLASSIAN_OAUTH_ENABLE=true (#954, fixes #858).env.example for DC OAuth, Basic Auth multi-user, BYOT mode, service-specific OAuth env vars, and HTTP timeouts (#957)Thanks to @blackalegator, @kangis89, @nealedj, @ckaytev, @hteichmann-strato, and @sergiobank!
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.15.0...v0.16.0
This release adds custom field options discovery, consolidates field formatting, and fixes several field-related bugs across create/update workflows.
This release adds custom field options discovery, consolidates field formatting, and fixes several field-related bugs across create/update workflows.
jira_get_field_options tool to discover allowed values for select, multi-select, radio, checkbox, and cascading select custom fields. Cloud uses the Field Context API with auto-resolution and pagination; Server/DC falls back to createmeta allowedValues (#944, fixes #686)_format_field_value_for_write method on FieldsMixin, adding schema-type handlers for cascading selects, multi-select options, custom user fields (Cloud/Server), custom dates, and generic options (#941, fixes #355)field_id.lower() instead of display names, fixing issues where fields with localized or duplicate display names were incorrectly matched (#941, fixes #770)update_issue JSON String Parsing: additional_fields parameter in jira_update_issue now accepts JSON strings in addition to dicts, matching jira_create_issue behavior (#941)update_issue: Add explicit components CSV parameter to jira_update_issue, matching jira_create_issue UX — previously required passing components through additional_fields JSON (#942, fixes #863)±HH:MM) to Jira's required basic format (±HHMM) — datetime custom fields could not be set at all before this fix (#942)id field in comment objects returned by jira_get_issue, enabling downstream use with jira_edit_comment and jira_delete_comment (#943, fixes #923)Thanks to @pibylick for the field options feature request, @dbalabka for reporting the missing comment ID, @mohsengachkoob for reporting the checklist field issue, @USAFSpawn for reporting the datetime timezone bug, and @rkochar11 for reporting the components update issue!
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.14.3...v0.15.0
Private Vulnerability Reporting: Enable GitHub private vulnerability disclosure and update SECURITY.md with responsible disclosure instructions (`e0b0…
This release fixes US Government Cloud (FedRAMP) compatibility, Homebrew packaging support, and Server/DC project key validation.
*.atlassian-us-gov-mod.net and *.atlassian-us-gov.net domains. Without this fix, US Gov Cloud instances were misidentified as Server/DC, causing HTTP 410 errors after the Jira v2 search API deprecation (#890)142d5d9, fixes #937)initialize → tools/list probe and closes stdin. The parent-process monitor now detects EOF promptly instead of blocking (74b32ec, fixes #939)e0b0f30, fixes #908)OSError/OverflowError crashes (d437876, fixes #916)Thanks to @maucher for the US Government Cloud fix!
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.14.2...v0.14.3
stdio transport broken (#935): Replace stdin-reading EOF guard with parent-process monitor. The previous implementation called sys.stdin.read() in an
stdio transport broken (#935): Replace stdin-reading EOF guard with parent-process monitor. The previous implementation called sys.stdin.read() in an executor thread, which held io.BufferedReader's internal lock until EOF — causing FastMCP's stdio reader to block indefinitely and produce silent stdout with no response to initialize. Now uses os.getppid() polling to detect orphan processes without touching stdin.
Python 3.14 support: Remove <3.14 upper bound from requires-python and relax pydantic to <3.0. This resolves pydantic 2.12.x → pydantic-core 2.41.5, which ships 28 pre-built cp314 wheels. The previous pydantic-core 2.33.2 had no Python 3.14 wheels and source builds failed because PyO3 0.24.1 does not support Python 3.14.
uvx mcp-atlassian@latest
SLA Tool Name: Rename jira_jira_get_issue_sla → jira_get_issue_sla (double-prefix bug from FastMCP tool registration)
jira_jira_get_issue_sla → jira_get_issue_sla (double-prefix bug from FastMCP tool registration) (#934)start_date is a date-only string (e.g., \"2026-03-01\") — was raising TypeError: can't compare offset-naive and offset-aware datetimes (#934)This release is a focused stability patch addressing community-reported bugs accumulated since v0.13.1.
This release is a focused stability patch addressing community-reported bugs accumulated since v0.13.1.
fields= kwarg in update_issue that broke all Jira issue updates after v0.13.0 (#926)assignee field is set (#925)jira_get_sprint_issues now respects the fields parameter correctly (#685)transition_issue now hits the correct /transitions REST endpoint (#659)confluence_get_page (#886)EmbeddedResource for proper MCP client handling (#929)This release brings significant new capabilities including Jira SLA metrics, ProForma forms support, development info integration, Confluence attachme
This release brings significant new capabilities including Jira SLA metrics, ProForma forms support, development info integration, Confluence attachment CRUD and page versioning, plus multi-tenant authentication and numerous stability fixes.
jira_get_issue_sla tool for querying SLA metrics on issues (#839)jira_get_issue_dates tool for retrieving issue date fields (#838)jira_update_issue (#901)confluence_get_page_views tool for page view analytics (#840)jira_get_issue_dates and confluence_get_page_views handlers (#927)jira_update_issue (#887)comment_limit is positive (#876)get_issue_transitions_full for complete transition data (#843)Thanks to all the contributors who made this release possible: @AmirhosseinHanifehzadeh, @brettfire, @ckreager, @HadjievK, @hiroishda, @hteichmann-strato, @IMKnysh, @jimweller, @jstoneburner, @major, @meliezer124, @mindmelting, @nigel-upstart, @saakshigupta2002, @saneroen, @WZHBEDZ
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.13.0...v0.13.1
This release adds mTLS support, stateless mode for streamable-http, and critical stability fixes for Windows and SSL connections.
This release adds mTLS support, stateless mode for streamable-http, and critical stability fixes for Windows and SSL connections.
jira:edit_comment tool for editing existing comments (#813)Thanks to all the contributors who made this release possible: @nhouck, @cary-hu, @4erdenko, @shoxst, @stewartthomson
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.12.0...v0.13.0
This release includes critical stability fixes for ASGI middleware and Docker, along with new configuration options and Jira 9+ compatibility.
This release includes critical stability fixes for ASGI middleware and Docker, along with new configuration options and Jira 9+ compatibility.
visibility parameter to jira:add_comment for controlling comment visibility (#689)Thanks to all the contributors who made this release possible: @CodingDoneRaitt, @danielfrey63, @njoshi-conga, @jtumidanski, @howell, @Erick, @GuilleGarcia, @jruus, @davyraitt
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.11.12...v0.12.0
This release adds MCP tool safety annotations, Confluence folder support, and Claude Code GitHub Action for AI-assisted reviews.
This release adds MCP tool safety annotations, Confluence folder support, and Claude Code GitHub Action for AI-assisted reviews.
readOnlyHint and destructiveHint annotations to all 42 tools for safer LLM decision-making (#789)get_page_children() results with graceful degradation (#787, fixes #165)<3.14 constraint for pydantic-core compatibility (#797, fixes #776)Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.11.11...v0.11.12
This release fixes critical ADF parsing issues, adds FastMCP 2.14.x support with security fixes, and improves read-only mode filtering.
This release fixes critical ADF parsing issues, adds FastMCP 2.14.x support with security fixes, and improves read-only mode filtering.
http_app() override and _list_tools_mcp method rename (#795)Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.11.10...v0.11.11
Jira Cloud Search API: Migrated Cloud search from deprecated v2 to v3 API endpoint, fixing search failures on Jira Cloud instances
This release fixes critical Jira Cloud search compatibility issues, improves Confluence page retrieval reliability, and enhances Multi-Cloud OAuth support.
JiraSearchResult.to_simplified_dict() method for easier integration and data processing (#585)body.storage.value gracefully when retrieving pages with empty or special content (#767).env.example for complete OAuth setup reference (#766).gitignore to include environment variable files with wildcard pattern (#583)ATLASSIAN_OAUTH_ENABLE in test mock environment (#587)Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.11.9...v0.11.10
Confluence OAuth v2 API: Added v2 API support for confluence_get_page to fix deprecated endpoint errors when using OAuth authentication
This release enhances corporate environment support, improves OAuth authentication reliability, and fixes critical issues with Jira Epic creation and Confluence API operations.
confluence_get_page to fix deprecated endpoint errors when using OAuth authentication (#579)JIRA_PROJECTS_FILTER with empty queries or ORDER BY clauses (#578)Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.11.8...v0.11.9
Removed deprecated decorator usage
This release introduces OAuth multi-cloud support, enhances Jira functionality, and fixes critical authentication and query issues.
X-Atlassian-Cloud-Id header and per-request authentication (#471)ATLASSIAN_OAUTH_ACCESS_TOKEN environment variable (#482)jira_create_remote_issue_link tool for creating web and Confluence links (#542)api.atlassian.com recognition for email-based user lookups (#561)markdown-to-confluence <0.4.0 and add version bounds (#558)str | None instead of empty string workarounds (#515)Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.11.7...v0.11.8
This release addresses critical compatibility issues affecting Windows environments, Jira Server status transitions, and Confluence page operations wi
This release addresses critical compatibility issues affecting Windows environments, Jira Server status transitions, and Confluence page operations with numeric IDs. These fixes enhance cross-platform stability and improve LLM client integration.
Windows Server Shutdown Stability: Resolved "ValueError: I/O operation on closed file" errors that occurred during server shutdown, particularly affecting Windows environments and Claude Desktop integration. The fix gracefully handles cases where parent processes close stdio pipes before the cleanup phase completes, ensuring clean exits without crashes (#532)
Jira Status Transitions: Fixed Method Resolution Order (MRO) conflict that prevented status updates on Jira Server/Data Center instances. The issue manifested as empty transition lists in error messages despite available transitions. The fix properly integrates TransitionsMixin methods and provides clear feedback about available status transitions (#455)
Confluence Numeric Parent IDs: Enhanced Confluence page operations to automatically handle numeric parent IDs sent by LLM clients (particularly Gemini). The API now seamlessly accepts both integer and string formats for parent_id parameters in create and update operations, preventing type validation failures (#452)
Enhanced Error Handling: Improved robustness in the shutdown sequence with comprehensive exception handling for various stream states, including closed streams, missing attributes, and flush failures (#533)
Test Coverage: Added extensive test cases for edge conditions in stream handling during shutdown, ensuring reliability across different operating systems and process termination scenarios
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.11.6...v0.11.7
This release adds native wiki markup support for Confluence page operations and simplifies the transport lifecycle testing infrastructure following th
This release adds native wiki markup support for Confluence page operations and simplifies the transport lifecycle testing infrastructure following the previous stdin monitoring fixes.
Wiki Markup Support for Confluence: Added comprehensive support for creating and updating Confluence pages using native wiki markup syntax and storage format. This enhancement enables users to leverage Confluence-specific features like {toc}, {panel}, and {change-history} macros that were previously unavailable with Markdown-only support. The implementation includes:
content_format parameter for confluence_create_page and confluence_update_page toolsTransport Lifecycle Test Simplification: Refactored the transport lifecycle test suite to align with the simplified architecture introduced in v0.11.5. After removing the problematic stdin monitoring functionality, all transports now behave identically, allowing for a cleaner and more maintainable test structure. The refactoring consolidates redundant tests while maintaining full regression coverage for issues #519 and #524 (#529)
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.11.5...v0.11.6
This release fixes a critical issue affecting streamable-http transport where sessions were terminated immediately after initialization, preventing su
This release fixes a critical issue affecting streamable-http transport where sessions were terminated immediately after initialization, preventing subsequent API calls in containerized environments.
Streamable-HTTP Session Management: Resolved session termination issue where HTTP transports (SSE and streamable-http) incorrectly used stdin monitoring, causing premature shutdown when clients closed their stdin. This prevented the initialize → tools/list flow from working correctly, with sessions being terminated and returning "Received request before initialization was complete" errors. The fix ensures HTTP transports rely solely on OS signals for shutdown while stdio transport continues to work correctly (#524)
Transport Lifecycle Test Suite: Added comprehensive test coverage for transport lifecycle behavior to prevent regression of stdin monitoring issues. The new tests verify that stdio transport correctly bypasses lifecycle monitoring while HTTP transports (SSE, streamable-http) use proper signal-based shutdown. These tests would have caught both issue #519 and #524 before shipping by detecting the race condition between MCP's stdio handler and lifecycle monitoring (#523)
Removed Flawed Lifecycle Function: Completely removed the run_with_stdio_monitoring function that was the root cause of both this issue and the previous stdio transport issue (#519). This function was fundamentally incompatible with MCP's architecture as it conflicted with the protocol's own use of stdin for communication. After the fixes in v0.11.4 and this release, the function was dead code and has been removed to prevent future issues.
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.11.4...v0.11.5
This release fixes a critical regression introduced in v0.11.3 that prevented the MCP Atlassian server from starting when using stdio transport in Doc
This release fixes a critical regression introduced in v0.11.3 that prevented the MCP Atlassian server from starting when using stdio transport in Docker containers.
🐛 Fixed
Docker stdio transport compatibility: Resolved a race condition where the lifecycle monitoring introduced in v0.11.3 conflicted with the MCP server's internal stdio handling. This caused immediate startup failures with "I/O operation on closed file" errors when running in Docker containers. The fix disables stdin monitoring for stdio transport while preserving the enhanced lifecycle management for SSE and HTTP transports (#522)
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.11.3...v0.11.4
Confluence OAuth v2 API Support: Resolved "This deprecated endpoint has been removed" errors by implementing ConfluenceV2Adapter for OAuth authenticat…
This release enhances Docker container integration with critical lifecycle management fixes, expands Jira project management capabilities with new version and project discovery tools, and strengthens the testing infrastructure with comprehensive integration tests.
Docker Lifecycle Management: Implemented comprehensive signal handling and stdin monitoring to ensure graceful shutdown in containerized environments. This critical enhancement resolves hanging container issues when using AI agent SDKs like OpenAI Agents SDK and Google ADK, which close stdin without sending proper shutdown signals (#514, #501)
Jira Project Discovery: Introduced the jira_get_all_projects tool to list all accessible Jira projects with optional archived project inclusion. The tool respects the JIRA_PROJECTS_FILTER configuration and returns comprehensive project metadata including keys, names, and project details (#493)
Jira Version Management: Added two new tools for managing project versions:
jira_create_version - Create individual project versions with optional metadata (#472)jira_batch_create_versions - Efficiently create multiple versions in a single operation with partial failure handling (#473)Confluence User Search: Introduced confluence_search_user tool with CQL query support for discovering Confluence users. Features automatic query conversion and comprehensive user data retrieval including account IDs, display names, and email addresses (#509)
Cloud Logging Compatibility: Added MCP_LOGGING_STDOUT environment variable to direct logs to stdout instead of stderr, resolving cloud platform logging categorization issues where DEBUG/INFO messages were incorrectly flagged as errors (#494)
Integration Testing Suite: Implemented comprehensive integration testing infrastructure with 127+ tests covering authentication flows, cross-service operations, SSL/proxy configurations, and real API validation. Includes --use-real-data flag for testing against live APIs (#517)
Confluence OAuth v2 API Support: Resolved "This deprecated endpoint has been removed" errors by implementing ConfluenceV2Adapter for OAuth authentication. The fix automatically routes OAuth requests to v2 API endpoints while maintaining backward compatibility for API token and basic auth users (#496)
VertexAI Schema Compatibility: Fixed function calling incompatibility by removing unsupported anyOf schema constructs in the confluence_search tool's spaces_filter parameter. VertexAI users can now successfully use Confluence search functionality (#497)
Environment Variable Backward Compatibility: Preserved existing behavior while adding new functionality by splitting environment variable validation into specialized functions:
is_env_truthy() for standard MCP variablesis_env_extended_truthy() for READ_ONLY_MODE with extended valuesis_env_ssl_verify() for SSL-specific logic (#516)Confluence Content Preservation: Fixed styling corruption during page updates by disabling automatic heading anchor generation. Styled content including colored highlights and code blocks are now preserved during create/update operations (#498)
Consistent Project Security: Made jira_get_issue honor the JIRA_PROJECTS_FILTER configuration, ensuring direct issue access respects the same project restrictions as search operations (#485)
Enhanced Error Handling: Improved error handling and performance in the jira_get_all_projects tool with:
LLM Development Guidelines: Added comprehensive AGENTS.md (now CLAUDE.md) with detailed architecture overview, repository map, development workflow, and quick reference commands for LLM-driven development (#491)
Simplified Authentication: Reorganized authentication documentation to position API Token as the recommended default method, with OAuth 2.0 marked as advanced. Updated .env.example with clearer precedence order and improved new user guidance (#468)
astral-sh/setup-uv@v3 action with caching enabled (#470).gitignore to exclude .claude/ directory and added stale bot workflow for automated issue/PR management (#492, #428)get_masked_session_headers() utility (#497)This release significantly improves container deployment reliability, expands project management capabilities, and establishes a robust foundation for future development with comprehensive testing and documentation enhancements.
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.11.2...v0.11.3
This release enhances Jira functionality with issue link support and project version management, while streamlining the development workflow with auto
This release enhances Jira functionality with issue link support and project version management, while streamlining the development workflow with automated versioning and improved authentication documentation.
Jira Issue Links Support: Added comprehensive support for the issuelinks field in Jira issues, enabling retrieval and representation of linked issues and their relationship types. This enhancement includes:
JiraIssueLinkType, JiraLinkedIssueFields, JiraLinkedIssue, and JiraIssueLinkJiraIssue model to parse and include issue links from API responsesto_simplified_dict output for better integration (#466)Jira Project Versions Tool: Introduced the new jira_get_project_versions tool to retrieve and list project versions (Fix Versions/Releases) from Jira projects. This foundational feature enables more advanced release-related automations and workflows (#463)
Automated Release Workflow: Implemented automated versioning and release management using:
PAT Authentication for Jira Data Center: Corrected authentication logic to consistently use "pat" as the auth_type for Personal Access Token authentication with Jira Data Center instances. Previously, there was a mismatch between configuration and client behavior that led to authentication failures (#461)
Improved Authentication Guidance: Reorganized authentication methods documentation to prioritize API Token (Method 1) as the recommended default for Cloud users, with OAuth 2.0 positioned as an advanced option. Updated .env.example and improved new user onboarding experience (#468)
astral-sh/setup-uv@v3 action for improved reliability and added caching (#470)This release strengthens mcp-atlassian's Jira integration capabilities while modernizing the development and release processes for better maintainability and user experience.
Full Changelog: v0.11.1...v0.11.2
Nothing published for this version
This is a hotfix release that addresses a critical bug affecting Jira write operations and improves the consistency of read-only mode handling across
This is a hotfix release that addresses a critical bug affecting Jira write operations and improves the consistency of read-only mode handling across all tools.
AttributeError: 'JiraConfig' object has no attribute 'read_only' that occurred when attempting to use Jira write tools. This issue (reported in #434) was caused by recent authentication refactoring. The read_only check now correctly uses the global application context.@check_write_access decorator to manage read-only mode restrictions. This ensures consistent behavior and makes the codebase cleaner. (PR #438)@check_write_access decorator in src/mcp_atlassian/utils/decorators.py for centralized read-only mode logic.This fix ensures that the READ_ONLY_MODE environment variable correctly restricts write operations for both Jira and Confluence tools as intended.
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.11.0...v0.11.1
This release marks a significant step forward in flexibility and user-specific interactions with mcp-atlassian. Version 0.11.0 introduces robust multi
This release marks a significant step forward in flexibility and user-specific interactions with mcp-atlassian. Version 0.11.0 introduces robust multi-user authentication for HTTP transports, expands Confluence capabilities with a new commenting tool and improved page lookup, and addresses important macro processing issues.
Multi-User Authentication for HTTP Transports (OAuth & PAT):
You can now run mcp-atlassian as a shared service where individual users authenticate their requests using their own OAuth 2.0 Bearer tokens (for Atlassian Cloud) or Personal Access Tokens (PATs for Server/Data Center). This means AI assistants can now operate with the specific permissions and context of the end-user, enhancing security and personalization. The server intelligently creates user-specific Jira and Confluence clients on-the-fly.
New confluence_add_comment Tool:
Programmatically add comments to Confluence pages! This new tool allows AI agents and users to engage more dynamically with Confluence content. (#424, Fixes #276)
Enhanced confluence_get_page Tool:
Finding Confluence pages is now more flexible. In addition to fetching by page_id, you can now retrieve pages using a combination of their title and space_key. This is particularly useful when the page ID isn't readily available. (#430)
fastmcp and mcp.cachetools for potential future token validation caching.confluence_add_comment tool to the tools table in the README. (#431)Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.10.6...v0.11.0
This release enhances the OAuth 2.0 authentication experience with improved detection logic and comprehensive documentation.
This release enhances the OAuth 2.0 authentication experience with improved detection logic and comprehensive documentation.
ATLASSIAN_OAUTH_CLOUD_ID) are present. This ensures OAuth takes precedence over other authentication methods when fully configured. (#410, #412)Comprehensive OAuth 2.0 Guide: Restored and significantly enhanced the OAuth setup documentation with:
--oauth-setup wizardoffline_access scope for refresh tokensDocker OAuth Support: Added Docker-specific instructions for OAuth configuration, including token persistence via volume mounting:
docker run --rm -i \
-p 8080:8080 \
-v "${HOME}/.mcp-atlassian:/home/app/.mcp-atlassian" \
ghcr.io/sooperset/mcp-atlassian:latest --oauth-setup -v
This ensures OAuth tokens stored in ~/.mcp-atlassian persist across container runs. (#413)
Configuration Clarity: Reorganized authentication methods in .env.example for better readability and understanding. (#414, #415)
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.10.5...v0.10.6
This release improves client compatibility and updates core dependencies for better stability with the latest FastMCP framework.
This release improves client compatibility and updates core dependencies for better stability with the latest FastMCP framework.
fastmcp dependency to 2.3.x series for latest improvements and stabilityFull Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.10.4...v0.10.5
This release enhances OAuth 2.0 stability, adds a Jira user profile tool, and improves Confluence tool compatibility.
This release enhances OAuth 2.0 stability, adds a Jira user profile tool, and improves Confluence tool compatibility.
jira_get_user_profile): New tool to retrieve Jira user details (name, email, avatar) using various identifiers (accountId, username, email). Enables better user-related automations. (#396)offline_access Scope): Added offline_access scope to OAuth configurations to enable refresh tokens and prevent authentication failures. Includes improved validation and UI in setup scripts. (#381)None is passed. Parameters now properly default to empty strings for better compatibility. (#389)jira_get_user_profile tool and clarified input format for assignee parameter in Jira issue tools. (#391, #395)Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.10.3...v0.10.4
This release introduces proxy support and addresses a critical compatibility issue encountered when running the server via uvx.
This release introduces proxy support and addresses a critical compatibility issue encountered when running the server via uvx.
HTTP_PROXY, HTTPS_PROXY, SOCKS_PROXY, NO_PROXY) or service-specific overrides (e.g., JIRA_HTTPS_PROXY, CONFLUENCE_NO_PROXY). Refer to the README and .env.example for detailed configuration instructions. (#260, #361)uvx Compatibility Fix: Resolved the "Context is not available outside of a request" error that occurred when running uvx mcp-atlassian@latest due to incompatibility with fastmcp>=2.2.8. Pinned the fastmcp dependency to <2.2.8 to ensure compatibility with the latest mcp-atlassian release when installed via uvx. (#383, #384)Note: This release pins the fastmcp version to address the immediate compatibility issue. Future releases will aim to update the code for compatibility with the latest fastmcp versions.
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.10.2...v0.10.3
SSE Docker Network Fix: Modified the SSE server to bind to "0.0.0.0" instead of the default localhost, allowing connections from any network interface
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.10.1...v0.10.2
Restore Health Check Endpoint: This release fixes a regression introduced in v0.10.0 where the /healthz endpoint (added to fix #359) was accidentally
/healthz endpoint (added to fix #359) was accidentally removed during the FastMCP v2 migration (#371). The /healthz endpoint is now correctly available again for Kubernetes health probes when using the SSE transport. (#375)Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.10.0...v0.10.1
This release introduces OAuth 2.0 support for Atlassian Cloud, migrates the server backend to FastMCP v2, and significantly improves Jira Cloud search
This release introduces OAuth 2.0 support for Atlassian Cloud, migrates the server backend to FastMCP v2, and significantly improves Jira Cloud search functionality.
uvx mcp-atlassian --oauth-setup). (#365, Fixes #238)total issue count in search results. (#360, Refs #333)/healthz endpoint for Kubernetes probes when using SSE transport. (#366, Fixes #359)jira_get_epic_issues and confluence_get_page_ancestors tools (use search tools instead). (#372)pyproject.toml. (#368)Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.9.0...v0.10.0
Support on-prem servers by @msabramo in https://github.com/sooperset/mcp-atlassian/pull/350
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.8.4...v0.9.0
fix: Added create_sprint by @qorpus in https://github.com/sooperset/mcp-atlassian/pull/235
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.8.3...v0.8.4
Remove Resources Functionality to Fix Excessive Startup Requests by @sooperset in https://github.com/sooperset/mcp-atlassian/pull/322
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.8.2...v0.8.3
Revert: Rollback FastMCP v2 refactoring to resolve v0.8.1 issues by @sooperset in https://github.com/sooperset/mcp-atlassian/pull/320
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.8.1...v0.8.2
Fix: Jira search pagination parameter mismatch (#308) by @sooperset in https://github.com/sooperset/mcp-atlassian/pull/309
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.8.0...v0.8.1
Add Docker Installation Support and Homebrew Option for macOS by @sooperset in https://github.com/sooperset/mcp-atlassian/pull/283
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.7.1...v0.8.0
Fix: Unwrap request to create issues by @lhays5 in https://github.com/sooperset/mcp-atlassian/pull/273
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.7.0...v0.7.1
Feature: Add jira_batch_create_issues tool by @lhays5 in https://github.com/sooperset/mcp-atlassian/pull/244
confluence_attach_content tool due to usability and technical limitations (#242) by @sooperset in https://github.com/sooperset/mcp-atlassian/pull/255Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.6.5...v0.7.0
Fix handling of fixVersions when provided in additional_fields (#241) by @sooperset in https://github.com/sooperset/mcp-atlassian/pull/247
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.6.4...v0.6.5
fix: windsurf parse error by @BEMELON in https://github.com/sooperset/mcp-atlassian/pull/228
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.6.3...v0.6.4
Fix Windsurf unable to parse input schema for jira_create_issue by @sooperset in https://github.com/sooperset/mcp-atlassian/pull/215
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.6.2...v0.6.3
Support Jira "Component/s" field when creating the tickets by @klacol in https://github.com/sooperset/mcp-atlassian/pull/207
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.6.1...v0.6.2
Add count metadata to Jira search results (#164) by @sooperset in https://github.com/sooperset/mcp-atlassian/pull/203
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.6.0...v0.6.1
Feat: Configure mcp-atlassian for Smithery Deployment and Installation by @sooperset in https://github.com/sooperset/mcp-atlassian/pull/194
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.5.0...v0.6.0
Parse fixVersions field properly under "fields" by @bstasz-graebert in https://github.com/sooperset/mcp-atlassian/pull/162
get tool for Jira agile sprint and board by @lanbaoshen in https://github.com/sooperset/mcp-atlassian/pull/166Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.4.0...v0.5.0
Add JiraBoards and get_all_agile_boards tool by @lanbaoshen in https://github.com/sooperset/mcp-atlassian/pull/158
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.3.1...v0.4.0
Fix SSLError when using no SSL verify option by @younho9 in https://github.com/sooperset/mcp-atlassian/pull/150
Full Changelog: https://github.com/sooperset/mcp-atlassian/compare/v0.3.0...v0.3.1
Your coding agent can read these notes before it upgrades. Set up the MCP server →