phone_read_messages — Palmyr MCP Tool
phone_read_messages
(phone read messages) is one of 33 tools on the
Palmyr
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call phone_read_messages from your client
- Claude Code Palmyr phone_read_messages run in your project directory
- Claude Desktop Palmyr phone_read_messages ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Palmyr phone_read_messages ~/.cursor/mcp.json
- VS Code Palmyr phone_read_messages .vscode/mcp.json
- Zed Palmyr phone_read_messages ~/.config/zed/settings.json
- Windsurf Palmyr phone_read_messages ~/.codeium/windsurf/mcp_config.json
- Cline Palmyr phone_read_messages ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Palmyr phone_read_messages ~/.gemini/settings.json
- Grok Palmyr phone_read_messages .mcp.json (in your project root)
- ChatGPT Palmyr phone_read_messages Settings → Connectors → Advanced → Developer mode
- Claude.ai Palmyr phone_read_messages Settings → Connectors → Add custom connector
- LangChain Palmyr phone_read_messages pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http palmyr https://palmyr.ai/mcp
Other tools on this server
- palmyr_pricing
- palmyr_capabilities
- i402_plan
- card_buy
- card_status
- card_get
- card_list
- email_create_inbox
- email_create_temp
- email_extend_temp
- email_send
- email_read_messages
- phone_buy_number
- phone_send_sms
- wait_for_otp
- phone_temp_number
- phone_extend_temp
- twitter_post
- tiktok_post
- tiktok_operation_status
- tiktok_connect
- tiktok_connect_status
- tiktok_accounts
- tiktok_analytics
- tiktok_series
- tiktok_hooks
- tiktok_niches
- tiktok_scheduled
- tiktok_cancel_scheduled
- domain_check
- domain_register
- compute_deploy
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.