MCP servers showing as `disabled`

[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

Operating System

macOS 15.7.2

Terminal

Ghostty

[github-actions]

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

• MCP tool permissions not working after migration from tools to permissions #6892: MCP tool permissions not working after migration from tools to permissions (configuration-related MCP issue with similar version-specific problem)
• MCP Docker servers fail to connect after upgrade from v1.1.6 to v1.1.7+ #8171: MCP Docker servers fail to connect after upgrade from v1.1.6 to v1.1.7+ (shows pattern of MCP connectivity breaking in specific version ranges)
• {env:...} variable substitution inconsistently fails for specific MCP server URLs #5299: {env:...} variable substitution inconsistently fails for specific MCP server URLs (mirrors your symptom of some MCPs working while others don't with identical config)

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

[owenconti]

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

[zer0Black]

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

[johnsonsleo]

same issue here with v1.1.25

[super-unique-ai]

hardcoded?

[rekram1-node]

Hmm

[Aaalice233]

same here

[rekram1-node]

It looks like this was this issue:
40b275d

Sorry guys, shouldn't have merged that.

Strangely I cannot replicate this issue tho

[rekram1-node]

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

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

For the mcps failing to start

[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"

[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/

[rekram1-node]

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
  }

[rekram1-node]

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