reply_to_inbox_message — purrplan MCP Tool
reply_to_inbox_message
(reply to inbox message) is one of 18 tools on the
purrplan
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call reply_to_inbox_message from your client
- Claude Code purrplan reply_to_inbox_message run in your project directory
- Claude Desktop purrplan reply_to_inbox_message ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor purrplan reply_to_inbox_message ~/.cursor/mcp.json
- VS Code purrplan reply_to_inbox_message .vscode/mcp.json
- Zed purrplan reply_to_inbox_message ~/.config/zed/settings.json
- Windsurf purrplan reply_to_inbox_message ~/.codeium/windsurf/mcp_config.json
- Cline purrplan reply_to_inbox_message ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI purrplan reply_to_inbox_message ~/.gemini/settings.json
- Grok purrplan reply_to_inbox_message .mcp.json (in your project root)
- ChatGPT purrplan reply_to_inbox_message Settings → Connectors → Advanced → Developer mode
- Claude.ai purrplan reply_to_inbox_message Settings → Connectors → Add custom connector
- LangChain purrplan reply_to_inbox_message pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http purrplan https://app.purrplan.ai/api/mcpOther tools on this server
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.