Conversation
…patibility Document Android Studio Otter 2 Feature Drop MCP client bug that incorrectly serializes array parameters as strings. Includes affected version, root cause analysis, and references to issue #20. This clarifies that the issue is with Android Studio's MCP client implementation, not with super-shell-mcp server.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Changes
Related Issues
Context
A user reported an issue where Android Studio's MCP client incorrectly serializes array parameters as strings, causing
execute_commandcalls with arguments to fail. After investigation, this was confirmed to be a bug in Android Studio's MCP client implementation, not in super-shell-mcp.The server implements the MCP specification correctly and works as expected with Claude Desktop and other MCP clients.