Connect Front to Town
Waiting threads surfaced before they age, replies drafted from the full conversation, and customer history in every brief — from your Front shared inbox, through Front's official MCP server.
Min swept the support inbox and drafted replies for the three threads still waiting.
See it work: a routine that clears the queue before you sit down
Morning queue sweep with replies ready
Replies ready every morning. Nothing sends without you.
Open Integrations in Town
Go to Integrations in your Town workspace (free to create) and find Front.
Authorize the connection
Sign in to Front when prompted. Town connects through Front's official MCP server (mcp.frontapp.com), so there's nothing to install or configure.
Put your shared inbox to work
Done — your Townie can search conversations, pull customer history into briefs, and draft replies and triage that wait for your approval.
Routines that use Front
Ready-made routines from the Town library, built on Front. Install one and tailor it to how you work.
Just ask your Townie
Front holds the conversations. Town turns them into digests, briefs, and replies waiting for your sign-off.
“What's sitting in the support inbox that we haven't answered?”
Every waiting thread, ranked by how long the customer's been waiting, in one chat summary.
“Pull up our Front history with Meridian before the renewal call.”
Their open threads, past conversations, and account details, drafted into your prep doc.
“Draft a reply to the refund thread in my voice.”
A reply drafted from the full thread, waiting in Front for your approval.
Front integration FAQ
The Front MCP is Front's hosted Model Context Protocol server at mcp.frontapp.com — the official integration surface Front maintains. MCP is the open standard that lets AI assistants securely work with data from apps — in this case your shared inboxes, conversations, contacts, and accounts. Town connects to it with your Front sign-in; no API keys or local setup.
Town only reaches Front when you (or a routine you configured) ask for it, and the connection sees exactly what your own Front teammate account can see — private inboxes stay private. Every action with outside effects, from drafts to sends to triage, waits for your approval. Read more about how Town approaches security.
No. Sending a message, saving a draft, assigning, tagging, moving, changing a conversation's status, and adding a comment each wait for your explicit approval, every single time — even inside routines that otherwise run on their own. Sending is never automatic.
Whatever your Front teammate account can access, and nothing more: conversations and their full message history, message attachments, contacts, company accounts, your own in-flight drafts, and your workspace's inboxes, teams, channels, tags, teammates, and statuses. With your approval it can also create and update drafts, send replies, triage conversations, and add internal comments.
Town works with your regular Front teammate account — the connection acts as you, so your Front role sets what it can see and do. Each teammate connects their own account (there's no shared team connection). On the Town side you just need an account: free to start.
Front is where your team answers customers. Town is where the inbox stops being a chore: waiting threads surface in your morning digest, customer history lands in your call prep, and replies arrive pre-drafted — you review in Front and hit send.
What is Front?
Front is the customer operations platform built around a shared inbox — the place where support, success, and sales teams answer customer email together, with assignments, tags, and internal comments keeping everyone in sync.
Front holds the conversations; Town puts them to work. Connected, waiting threads surface before they age, customer history arrives ahead of every call, and replies show up drafted — waiting for your approval.
