MCP error, literals invalid

[Manamama]

MCP ERROR (mcp-android-adb-server): [
  {
    "code": "invalid_union",
    "unionErrors": [
      {
        "issues": [
          {
            "code": "invalid_literal",
            "expected": "2.0",
            "path": [
              "jsonrpc"
            ],
            "message": "Invalid literal value, expected \"2.0\""
          },
          {
            "code": "unrecognized_keys",
            "keys": [
              "time",
              "level",
              "msg",
              "message"
            ],
            "path": [],
            "message": "Unrecognized key(s) in object: 'time', 'level', 'msg', 'message'"
          }
        ],
        "name": "ZodError"
      },
      {
        "issues": [
          {
            "code": "invalid_literal",
            "expected": "2.0",
            "path": [
              "jsonrpc"
            ],
            "message": "Invalid literal value, expected \"2.0\""
          },
          {
            "code": "unrecognized_keys",
            "keys": [
              "time",
              "level",
              "msg",
              "id",
              "message"
            ],
            "path": [],
            "message": "Unrecognized key(s) in object: 'time', 'level', 'msg', 'id', 'message'"
          }
        ],
        "name": "ZodError"
      },
      {

in Gemini CLI.

adb devices
List of devices attached
ZHE6ORBQ7TR8BQHM	device
192.168.222.109:5555	device
192.168.44.1:5555	device

and:

   "mcp-android-adb-server": {
      "command": "/home/user/.local/bin/mcp-android-adb-server",
      "env": {
        "DEVICE_ID": "localhost:5555",
        "SCREEN_LOCK_PASSWORD": "123456",
        "VISUAL_MODEL_ON": "true"
        //"VISUAL_MODEL_API_KEY": "sk-or-xxxxxxxxxxxxxxxxxxx",
        //"VISUAL_MODEL_BASE_URL": "https://openrouter.ai/api/v1/",
        //"VISUAL_MODEL_NAME": "qwen/qwen2.5-vl-72b-instruct:free"
      }
    }

It works otherwise:

adb -s 192.168.44.1:5555 shell whoami && ls
shell
device ...

etc.

[github-hewei]

Hi @Manamama,

Thank you very much for submitting such a detailed issue. The information and logs you provided were extremely helpful in diagnosing the
problem.

We have analyzed the issue and confirmed the root cause. You were correct; the problem was indeed in the server-side code.

Root Cause:
The core of the issue is that the program uses standard I/O (stdio) for its JSON-RPC communication. However, the logger was incorrectly
configured to write JSON-formatted logs to both a log file and to standard output (stdout).

This caused the client (Gemini CLI) to receive a mix of log data and the actual RPC response on the stdout stream. When the client
attempted to parse the log data, it failed because the format did not match the expected JSON-RPC protocol, leading to the invalid_literal
and unrecognized_keys errors you observed.

The Fix:
To resolve this, we have modified the logger configuration in main.go. The logger will now only write to the log file and will no longer
output anything to stdout. This ensures that the stdout stream remains "clean" and is used exclusively for JSON-RPC communication.

The fix has been committed. Please pull the latest code from the repository and re-compile the application. This should completely resolve
the issue you encountered.

If you have a moment, we would appreciate it if you could verify that the fix works on your end. We can close this issue upon your
confirmation.

Thanks again for your valuable contribution!

(Note: This response was generated with the assistance of Google's Gemini AI.)