DN

dondetir/neuralbridge_mcp

Developer tools
30ย stars 0 forks ํ’ˆ์งˆ 90 ํŠธ๋ Œ๋“œ 90

๐Ÿง  AI-native Android automation via MCP. Give Claude, GPT, Gemini or any AI agent full control over Android โ€” tap, swipe, type, screenshot โ€” with ~6ms latency. 100x faster than Appium. 43 tools.

๊ฐœ์š”

AI-native Android automation via the Model Context Protocol Give any AI agent โ€” Claude, GPT, Gemini, or your own โ€” full control over an Android device. Observe the UI. Tap. Swipe. Type. Manage apps. Capture screenshots. All with sub-100ms latency . No root required. Existing Android automation falls into two camps โ€” and both share the same bottleneck: 1. (Appium, Maestro) โ€” built for QA, not AI agents. Every action routes through ADB or UIAutomator IPC, costing 200-1000ms per operation. 2. (mobile-mcp, droidrun) โ€” AI-aware, but thin ADB wrappers underneath. 200-2000ms per action. NeuralBridge takes a different approach: an on-device AccessibilityService that executes actions , eliminating IPC overhead entirely. โ€” NeuralBridge averages per action vs for Appium and for mobile-mcp. See full benchmarks โ†’ Your AI agent speaks MCP over HTTP directly to the companion app โ€” no middleware, no ADB, no intermediate server.

README

๐Ÿง  NeuralBridge

AI-native Android automation via the Model Context Protocol

Give any AI agent โ€” Claude, GPT, Gemini, or your own โ€” full control over an Android device. Observe the UI. Tap. Swipe. Type. Manage apps. Capture screenshots. All with sub-100ms latency. No root required.

ย ย 

ย ย 


๐Ÿค” Why NeuralBridge?

Existing Android automation falls into two camps โ€” and both share the same bottleneck:

  1. Test frameworks (Appium, Maestro) โ€” built for QA, not AI agents. Every action routes through ADB or UIAutomator IPC, costing 200-1000ms per operation.
  2. MCP wrappers (mobile-mcp, droidrun) โ€” AI-aware, but thin ADB wrappers underneath. 200-2000ms per action.

NeuralBridge takes a different approach: an on-device AccessibilityService that executes actions in-process, eliminating IPC overhead entirely.

NeuralBridge Appium Maestro mobile-mcp droidrun ADB Shell
โšก Tap latency ~2ms 300-1000ms 750ms-2s 500-2000ms 200-1000ms 300-1000ms
โŒจ๏ธ Text input ~1.4ms 500-3000ms 750ms-2s 500-2000ms 200-1000ms 500-2000ms
๐ŸŒณ UI tree read 18-33ms 500-2000ms 750ms-2s 1-5s 200-500ms 1-5s
๐Ÿ“ธ Screenshot ~60ms 300-500ms ~1s 300-500ms ~250ms 300-500ms
๐Ÿ”Œ MCP native Yes Add-on Yes (stdio) Yes Via adapter No
๐Ÿ› ๏ธ MCP tools 43 30+ (add-on) 14+ ~19 ~11 โ€”
๐ŸŽฏ Token optimization Yes (73%) No No No No No

[!TIP] 100x faster on average โ€” NeuralBridge averages 6.4ms per action vs ~800ms for Appium and ~1.5s for mobile-mcp. See full benchmarks โ†’


๐Ÿ—๏ธ How It Works

Your AI agent speaks MCP over HTTP directly to the companion app โ€” no middleware, no ADB, no intermediate server.

[!NOTE] 1 hop, not 5. Appium routes through HTTP โ†’ Appium Server โ†’ ADB โ†’ UIAutomator2 โ†’ Device. NeuralBridge goes Agent โ†’ HTTP โ†’ Companion App. The AccessibilityService runs in-process โ€” like the difference between a phone call and a note on your own desk. Deep dive โ†’


๐Ÿš€ Quickstart

Prerequisites: Android SDK (API 24+), Java JDK 17, Android device or emulator (7.0+)

1๏ธโƒฃ Clone & Build

git clone https://github.com/dondetir/NeuralBridge_mcp.git
cd NeuralBridge_mcp/android
./gradlew assembleDebug

2๏ธโƒฃ Install & Enable

# Install the companion app
adb install -r app/build/outputs/apk/debug/app-debug.apk

# Enable AccessibilityService
adb shell settings put secure enabled_accessibility_services \
  com.neuralbridge.companion/.service.NeuralBridgeAccessibilityService
adb shell settings put secure accessibility_enabled 1

[!IMPORTANT] Android 15+ requires an extra step: Settings โ†’ Apps โ†’ NeuralBridge โ†’ Enable โ€œAllow restricted settingsโ€

3๏ธโƒฃ Connect Your AI Agent

The app shows its IP on the main screen. Add it to your agentโ€™s MCP config:

# Claude Code
claude mcp add neuralbridge http://:7474/mcp --transport http

4๏ธโƒฃ Verify

Ask your AI agent: โ€œTake a screenshot of the Android deviceโ€ โ€” if you see a screenshot, youโ€™re connected! ๐ŸŽ‰


๐Ÿ“š Documentation

Document Whatโ€™s inside
๐Ÿ—๏ธ Architecture Data flow, command paths, selector system, limitations
๐Ÿ› ๏ธ Tools Reference All 32 MCP tools with descriptions and latencies
โšก Performance Benchmarks, architecture comparison, token optimization
๐Ÿ”ง Troubleshooting Connection issues, permissions, screenshots, crashes
๐Ÿ”จ Development Building from source, project structure, protobuf, logs
๐Ÿ“ฑ Android App App-specific setup and permissions
๐Ÿค Contributing Code style, PR process, guidelines
๐Ÿ”’ Security Vulnerability reporting policy

๐Ÿ—บ๏ธ Roadmap

  • [x] Core MVP โ€” 16 tools, TCP protocol, basic gestures
  • [x] Advanced gestures, selectors, event streaming, notifications
  • [x] Semantic resolver, scroll-to-element, accessibility audit, screenshot diff
  • [ ] Multi-device, WebView tools, CI/CD integration, visual regression

๐Ÿค Contributing

See CONTRIBUTING.md for guidelines. High-priority areas: additional MCP tools, performance optimizations, cross-platform support (iOS), and example demos.


๐Ÿ“„ License

Apache 2.0 โ€” Copyright 2026 dondetir

โ€œPowered by NeuralBridgeโ€

View this README on GitHub

์„ค์น˜

This server does not publish a one-line install command.

Open the repository installation guide

์„ค์ •

{ "mcpServers": { "neuralbridge": { "type": "http", "url": "http://<device-ip>:7474/mcp" } } }