Server facts
phonepi-mcp
Project
- Author
- priyankark
- Repository
- github.com/priyankark/phonepi-mcp
- Website
- www.phonepimcp.com/
- License
- MIT
- Category
- Mobile & Desktop Automation
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 38
- Last commit
- Data as of
Tags
- Claude
- Cursor
- ai
- ai smartphone
- mcp
- mcp client
- mcp phone control
- mcp server
- mobile mcp
- modelcontextprotocol
- phone link
- phone mcp
- phone p2p
- phone pc link
- phonepi mcp
- remote access tool
- remote control
Overview
Contacts, saved snippets, and phone communication are central to PhonePi MCP’s desktop-to-mobile workflow. Through MCP-compatible assistants such as Cursor and Claude Desktop, users can retrieve, create, edit, or delete contacts and snippets. Snippet tools also support searching, filtering by type, fetching an individual entry, and sharing through messaging apps. Calling and SMS preparation sit alongside these tools, but SMS has an important interaction boundary: current store versions launch the phone’s composer, leaving final sending confirmation to the user. The phone app needs to remain open for that SMS workflow.
Other actions cover copying text into the phone’s clipboard, checking its battery level, setting a timer, and triggering a beep to locate the device. Assistants can also deliver notifications or request user attention through a message, then retrieve the response. The project pairs an open-source MCP server with a companion app, linking them across a local network without third-party servers handling that connection. Users control local server hosting and choose app permissions according to the features they use. The documentation recommends secure networks and suggests Tailscale for a private VPN connection.
phonepi-mcp setup notes
- phonepi-mcp records stdio only; confirm a network transport upstream before planning remote access.