LuckyStar MCP Server
MCP server that lets AI agents drive the LuckyStar/LS_KTool Android memory-debugging stack, exposing tools for memory read/write, scanning, pointer operations, and device/process management via the Model Context Protocol.
README
lucky-star-mcp
AI-agent plugins for the LuckyStar / LS_KTool Android memory-debugging stack (from lsnbm/Linux-android-arm64).
This repository packages the agent-facing components so any MCP-capable client (Claude Code, Claude Desktop, Cursor, etc.) can drive the Android debugger through the standard Model Context Protocol (MCP).
⚠️ Research/learning use only. The upstream driver provides kernel memory read/write, module scanning, hardware breakpoints, and input simulation. Use it only on devices and processes you own or are authorized to test.
What's inside
lucky-star-mcp/
├── python/
│ ├── LuckyStarMcp.py # FastMCP server → exposes the Android bridge as MCP tools
│ ├── http_bridge.py # NativeHttpBridge → talks to the Android HTTP server (port 9494)
│ └── examples/
│ └── mcp-config.example.json # sample MCP client registration
├── go-client/ # Go desktop client (Fyne UI) with a bundled MCP server (internal/mcp)
├── requirements.txt # Python deps (mcp, pydantic)
└── LICENSE # MIT
Python MCP server (python/)
LuckyStarMcp.py is a self-contained FastMCP server. It exposes the Android
debugger's full toolset as MCP tools:
- Connection:
android_connection,discover_android_bridges,android_bridge_ping - Target:
android_target_set_pid,android_target_attach_package,android_target_find_pid,android_target_current - Environment:
android_env_get_params - Memory:
android_memory_regions,android_memory_read,android_memory_write,android_memory_dump - Scanning:
android_memory_scan_start,android_memory_scan_refine,android_memory_scan_results,android_memory_scan_status,android_memory_scan_clear - Pointers:
android_pointer_status,android_pointer_scan,android_pointer_merge,android_saved_* - Modules/breakpoints:
android_module_address, breakpoint helpers
Go client (go-client/)
A desktop GUI client (Fyne) for the same bridge, with its own MCP server in
internal/mcp (uses mark3labs/mcp-go). Build with build.ps1 / go build.
Prerequisites
- Android device running
LS_KToolin HTTP-server mode (port9494), reachable over the LAN (or via a Cloudflare tunnel URL). - Python 3.12+ for the Python MCP server.
The MCP server starts even when the device is offline — each tool call will then return a bridge-connection error instead.
One-shot install for local agents
./install.sh sets up a Python venv, registers the MCP server with your local
agents (Claude Code, Claude Desktop, Cursor), and starts it:
./install.sh # venv + deps + register agents + start server
./install.sh status # check server / adb forward state
./install.sh stop # stop the server
It also runs adb forward tcp:9494 tcp:9494 so the server reaches the device
through the adb connection (--android-host 127.0.0.1).
Install & run (Python)
pip install -r requirements.txt
# Start the MCP server (default: http://127.0.0.1:14447/mcp)
python python/LuckyStarMcp.py
# Point it at a specific device on your LAN:
python python/LuckyStarMcp.py --android-host 192.168.1.50 --android-timeout 4
# Use a Cloudflare tunnel URL instead of a raw IP:
python python/LuckyStarMcp.py --android-host "https://your-tunnel.trycloudflare.com"
| Flag | Default | Description |
|---|---|---|
--mcp-host |
127.0.0.1 |
Bind host for the local MCP web server |
--mcp-port |
14447 |
Bind port for the local MCP web server |
--mcp-path |
/mcp |
HTTP endpoint path for streamable-http clients |
--android-host |
auto |
Android IP/host, full HTTP(S) tunnel URL, or auto for LAN discovery |
--android-timeout |
4 |
Timeout (seconds) for Android bridge requests |
Environment variables: ANDROID_HTTP_HOST (default auto), ANDROID_HTTP_PORT
(9494), ANDROID_HTTP_TIMEOUT (4), ANDROID_MCP_BIND_HOST (127.0.0.1),
ANDROID_MCP_BIND_PORT (14447), ANDROID_MCP_PATH (/mcp).
Register with an MCP client
With the server running, register it in your client's MCP config. Example (Claude Code / Claude Desktop style):
{
"mcpServers": {
"luckystar": {
"type": "http",
"url": "http://127.0.0.1:14447/mcp",
"enabled": true
}
}
}
Or, to have the client launch the server itself (stdio mode):
{
"mcpServers": {
"luckystar": {
"command": "python",
"args": ["/path/to/lucky-star-mcp/python/LuckyStarMcp.py"]
}
}
}
License
MIT. The LuckyStarMcp.py, http_bridge.py, and go-client/ sources are
derived from lsnbm/Linux-android-arm64
(© 2025 LsLucky). See LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。