Skip to content

Reauthentication with Jira MCP via Oauth doesn't work #5953

Closed

Description

@klaudworks

Description

I have to logout and log in again instead of reauthenticating with the Jira mcp server. Reauthentication using the following command does not work.

$ opencode mcp auth jira

┌  MCP OAuth Authentication
│
◇  jira already has stored credentials. Re-authenticate?
│  Yes
│
■  Authentication failed
│
■  Error POSTing to endpoint (HTTP 404): Missing sessionId parameter
│
└  Done

OpenCode version

1.0.184

Steps to reproduce

Configure jira mcp:

  "mcp": {
    "jira": {
      "type": "remote",
      "url": "https://mcp.atlassian.com/v1/sse",
      "enabled": true,
      "oauth": {}
    }
  },
  1. Run opencode mcp auth jira to authenticate first time -> works
  2. Run opencode mcp auth jira to reauthenticate -> fails

Screenshot and/or share link

No response

Operating System

macOS 26.0.1

Terminal

iTerm2

Activity

  1. github-actions commented on Dec 22, 2025

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    Feel free to ignore if none of these address your specific case.

  2. lideen commented on Feb 6, 2026

    @lideen
    opencode mcp logout jira
    opencode mcp auth jira

    For anyone coming here for a quick-fix

  3. ollietreend commented on Mar 23, 2026

    @ollietreend
    opencode mcp logout jira
    opencode mcp auth jira
    

    For anyone coming here for a quick-fix

    This worked for me last week. But today it doesn't 🫠

    Note

    I'm experiencing this issue with a different MCP server, not Jira. It's an internal MCP with oAuth authentication – the behaviour is exactly the same.

  4. removed
    bugSomething isn't working
    on May 3, 2026
  5. ImDevinC commented on May 15, 2026

    @ImDevinC

    The aboev workaround also does not work for me. I can find no way to reauthenticate my MCP servers at this time.
    Looking at the code, it does look like when mcp.browser.open.failed happens, the user should be prompted to manually ope nthe URL but that does not happen for me, the terminal just says "Authentication successful" even though it wasn't

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions