Support Android Studio Otter 2 Feature Drop

[JimmyYanDev]

Desc:
When calling tools that expect a json object for an argument (e.g., the args in execute_command), the Python list is incorrectly serialized as a single string instead of a JSON array. This causes "Invalid argument" errors, specifically "Expected array, received string".

Scene 1：

Failed calling tool: execute_command

Tool call
execute_command(
  command = "git",
  args = ["add", "."]
)

Response
Error: Error: [
  {
    "code": "invalid_type",
    "expected": "array",
    "received": "string",
    "path": [
      "args"
    ],
    "message": "Expected array, received string"
  }
]

Scene 2：

Failed calling tool: execute_command

Tool call
execute_command(
  command = "git add ."
)

Response
Error: Command execution failed: Command execution failed: spawn git add . ENOENT

Android Studio version：
Android Studio Otter 2 Feature Drop | 2025.2.2 Canary 3
Build #AI-252.25557.131.2522.14357309, built on October 30, 2025
Runtime version: 21.0.8+-14196175-b1038.72 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.awt.X11.XToolkit
Linux 5.4.0-218-generic
Ubuntu 20.04.6 LTS; glibc: 2.31
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 6144M
Cores: 16
Registry:
ide.experimental.ui=true
gradle.phased.sync.enabled=true
com.android.studio.ml.activeModel=com.android.studio.ml.AidaModel
Non-Bundled Plugins:
com.pingfangx.plugin.legacylayoutinspector (1.2.0)
cn.yiiguxing.plugin.translate (3.8.0)
Current Desktop: ubuntu:GNOME

Related Links
https://developer.android.com/studio/gemini/add-mcp-server

[cfdude]

@JimmyYanDev : I've reviewed the GitHub issue and the super-shell-mcp codebase. Here's my assessment:

✅ Verdict: The error report is VALID, but the bug is NOT in super-shell-mcp

The issue is in Android Studio Otter 2 Feature Drop's MCP client implementation, not in your server code.

Evidence:

1. Server Implementation is Correct (src/index.ts:152-168)

• The execute_command tool schema correctly defines args as type array:
  args: {
  type: 'array',
  items: { type: 'string' },
  description: 'Command arguments',
  }

• Zod validation correctly expects an array (src/index.ts:338):
  const schema = z.object({
  command: z.string(),
  args: z.array(z.string()).optional(),
  });

2. Working Example Confirms Correct Behavior (examples/client-example.js:38-41)
   const lsResult = await client.callTool('execute_command', {
   command: 'ls',
   args: ['-la'], // ✅ Array works correctly with official MCP SDK
   });

3. Root Cause
   The Zod error "Expected array, received string" means Android Studio is serializing the JavaScript/Python array ["add", "."] as a string (probably '["add", "."]') instead of a proper JSON array
   before sending it to your MCP server.

Scene Analysis:

• Scene 1: Android Studio sends args as string → Zod rejects it ✅ (correct behavior)
• Scene 2: User tries workaround command: "git add ." → Fails with spawn error because Node tries to execute a binary literally named "git add ." (with spaces in the name)

I would suggest reporting the bug to Android Studio Team

File a bug report with:

• Android Studio version: 2025.2.2 Canary 3
• Issue: MCP client incorrectly serializes array parameters as strings
• Reference: MCP specification requires proper JSON serialization
• Working example: Claude Desktop, official MCP SDK client (your examples/client-example.js)

[JimmyYanDev]

Thank you for your analysis！

[cfdude]

my pleasure!