feat(gmail): Add from_name parameter for sender display name

[peterhartree]

Summary

• Adds optional from_name parameter to send_gmail_message and draft_gmail_message functions
• When provided, the From header is formatted as "Name <email>" instead of just the email address

Motivation

Currently, emails sent via the MCP server only include the bare email address in the From header, even when the user has a display name configured in their Gmail account settings. This differs from composing emails directly in Gmail, where the display name is automatically included.

This change allows users to specify their display name when sending emails, resulting in a more professional appearance and consistency with Gmail's native behaviour.

Example usage

send_gmail_message(
    to="[email protected]",
    subject="Hello",
    body="Hi there!",
    from_name="Peter Hartree"
)

Results in: From: Peter Hartree <[email protected]>

Test plan

• Tested send_gmail_message with from_name parameter - From header correctly formatted
• Tested draft_gmail_message with from_name parameter - draft shows correct From header
• Tested without from_name parameter - backwards compatible, behaves as before

🤖 Generated with Claude Code

[taylorwilsdon]

Seems like a useful mechanism, I do use different send-as addresses. Will take a look!

[Copilot]

Pull request overview

This PR adds support for customizing the sender's display name in Gmail messages by introducing an optional from_name parameter. When provided, emails will show "Name " in the From header instead of just the email address, matching Gmail's native behavior.

Changes:

• Added from_name optional parameter to send_gmail_message and draft_gmail_message functions
• Modified _prepare_gmail_message to format the From header as "Name <email>" when from_name is provided
• Updated documentation and examples to demonstrate the new parameter

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The from_name parameter is not sanitized before being inserted into the email header. Special characters like quotes, angle brackets, or newlines could break the email header format or be exploited for header injection attacks. Consider using email.utils.formataddr() to properly format and escape the display name, or implement validation to reject names containing problematic characters.

[taylorwilsdon]

Looks like it needs a ruff format but otherwise this looks great, thanks!