Skip to content

MCP servers showing as disabled #8990

Closed

Description

@joseph-stano

Description

Seeing previously-working MCP servers showing as disabled, despite "enabled": true being set in opencode.jsonc.

Seems to have been introduced by a change in version 1.1.24 - the MCP servers work correctly in 1.1.23 and below.

I don't see any recent logs in ~/.local/share/opencode/log.

Plugins

Only one custom plugin for analytics.

OpenCode version

1.1.24+

Steps to reproduce

sample of my opencode.jsonc (servers obfuscated with ...)

"mcp": {
  "github-mcp": {
    "type": "local",
    "command": [
      "docker",
      "run",
      "-i",
      "--rm",
      "-e",
      "GITHUB_HOST=...",
      "-e",
      "GITHUB_API_URL=...",
      "-e",
      "GITHUB_PERSONAL_ACCESS_TOKEN",
      "ghcr.io/github/github-mcp-server"
    ],
    "enabled": true,
    "environment": {
      "GITHUB_PERSONAL_ACCESS_TOKEN": "{env:GITHUB_PAT}"
    }
  },
  "gyde-mcp": {
    "type": "remote",
    "url": "https://.../api/mcp/",
    "timeout": 60000,
    "enabled": true
  },
  "codex-mcp": {
    "type": "remote",
    "url": "https://.../mcp/",
    "timeout": 60000,
    "enabled": true
  },
  "jira-mcp": {
    "type": "remote",
    "url": "https://.../mcp/",
    "timeout": 60000,
    "enabled": true,
    "headers": {
      "Authorization": "Token {env:JIRA_PAT}"
    }
  }
}

Screenshot and/or share link

Image

Operating System

macOS 15.7.2

Terminal

Ghostty

Activity

  1. github-actions commented on Jan 16, 2026

    @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. owenconti commented on Jan 17, 2026

    @owenconti

    Seeing this on ubuntu 25 with github MCP. opencode v1.1.25

  3. zer0Black commented on Jan 17, 2026

    @zer0Black

    Yes, I encountered the same issue. All MCPs with type "remote" are disabled by default and cannot be opened

  4. johnsonsleo commented on Jan 17, 2026

    @johnsonsleo

    same issue here with v1.1.25

  5. super-unique-ai commented on Jan 17, 2026

    @super-unique-ai

    hardcoded?

  6. rekram1-node commented on Jan 17, 2026

    @rekram1-node
    Contributor

    Hmm

  7. Aaalice233 commented on Jan 17, 2026

    @Aaalice233

    same here

  8. rekram1-node commented on Jan 17, 2026

    @rekram1-node
    Contributor

    It looks like this was this issue:
    40b275d

    Sorry guys, shouldn't have merged that.

    Strangely I cannot replicate this issue tho

  9. rekram1-node commented on Jan 17, 2026

    @rekram1-node
    Contributor

    If you put this in ur config it might fix it:

    "oauth": false  // <-- Add this
    

    For the mcps failing to start

  10. Aaalice233 commented on Jan 17, 2026

    @Aaalice233

    If you put this in ur config it might fix it:

    "oauth": false  // <-- Add this
    

    For the mcps failing to start

    Is it supposed to be added to opencode.json? After adding it, launching opencode will prompt the following error:
    Error: Configuration is invalid at C:\Users\Administrator\.config\opencode\opencode.json ↳ Unrecognized key: "oauth"

  11. super-unique-ai commented on Jan 17, 2026

    @super-unique-ai

    If you put this in ur config it might fix it:

    "oauth": false  // <-- Add this
    

    For the mcps failing to start

    Is it supposed to be added to opencode.json? After adding it, launching opencode will prompt the following error: Error: Configuration is invalid at C:\Users\Administrator\.config\opencode\opencode.json ↳ Unrecognized key: "oauth"

    Should of installed it on Rocky Linux... https://rockylinux.org/

  12. rekram1-node commented on Jan 17, 2026

    @rekram1-node
    Contributor

    No I meant doing it per mcp server like this:

      "jira-mcp": {
        "type": "remote",
        "url": "https://.../mcp/",
        "timeout": 60000,
        "enabled": true,
        "headers": {
          "Authorization": "Token {env:JIRA_PAT}"
        },
        "oauth": false
      }
    
  13. rekram1-node commented on Jan 17, 2026

    @rekram1-node
    Contributor

    I have reverted bad commit (or the only suspect commit I should say): 33290c5

  14. shawnmcrowley commented on Jan 17, 2026

    @shawnmcrowley

    The "oauth": false took care of n8n mcp servers in 1.1.25 all are enabled now.

  15. juneleung commented on Jan 19, 2026

    @juneleung

    still happened in Arch Linux and needs the "oauth" fix in the config JSON.

  16. joseph-stano commented on Jan 19, 2026

    @joseph-stano
    Author

    setting "oauth": false did the trick for now 👍

  17. fengwk commented on Jan 20, 2026

    @fengwk

    Fixed in 1.1.26

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions