Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Front to Claude Code

Let Claude draft, route, and send replies inside your shared inbox in Front. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Front to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Front, you add a Front MCP server: a small hosted service that exposes Front's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Front account. No API keys pasted into config files.

claude mcp add --transport http front https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Front once connected?

Full read-write Front access lets Claude draft a reply inside the original conversation, keep recipients and history intact, assign it to a teammate, apply tags, add an internal comment, archive, and send once you approve. The triage and drafting that used to mean copy-paste happen where the conversation already lives.

  • Draft a reply inside an existing conversation, preserving recipients and history
  • Assign or reassign conversations to the right teammate or inbox
  • Apply or remove tags to triage and route the shared inbox
  • Add an internal comment to brief the team without emailing the customer
  • Archive or reopen conversations as you clear the queue
  • Send a drafted reply after you approve it

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Front access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Front API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Front changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Front connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Front connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Front account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Front's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Front?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Front account it signs in with. Revoking access is one click in Front.

More on the Front connector

Front connector for claude.aiGmail + Claude CodeOutlook + Claude CodeSlack + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us