Skip to main content
leom
Rookie
August 31, 2026

MCP feedback on daily usage

  • August 31, 2026
  • 2 replies
  • 34 views

Hello Front team,


We’ve been testing the Front MCP with Claude and overall, it’s been super useful for our CSM team! 

Being able to interact with Front directly from Claude has a lot of potential for our day-to-day workflows, especially when it comes to understanding conversations, drafting replies, and saving time on email management in general.

After using it regularly, we’ve also identified a few things that were impacting our experience, and we wanted to share it with you :

  • Images & screenshots: Claude doesn’t seem to be able to read screenshots or images embedded in emails ? And this is sometimes key for the context
  • Draft iterations: When asking Claude to improve or modify an existing draft, it sometimes creates a new draft instead of updating the previous one. Being able to iterate on the same draft would make the workflow much smoother.
  • Draft refresh in Front: Updates made through the MCP don’t always appear immediately in the Front interface. We sometimes need to open the message in a pop-up, or switch to another conversation and come back, to see the updated draft.
  • CC recipients: When creating a draft reply, the original CC recipients aren’t always preserved, sometimes only the sender is included.
  • Long threads & confidence: On longer conversations, Claude can occasionally miss information that is explicitly mentioned earlier in the thread. Don’t know if there is a specific limit on this?
  • Email Templates: This is not (yet) possible to manage email template via the MCP, but maybe planned on your side?

Overall, we’re really enjoying the integration and see a lot of value in. These improvements would make the workflow even more reliable and seamless for teams like ours using it on a daily basis.

Happy to share more details or examples if useful!

Léo

2 replies

Javier - Developer Relations
Community Manager
August 31, 2026

Hi ​@leom, thanks for the excellent feedback! The team is always grateful for the opportunity to improve the product to better suit customer needs. A few initial thoughts:
 

  • Images & screenshots: You can download attachments from conversations through our MCP server, but processing and understanding them comes down to the capabilities of your AI assistant. This is likely something that would be improved from Claude’s end first.
  • Draft iterations: The team will be discussing this, thanks for pointing it out!
  • Draft refresh in Front: Thanks for letting us know, we can see if there are any improvements that can be made here too.
  • CC recipients: I’ll check on what the intended behavior is here. When replying to all, the CC recipients shouldn’t be dropped.
  • Long threads & confidence: This seems like a limitation on Claude’s end. Sometimes being very explicit in your prompt to Claude that all messages are equally important might help Claude preserve the entire conversation history when it answers.
  • Email Templates: This was recently brought up by another customer here, so the team is investigating what can be prioritized. This would definitely be useful!
Javier - Front Developer Relations
Javier - Developer Relations
Community Manager
August 31, 2026

P.S. For the draft iterations and the CC recipients feedback, does explicitly telling Claude to use the update_draft tool help? An AI agent like Claude might make a suboptimal decision to delete and recreate but pointing out that you prefer to update in place should help it choose the right tool going forward.

On the replies, the default is to reply to all, so if you continue to see the CC’s being dropped when you haven’t explicitly asked to reply to one recipient, could you please contact our Support team so that we can investigate a specific conversation for you? Same for the draft refresh...if you think this is taking too long then our team can dig into a specific conversation on your account to see if there is a bug or latency issue.

Javier - Front Developer Relations