Turn your Android phone into an MCP (Model Context Protocol) server. AI agents and desktop scripts can call your phone for live data and actions over
Most team communication work still happens through a UI a human drives. Pocketmcp MCP server moves it into the conversation instead. Turn your Android phone into an MCP (Model Context Protocol) server. AI agents and desktop scripts can call your phone for live data and actions over LAN or Tailscale.
The server publishes 14 tools. What each one is for:
device_info — Battery, model, OS, network, memoryget_location — Best recent location from device providerssearch_contacts — Search contacts by namemake_call — Make phone calls to any numbersend_message — Send messages via WhatsApp, Instagram, Messenger, Google Messagessend_whatsapp_business_message — Dedicated WhatsApp Business contact-safe senderwhatsapp_automation — Advanced WhatsApp automation with accessibility controlsocial_media — Instagram, YouTube, X/Twitter interactionsapp_actions — JSON-preset actions for simpler app automation callsnotifications — Real-time notification monitoring and managementshell — Run shell commands with safety filters and timeoutflashlight — Turn flashlight on/off/toggle and read stateThe server ships on npm as node, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Configuration is passed through the environment: POCKET_MCP_URL, POCKET_MCP_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pocketmcp's toolset — device_info, get_location, search_contacts and 11 more — is a fair guide to whether it matches your workflow. It is maintained by axonixtools; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| device_info | Battery, model, OS, network, memory |
| get_location | Best recent location from device providers |
| search_contacts | Search contacts by name |
| make_call | Make phone calls to any number |
| send_message | Send messages via WhatsApp, Instagram, Messenger, Google Messages |
| send_whatsapp_business_message | Dedicated WhatsApp Business contact-safe sender |
| whatsapp_automation | Advanced WhatsApp automation with accessibility control |
| social_media | Instagram, YouTube, X/Twitter interactions |
| app_actions | JSON-preset actions for simpler app automation calls |
| notifications | Real-time notification monitoring and management |
| shell | Run shell commands with safety filters and timeout |
| flashlight | Turn flashlight on/off/toggle and read state |
| launch_app | Open an installed app by package or app name |
| list_apps | List launchable installed apps (309+ apps detected) |
{
"mcpServers": {
"phone": {
"type": "streamableHttp",
"url": "http://192.168.1.100:8080/mcp",
"headers": {
"X-API-Key": "your-api-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| POCKET_MCP_URL | Endpoint or connection string the server talks to. | Yes |
| POCKET_MCP_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.