Skip to content

Kubernetes MCP server tools fail with TypeError: output.output.toLowerCase #12987

Closed

Description

@kamafozilov

Description

All tools from kubernetes-mcp-server (v0.0.57 by containers/kubernetes-mcp-server) fail with:

TypeError: undefined is not an object (evaluating 'output.output.toLowerCase')

The MCP server itself works correctly — tested directly via JSON-RPC over stdio, it returns valid MCP responses. The issue is in OpenCode's MCP client response parsing.

Direct JSON-RPC test (works):

{"jsonrpc":"2.0","id":1,"result":{"content":[{"type":"text","text":"APIVERSION   KIND   NAME..."}]}}

Same call through OpenCode → TypeError

Every tool fails identically: namespaces_list, pods_list, configuration_view, events_list, helm_list, etc.

Plugins

[email protected] (containers/kubernetes-mcp-server)

OpenCode version

1.1.53

Steps to reproduce

  1. Configure .mcp.json with kubernetes-mcp-server:
{
  "mcpServers": {
    "kubernetes": {
      "command": "npx",
      "args": ["-y", "kubernetes-mcp-server@latest"],
      "env": {
        "KUBECONFIG": "./kubeconfig/my-cluster.yaml"
      }
    }
  }
}
  1. Open OpenCode and invoke any kubernetes MCP tool (e.g. namespaces_list, pods_list)
  2. All calls fail with: TypeError: undefined is not an object (evaluating 'output.output.toLowerCase')

Operating System

macOS 26.3 (Apple Silicon / arm64)

Terminal

Warp, Ghostty

Activity

  1. scw1109 commented on Feb 10, 2026

    @scw1109

    Seeing same for using playwright-mcp and mcp with google toolbox.
    However, my error only being seen via OpenCode ACP, does not seeing it if using TUI.

  2. Nenormalniy commented on Feb 10, 2026

    @Nenormalniy

    Same bug on Windows 11 with my custom mcp server.
    Also, do you use OMO plugin?
    Is the problem related with this release?: https://github.com/code-yeongyu/oh-my-opencode/releases/tag/v3.5.0
    code-yeongyu/oh-my-openagent#1720

    rollback to [email protected] fixed this issue for me

  3. kamafozilov commented on Feb 10, 2026

    @kamafozilov
    Author

    Same bug on Windows 11 with my custom mcp server. Also, do you use OMO plugin? Is the problem related with this release?: https://github.com/code-yeongyu/oh-my-opencode/releases/tag/v3.5.0 code-yeongyu/oh-my-opencode#1720

    rollback to [email protected] fixed this issue for me

    yeah, I use OMO too, but I haven’t had any issues with OMO on my side

  4. blackbxdev commented on Feb 10, 2026

    @blackbxdev

    Same bug on Windows 11 with my custom mcp server. Also, do you use OMO plugin? Is the problem related with this release?: https://github.com/code-yeongyu/oh-my-opencode/releases/tag/v3.5.0 code-yeongyu/oh-my-opencode#1720

    rollback to [email protected] fixed this issue for me

    Pinning OMO solved my issue as well. Thank you for this!

  5. roshitx commented on Feb 11, 2026

    @roshitx

    Confirmed - Affects ALL MCP Servers

    I can confirm this bug affects all MCP integrations, not just Kubernetes MCP:

    • ✅ Laravel Boost MCP - All tools fail
    • ✅ Exa MCP - All tools fail
    • ✅ Context7 MCP - All tools fail
    • ✅ grep.app MCP - All tools fail
    • ✅ Kubernetes MCP - As reported

    Root Cause: Client-side parser expects response.output.output but MCP servers return response.output

    Workaround for Laravel Boost users:

    # Direct tool execution bypasses the bug
    php artisan boost:execute-tool 'Laravel\\Boost\\Mcp\\Tools\\SearchDocs' 'base64_params'

    Additional Details: #13091

  6. ouchxp commented on Feb 11, 2026

    @ouchxp

    Temporary fix -> add it to oh-my-opencode.jsonc

    "disabled_hooks": ["comment-checker"], // Temporarily added to address bug in 3.5.1 (MCP)

    code-yeongyu/oh-my-openagent#1737 (comment)

  7. github-actions commented on Apr 13, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.

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