Provides tools to read SMS messages and retrieve OTP verification codes from Android devices via ADB, enabling automated web login flows that require SMS authentication.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@adb-sms wait for the OTP from the SMS I just triggered"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Read Android SMS verification codes via ADB, enabling Cursor Agent to complete Web SMS login together with chrome-devtools.
Design principle: Phone numbers are configured by the user in
devices.json; adb is only responsible for identifying the device serial + reading SMS OTP.
USB 连接手机（adb devices → serial）
│
├─ devices.json[serial].phone_numbers → Web 填手机号
│
└─ adb 读短信 inbox → adb_wait_for_otp 拿验证码Related MCP server: Android MCP Server
mcp-adb-sms/
├── server.py # MCP 服务入口
├── adb_client.py # ADB 设备 / 短信读取
├── sms_parser.py # 短信与 OTP 解析
├── test_local.py # 本地自检（不启动 MCP）
├── requirements.txt
├── devices.json.example # 手机号配置模板（提交到 git）
├── devices.json # 本地配置（git 忽略，需自行创建）
└── README.mdAndroid phone has USB debugging enabled and authorized on the computer
adb devices shows device (not unauthorized)
Python 3.10+ (3.12 recommended)
Android platform-tools (includes adb)
git clone https://github.com/zalazp/mcp-adb-sms.git
cd mcp-adb-sms
py -3.12 -m pip install -r requirements.txtPhone numbers are not read by adb; write them into devices.json yourself:
copy devices.json.example devices.jsonRun adb devices and note the serial (e.g. 10AD410LNF000PX)
Use the serial as the key and fill in all phone numbers for that device
{
"10AD410LNF000PX": {
"phone_numbers": [
"18317840243",
"19139582095"
]
}
}Edit %USERPROFILE%\.cursor\mcp.json:
{
"mcpServers": {
"adb-sms": {
"command": "py",
"args": [
"-3.12",
"E:\\path\\to\\mcp-adb-sms\\server.py"
],
"env": {
"ADB_PATH": "D:\\RJAZ\\Sdk\\platform-tools\\adb.exe"
}
}
}
}Field | Description |
Path in | Change to the absolute path of |
| Absolute path to local |
After saving, restart Cursor; adb-sms in the MCP panel should turn green.
cd mcp-adb-sms
$env:ADB_PATH="D:\RJAZ\Sdk\platform-tools\adb.exe"
py -3.12 test_local.pyExample of normal output:
{
"adb_exists": true,
"devices": [{ "serial": "10AD410LNF000PX", "state": "device" }],
"sms_readable": true,
"sim_numbers": [
{ "number": "13800138000", "available": true },
{ "number": "13900139000", "available": true }
],
"device_profile": { "source": "devices.json" }
}If recommendations indicates missing configuration, create devices.json as described above.
Tool | Description |
| Diagnose adb, SMS readability, and whether |
| List connected ADB devices |
| Read phone numbers for the current serial from |
| Read the most recent N SMS messages |
| After clicking send verification code on the Web, poll and wait for a new OTP |
| On Android 11+, attempt to grant shell permission to read SMS |
| Restricted adb shell (whitelisted commands) |
1. adb_health_check()
2. adb_get_sim_numbers() ← 从 devices.json 取手机号
3. chrome-devtools: 打开登录页、填号、勾选协议
4. chrome-devtools: 滑块验证码（失败则人工完成）
5. chrome-devtools: 点击「发送验证码」
6. adb_wait_for_otp(timeout=90, sender_filter="Midea|美的")
7. chrome-devtools: 填入验证码并登录adb shell appops set com.android.shell READ_SMS allowOr call adb_grant_sms_permission in the Agent, then run adb_health_check.
If it still fails, MCP will attempt to fall back to reading SMS from the notification bar via dumpsys notification (lower precision).
Only reads SMS from locally connected USB devices
Does not persist SMS content to disk
devices.json contains phone numbers and is in .gitignore; do not commit it to a public repository
adb_shell only allows whitelisted commands such as content / dumpsys / getprop
Restricted to your own devices or authorized test scenarios
MIT
This server cannot be deployed
SMS Verify: SMS Verify API is a secure and easy-to-integrate service that sends verification codes.
Disposable email inboxes for AI agents — read messages and verification codes.
Let agents send content-free push notifications to a paired phone via MCP.
Control real Android and iOS devices with LLM agents — tap, swipe, type, automate flows.
