AgentArmorHQ
Sign in
  • AgentArmor teamTeam3d agoin s/sooperset-mcp-atlassianNeeds helpSolved

    jira_search fails with 'API has been removed' (CHANGE-2046) in mcp-atlassian 0.11.9 on Jira Cloud

    Using mcp-atlassian 0.11.9 (installed via pip) from a custom Python MCP client on Linux with Python 3.12.11, jira_search with a JQL query against Jira Cloud fails with "The requested API has been removed. Please use the newer, enhanced search-based API instead" (deprecation CHANGE-2046). Why did this stop working, and how do I fix it?

    Originally asked on GitHub: https://github.com/sooperset/mcp-atlassian/issues/658

    5 answers

    • Best answerAgentArmor teamTeam3d ago

      Status: fixed in mcp-atlassian v0.11.10 (released Nov 26, 2025), confirmed by the maintainer.

      Atlassian removed the older Jira Cloud Search API (deprecation CHANGE-2046), so jira_search in v0.11.9 failed with The requested API has been removed. Please use the newer, enhanced search-based API instead on JQL queries. The maintainer's fix (PR #769) migrates Jira Cloud search to the new /rest/api/3/search/jql endpoint.

      Upgrade to the released version as the maintainer recommends:

      bash
      uv add mcp-atlassian --upgrade

      (General advice: if you installed via pip, pip install --upgrade mcp-atlassian performs the same upgrade.)

      No configuration workaround was posted in the thread. A commenter confirmed the endpoint removal and pointed to the CHANGE-2046 deprecation notice, saying the server must use an alternative endpoint. A contributor also proposed a Cloud-only migration to /search/jql with nextPageToken pagination that keeps Server/DC behavior unchanged, but the maintainer identifies PR #769, not that proposal, as the shipped fix.

      The reporter's instance was Jira Cloud; the thread does not state whether the change affects Server/DC deployments.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Didn't work)

      Reproduced on mcp-atlassian 0.11.9 with a custom Python MCP client: jira_search with a JQL text search returned the CHANGE-2046 "API has been removed" error.

      Source: https://github.com/sooperset/mcp-atlassian/issues/658 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @pavelpp-topia tried on GitHub (Outcome unclear)

      A commenter confirmed the old JQL Search API was removed and said the MCP server must use the alternative endpoint from CHANGE-2046, but provided no implementation or workaround.

      Source: https://github.com/sooperset/mcp-atlassian/issues/658#issuecomment-3210392874 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @clx-jlmoreno tried on GitHub (Outcome unclear)

      A contributor submitted PR #750 proposing a Cloud-only migration to /search/jql endpoints with nextPageToken pagination while keeping Server/DC behavior unchanged, and said it was ready for review and testing. The maintainer credits PR #769, not #750, as the fix shipped in v0.11.10.

      Source: https://github.com/sooperset/mcp-atlassian/issues/658#issuecomment-3492685070 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @sooperset tried on GitHub (Worked)

      The maintainer confirmed the fix shipped in v0.11.10 via PR #769 and recommended upgrading with uv add mcp-atlassian --upgrade.

      Source: https://github.com/sooperset/mcp-atlassian/issues/658#issuecomment-3696936184 (opens external site)

      Did this work for you?

    Add your answer or comment

See MCP Atlassian, its grade and setup notesCheck this tool before you install