8000 Error spawnSync adb ENOENT in the Claude Desktop · Issue #66 · mobile-next/mobile-mcp · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Error spawnSync adb ENOENT in the Claude Desktop #66

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
MrRahulR opened this issue May 18, 2025 · 2 comments
Closed

Error spawnSync adb ENOENT in the Claude Desktop #66

MrRahulR opened this issue May 18, 2025 · 2 comments
Assignees
@gmegidish

Comments

@MrRahulR
Copy link

Describe the bug
The Mobile MCP server fails to detect ADB on Claude Desktop despite proper PATH configuration. While GitHub Copilot successfully executes ADB commands against the same environment setup, Claude Desktop consistently returns "ADB not found" errors. I've verified the platform-tools directory is correctly added to both the system PATH and explicitly configured in the filesystem MCP.

Configuration (please complete the following information):

  • Agent: Claude Desktop 3.7 Sonnet
  • OS: macOS Sequoia 15.4.1
  • Device: Android Emulator
  • Android Version: Android v14 (API 34)

To Reproduce
Steps to reproduce the behavior:

  • Install and configure Mobile MCP server on macOS
  • Verify Android emulator is running (adb devices shows device in terminal)
  • Connect Claude Desktop to the MCP server
  • Request Claude to list connected devices
  • Observe the error response from mobile_list_available_devices command

Expected behavior
Claude Desktop should successfully detect and list available Android devices through the Mobile MCP server, identical to the functionality working correctly in GitHub Copilot.

Screenshots

Image
Image
@gmegidish
Copy link
Contributor

Hey @MrRahulR . Thanks for this issue. Claude Desktop is executed in a new environment, that might not inherit from your bashrc. As opposed to command line tools.

Two things here:

  1. I need to debug why you got ENOENT, it should have told you that you dont have platform-tools installed.
  2. You can configure ANDROID_HOME under your mcpServers configuration in Claude Desktop, add "env" and provide ANDROID_HOME there. See here: https://forum.cursor.com/t/how-to-config-mcp-server-with-an-env-parameter-in-cursor/49069

I'll add it to the documentation. Please reply if this solved your issue. I will close the issue when it's working for you. 🙏

@gmegidish gmegidish self-assigned this May 18, 2025
@MrRahulR
Copy link
Author

Hi @gmegidish,

Thank you so much for your help, it worked! I'm now able to execute the commands on Claude as well.
Since the issue is resolved, I’ll go ahead and close the PR.

Thanks again! 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gmegidish gmegidish

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gmegidish @MrRahulR
0