Tuesday, Mar 17, 2026
shippedPylon replies MCP server with email support
Buğra Gündüz shipped an initial MCP server for sending customer-facing replies on Pylon issues, then refined it by removing destructive tools and adding email recipient handling.
1 person shipped this
The work began with an initial commit to bgrgndzz/pylon-replies-mcp, a Model Context Protocol server built to handle customer replies on Pylon issues [1]. The server exposed six tools: search_issues, get_issue, get_issue_messages, reply_to_issue, delete_message, and redact_message.
On the same day, Gündüz removed the delete_message and redact_message tools [2]. The reasoning was clear in the commit: "These are tangential to the replies focus and are irreversible destructive operations that don't belong in a reply-focused MCP."
He then fixed a gap in the reply tool by adding an email_info parameter to reply_to_issue [3]. This addressed the "No email recipients specified" error that occurred on email-based tickets by allowing explicit to, cc, and bcc addresses. The same change made message_id optional, aligning the tool with the API specification.
Gündüz finished the day by bumping the version to 1.0.1 [4] to reflect the email support and the removal of the destructive tools.
Sources
- Initial commit: Pylon replies MCP server · bgrgndzz/pylon-replies-mcp
- Remove delete_message and redact_message tools · bgrgndzz/pylon-replies-mcp
- Add email_info parameter to reply_to_issue · bgrgndzz/pylon-replies-mcp
- Bump version to 1.0.1 · bgrgndzz/pylon-replies-mcp