The Front MCP Server is here (beta)

I’ve given it a whirl - as you already know the top priority would be properly scoping permissions per user. Beyond that though, the current tools that are exposed are a bit unusual for an MCP for a service like this. Claude (for example) is ultimately able to achieve what it needs here, but not in a highly efficient way. I’d love to see specific tools for fetching inboxes, fetching and filtering conversations by status/tags/etc, more natively as tools w/ params.

Thanks for the feedback, ​@jetlagdev. This beta release is scoped and configured similarly to our API. For the full release, the team will be evaluating a more tailored approach based on comments like yours.

Is there any documentation on what endpoints are available in the MCP? 

What are some of the practical ways we can use the MCP?

Hey ​@zeek, you can ask your AI agent for the full list of available endpoints. You can also ask it for ideas on how to use those endpoints. In general, the endpoints we’ve made available for this beta release are related to conversation data and related resources such as inboxes and teammates. Most of the endpoints are read only, but you can post tags, add comments, and create draft replies.

It would be great if other users could share their real-world use cases with us here for inspiration and feedback on what may or may not be working well with the beta MCP server.

Thanks everyone!

Just requested access, thanks!

Hey! Quick question on the MCP beta: any plans to support the native MCP OAuth flow so Claude Desktop (and similar) can handle the auth handshake directly, instead of us writing a wrapper to fetch the token and pass it as a Bearer header?

Would be a big UX win for non-dev teammates, and a natural fit with the per-user token support you hinted at. Thanks!

Hey ​@make — I’ve noted this feedback for the team. Based on early discussions, we will be prioritizing a user-based OAuth flow for the full release of the MCP server, so supplying it such that you don’t have to write an extra wrapper is a likely result.

Hi everyone, we’d like to gather your input: which services would be useful to connect Front into? We’re planning to submit an official Claude connector with the launch of the full MCP server, but also try to get the Front MCP server connected to services like Slack and Notion.

It would be helpful to hear directly from the community regarding which services you’re interested in!

All three plz! 😍

any chance I can still get on the beta?

Would it be possible for the Front MCP to be remote first? The local MCP design is quite limiting and requires you to work in claude cowork which is more challenging for users who switch between different machines (home/work)

​@pablo We are targeting the next iteration release (which will use a different server URL and come with added benefits) for end of month. Given how close we are to that, we have closed the current beta in favor of customers trying the new MCP server, which we have built from the ground up based on the feedback.

I will communicate broadly once this becomes available!

Sounds good. The current MCP is struggling with how Front presents emails to the user it seems. The internal view logic needs to somehow be mirrored in the mcp design otherwise it is a real challenge to pull the right conversations into Claude.

could you also clarify if the existing MCP remains usable? Thanks

Hey ​@marklaz81 I accidentally copied you in my response to Pablo. Regarding your questions:
 

• The next iteration of the MCP server will make it easier to connect remotely, including being listed in Claude’s connector directory.
• Hopefully, the new MCP server will present conversations more effectively for you, as our engineers have built it from the ground up rather than it being a wrapper over our Core API like the existing beta is. However, please reach out after the next release if you still see the same issues here!
• The existing MCP server beta will remain live for a limited period of time. After the release of the next iteration, we will email beta users with the timeline for when the old URL will no longer work. If you have any feedback about timing when you see this email, just let us know and we can work with you.

Would love to use this with claude.  When will it be released?  

Hey ​@dannyprecise,

We plan to release the next iteration of the MCP server by end of month, barring any unexpected delays. You will be able to connect to it as a custom connector in Claude, and depending on how long it takes Anthropic to review our submission, you will be able to connect it directly from the Claude directory not long after we launch.

We will post an update here and in our other community announcement spaces when this launches!