phonelink-mcp-server
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., "@phonelink-mcp-server Show me my recent text messages."
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.
phonelink-mcp-server
MCP server that reads and interacts with the Phone Link (MyPhone) Windows app via UI Automation.
Since Microsoft doesn't offer public APIs for Phone Link, this server scrapes the UI using PowerShell + .NET's System.Windows.Automation.
Features
Tool | Type | Description |
| Read | Connection status + phone info |
| Read | List conversations or read a specific chat |
| Read | Call history (incoming/outgoing/missed) |
| Read | Phone notifications |
| Read | Photo gallery metadata |
| Read | Debug: dump full UI automation tree |
| Write | Send an SMS via the Phone Link UI |
| Write | Initiate a phone call |
| Write | Launch Phone Link if not running |
Related MCP server: umbriel
Requirements
Windows 10/11 with Phone Link installed and configured
Node.js >= 18
PowerShell (Windows PowerShell 5.1+ or PowerShell Core 7+)
Phone connected and paired in Phone Link
Setup
cd phonelink-mcp-server
npm install
npm run buildClaude Desktop Configuration
Add to your claude_desktop_config.json:
{
"mcpServers": {
"phonelink": {
"command": "node",
"args": ["C:/path/to/phonelink-mcp-server/dist/index.js"],
"env": {
"PHONELINK_PS_EXECUTABLE": "powershell.exe"
}
}
}
}Note: Use
pwsh.exeinstead ofpowershell.exeif you have PowerShell Core installed (recommended for better performance).
How It Works
Claude ←→ MCP (stdio) ←→ Node.js Server ←→ PowerShell Scripts ←→ UIAutomation ←→ Phone Link UIClaude calls an MCP tool (e.g.,
phonelink_get_messages)The Node.js server executes the corresponding PowerShell script
The PowerShell script uses .NET's
System.Windows.Automationto:Find the Phone Link window
Navigate to the correct tab
Traverse the UI element tree
Extract text, names, and metadata
Results are returned as JSON through the MCP protocol
Environment Variables
Variable | Default | Description |
|
| PowerShell executable path |
Troubleshooting
"Phone Link window not found"
Make sure Phone Link is running (use
phonelink_launch_appfirst)Check that Phone Link's window title matches expected names. Use
phonelink_inspect_uito debug.The server searches for: "Phone Link", "Collegamento al telefono", "Il tuo telefono", "Your Phone"
UI elements not found
Phone Link updates may change the UI structure. Use
phonelink_inspect_uito see current elements.Try increasing
max_depthin inspect_ui to find deeper elements.The PowerShell scripts include multi-language support (EN, IT, DE, ES) but your locale might use different strings.
Slow responses
UI Automation traversal can be slow, especially with high
max_depth.Keep
max_depthat 10-12 for most operations.The first call after launching Phone Link may be slower while the UI loads.
Permission issues
PowerShell must run with sufficient privileges to use UIAutomation.
If running as a service, ensure the service account has access to the desktop session.
Limitations
UI-dependent: Changes to Phone Link's UI can break scraping. Use
inspect_uito adapt.Single language per session: Element names depend on the Windows display language.
No photo download: The photos tool lists metadata but cannot export actual image files.
Sequential only: Only one tool should run at a time (concurrent UI automation will conflict).
Foreground required: Phone Link window must be visible (not minimized) for some operations.
Development
npm run dev # Watch mode
npm run build # Build once
npm start # Run serverLicense
MIT
Available Tools
9 toolsphonelink_get_callsGet Call HistoryARead-only
Read recent call history from Phone Link's Calls tab.
Navigates to the Calls tab and scrapes the visible call list. Each entry includes the contact/number, call type (incoming/outgoing/missed), and display text.
Args:
max_calls (number): Maximum call entries to return (1-100, default: 20).
Returns: { "call_count": number, "calls": [{ "display_text": string, // Full text shown for the call entry "call_type": "incoming" | "outgoing" | "missed" | "unknown", "automation_id": string }] }
Inputs: max_calls.
phonelink_get_messagesGet Phone MessagesARead-only
Read SMS messages from Phone Link's Messages tab.
Two modes:
List conversations: Leave conversation_name empty to get a list of all visible conversations with their last message previews.
Read conversation: Provide a contact name to open and read messages from that specific conversation.
Args:
conversation_name (string, optional): Contact name to open. Empty = list all conversations.
max_messages (number): Max messages/conversations to return (1-100, default: 20).
navigate_to_tab (boolean): Click the Messages tab first (default: true).
Returns (list mode): { "conversation_count": number, "conversations": [{ "contact": string, ... }] }
Returns (conversation mode): { "conversation": string, "message_count": number, "messages": [{ "text": string, ... }] }
Tips:
Use list mode first to discover available conversations.
The contact name must match what's displayed in the Phone Link UI.
Inputs: max_messages, navigate_to_tab, conversation_name.
phonelink_get_notificationsGet Phone NotificationsARead-only
Read phone notifications from Phone Link's Notifications panel.
Navigates to the Notifications section and scrapes all visible notification entries. Useful for checking app notifications, system alerts, and other phone notifications mirrored to PC.
Args:
max_notifications (number): Max notifications to return (1-100, default: 30).
Returns: { "notification_count": number, "notifications": [{ "text": string, "control_type": string, ... }] }
Inputs: max_notifications.
phonelink_get_photosGet Phone PhotosARead-only
List recent photos from Phone Link's Photos tab.
Navigates to the Photos tab and scrapes the visible photo grid. Returns metadata about each photo entry (name, bounds, type). Note: This does NOT download photos — it lists what's visible in the UI.
Args:
max_photos (number): Maximum photo entries to return (1-100, default: 25).
Returns: { "photo_count": number, "photos": [{ "name": string, "bounds": { x, y, width, height }, ... }] }
Inputs: max_photos.
phonelink_get_statusGet Phone Link StatusARead-onlyIdempotent
Get the connection status of Phone Link (MyPhone) and basic phone info.
Returns whether the phone is connected, the phone name/model, and whether the app is running. Use this as the first tool call to verify Phone Link is available before using other tools.
Returns: { "connected": boolean, // Whether the phone is connected "status": string, // Status text from the UI "phone_name": string, // Phone model/name if detected "app_running": boolean // Whether Phone Link is running }
Error Handling:
If Phone Link is not running, returns connected=false with an appropriate status message.
Use phonelink_launch_app to start it first if needed.
Inputs: no named parameters.
phonelink_inspect_uiInspect Phone Link UI TreeARead-onlyIdempotent
Debug tool: dumps the Phone Link UI automation tree as JSON.
Use this to discover UI element names, automation IDs, control types, and bounding rectangles. Helpful for troubleshooting when other tools can't find expected elements.
Args:
max_depth (number): Maximum tree depth (1-25, default: 10). Higher = more elements but slower.
filter_control_type (string, optional): Only return elements of this type (e.g. "Text", "Button", "ListItem").
Returns: { "element_count": number, "window_name": string, "elements": [{ "Name": string, "ControlType": string, "AutomationId": string, ... }] }
Inputs: max_depth, filter_control_type.
phonelink_launch_appLaunch Phone LinkAIdempotent
Launches the Phone Link app if not already running.
Uses the ms-phone: protocol handler to open Phone Link. Wait a few seconds after calling this before using other tools.
Returns: { "launched": boolean, "message": string }
Inputs: no named parameters.
phonelink_make_callMake Phone CallA
Initiate a phone call through Phone Link's dial pad.
Opens the Calls tab, enters the phone number, and clicks the call button. This triggers a real phone call from your connected phone.
Args:
phone_number (string): The number to call (include country code if needed).
Returns: { "initiated": boolean, "phone_number": string }
⚠️ WARNING: This initiates a REAL phone call. Verify the number before calling.
Inputs: phone_number (required).
phonelink_send_messageSend SMS MessageA
Send an SMS message through Phone Link's UI.
Opens a new message, types the recipient and message text, and clicks Send. This interacts with the Phone Link UI to send a real SMS from your phone.
Args:
recipient (string): Contact name or phone number.
message_text (string): The message to send (max 1600 chars).
Returns: { "sent": boolean, "recipient": string, "message": string }
⚠️ WARNING: This sends a REAL SMS. Verify recipient and message before calling.
Error Handling:
Returns sent=false with error message if any UI element can't be found.
Common issues: Phone not connected, Messages tab not loading, UI layout changes.
Inputs: recipient (required), message_text (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a distinct Phone Link surface or action: status, photos, messages, calls, notifications, UI inspection, send, call, and launch. There is no meaningful overlap between get_messages and get_calls or between send_message and make_call, and the debug tool is clearly differentiated as a troubleshooting utility.
All tools share the phonelink_ prefix and use consistent snake_case verb_noun patterns: get_* for read operations and send_message, make_call, and launch_app for actions. This makes it easy to predict a tool's behavior from its name.
Nine tools is well-scoped for a Phone Link automation server: it covers the main phone data surfaces plus two user-initiated actions and a launcher/debug aid. Each tool earns its place without bloat or obvious omissions.
The set covers the main Phone Link workflows: connection status, launching the app, reading photos/messages/calls/notifications, sending an SMS, and making a call. Minor gaps exist—photos are not downloadable and notification actions are absent—but these are reasonable boundaries for a UI-automation MCP server.
Maintenance
Related MCP Connectors
The official Planning Center MCP server for interacting with your ministry's data.
MCP connector for iMessage & Contacts via a local Mac agent + Vercel relay
MCP server for FormBro Canadian immigration application automation.
Your own WhatsApp as an MCP server: read, search and send from any MCP client.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for a local-first messaging workspace that integrates Google Messages, WhatsApp, and Signal. It enables reading, sending, searching messages, and managing conversations through MCP tools.73-
- AlicenseNot gradedqualityDmaintenanceMCP server for driving any Windows app through five layers including OCR, UI Automation, and direct OS operations. Enables AI agents to control Windows desktop and OS cursor-free, even on background/locked windows.122 npm3MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that lets an LLM see and drive any running Windows app: attach a window, screenshot it, read its UI Automation tree, and send clicks, typed text, and key presses with pixel coordinates.-
- AlicenseAqualityDmaintenanceWindows desktop automation MCP server enabling screenshot capture, precise visual locating of UI elements via vision models, and automated mouse clicking.41MIT