8000 [Bug]: Connection Error in mcp-atlassian when Attempting to Access Jira Functions · Issue #383 · sooperset/mcp-atlassian · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Bug]: Connection Error in mcp-atlassian when Attempting to Access Jira Functions #383

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
2 tasks done
nicholastn1 opened this issue May 6, 2025 · 5 comments
Closed
2 tasks done

[Bug]: Connection Error in mcp-atlassian when Attempting to Access Jira Functions #383

nicholastn1 opened this issue May 6, 2025 · 5 comments
Labels
bug Something isn't working

Comments

@nicholastn1
Copy link

Prerequisites

  • I have searched the existing issues to make sure this bug has not already been reported.
  • I have checked the README for relevant information.

Bug Description

The mcp-atlassian service is returning "Context is not available outside of a request" error when trying to access Jira functionality. This prevents issues from being properly queried through the interface.

Steps to Reproduce

  1. Attempt to access any Jira function through the mcp-atlassian API
  2. Execute a query to list open issues using the jira_search command
  3. Observe the returned error "Error executing tool search: Context is not available outside of a request"

Expected Behavior

The system should return the list of open Jira issues as requested by the query, displaying details such as title, status, priority, and assignee.

Actual Behavior

The system returns the error "Context is not available outside of a request" and cannot access any Jira information. It's impossible to view issues or interact with Jira functionalities.

mcp-atlassian Version

0.10.2

Installation Method

From PyPI (pip install mcp-atlassian / uv add mcp-atlassian)

Operating System

macOS

Python Version

3.13.3

Atlassian Instance Type

Jira Cloud

Client Application

Claude Desktop

Additional Context

This error appears to indicate a context initialization problem in the mcp-atlassian service. It's possibly related to an authentication failure or initial configuration issue that prevents establishing the necessary context for API calls.
@nicholastn1 nicholastn1 added the bug Something isn't working label May 6, 2025
@jstewmon
Copy link
jstewmon commented May 6, 2025

Seems possibly related to the auth changes in mcp 1.7.0 or 1.7.1. I updated my config to use the docker image (deps are baked at build time), and the issue resolved.

@KozielGPC
Copy link

I'm facing the same problem. Cannot pull informations from a jira ticket

Image

@sooperset
Copy link
Owner

Thanks for reporting this issue, @nicholastn1, and for the confirmations from @jstewmon and @KozielGPC.

I've reproduced the "Context is not available outside of a request" error when using uvx mcp-atlassian@latest. As @jstewmon mentioned, this is likely related to recent auth changes in mcp 1.7.x.

Workaround: Use either:

  • Docker image: ghcr.io/sooperset/mcp-atlassian:latest (recommended)
  • Local installation: uv add mcp-atlassian && uv sync --frozen

I'll investigate the dependency conflict with uvx installation and work on a patch release (0.10.3).

@KozielGPC
Copy link

Sure, thank you! Waiting for updates.

@sooperset
Copy link
Owner

Fixed in v0.10.3! The issue was an incompatibility with fastmcp>=2.2.8 causing the context error when installed via uvx. I've pinned fastmcp<2.2.8 as an immediate fix (#384).

You can now use uvx mcp-atlassian@0.10.3 without issues. I've tested this with uvx, local installation, and Docker.

We'll update for full compatibility with newer fastmcp versions in a future release.

Thanks for the report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jstewmon @sooperset @KozielGPC @nicholastn1
0