Helpdesk
Front MCP connector
The Front connector brings your shared inboxes, conversations, teammates, teams and accounts into Claude, ChatGPT, Cursor and any MCP client, so each person can find, assign, remind and update Front conversations from an AI assistant while signed in as themselves.
-
How it connects. OAuth or API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Front to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Front once
-
Open Connections, choose Add connection, and pick Front.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Front app, then approve. Front needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Front to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Front to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Front to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Front to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Front through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Find what is waiting in the inbox
Ask which Front conversations are still open, unassigned or overdue in a given inbox, and get a list you can act on before the queue builds up.
-
Support
Hand a conversation to the right teammate
When a ticket lands with the wrong person, reassign the Front conversation to the teammate who owns that customer without opening Front.
-
Customer success
Set a follow-up reminder after a call
Once a check-in is done, put a reminder on the Front conversation so it comes back to you on the day you promised to follow up.
-
Sales
Add a note to the customer thread
Drop a message into the Front conversation with what was agreed on a call, so the rest of the team sees the context in the same thread.
-
Account management
Keep account records current
Look up a Front account, see which conversations belong to it, and create a new account when a customer is missing from the list.
-
Operations
Set up inboxes and teams for a new group
When a new region or product line launches, create the Front inbox and team it needs and check which teammates belong to it.
Try asking
- “Which Front conversations in Support are unassigned right now?”
- “Summarize open conversations in the Billing inbox today.”
- “Who on the Front sales team has the heaviest queue?”
AI tools
Front tools for your AI agents
243 tools are ready to call through Elaichi's MCP endpoint the moment you connect Front, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Front gets you
6 screens from the product, each doing one job for your Front account.
The agent
Ask about Front conversations, get real answers.
Plain language questions run against live Front conversations, inboxes and teammates.
- conversations
- inboxes
- teammates
- teams
Ask Elaichi to work across your apps.
Which Front conversations in Support are unassigned right now?
Summarize open conversations in the Billing inbox today.
Who on the Front sales team has the heaviest queue?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Front here.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
243 Front tools ready without custom code.
Conversations, inboxes, teams, teammates, comments and tags, every method already wired.
- List all Front teammates
- Get single Front teammate by ID
- Update a Front teammate by ID
- List all Front teams
Toolboxes
Each team gets its own Front toolbox.
Support, sales and ops each see the Front tools their work needs.
- Support
- Sales
- Success
- Operations
Shared connections
Teammates work in Front without a credential.
One person connects the Front account, shared teams and members use it safely.
- Support EMEA
- Support US
- Sales inbound
- Customer success
Audit log
Every Front call has a name on it.
When, who, what happened, type and resource for each conversation and inbox touched.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts your Front digest nightly.
Fetch conversations, group them, draft a digest, approve it, post back to Front.
Front digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch conversations
Front
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Front
Queued
Collections and dashboards
Front inbox health, counted not guessed.
Four metrics, 14 days of conversations created, split by team, refreshed on schedule.
Front health
Refreshed 4 minutes ago · every 15 minutes · from the conversations collection
Conversations
1,284 ↓ 12%
Inboxes
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Conversations created
Last 14 days
By team
Share of activity
Support EMEA 34%
Support US 27%
Sales inbound 21%
Customer success 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Front to Claude?
Two steps. First connect Front in Elaichi: Front asks you to register an OAuth application inside Front's own developer settings, so someone on your team brings that client ID and secret into Elaichi once, or you can paste a Front API key instead. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Front is available in Claude.
Does Front work with ChatGPT and Cursor as well as Claude?
Yes. Front is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. Each person signs in once per client and their Front access follows them.
What can an AI agent actually do with my Front data?
With Front connected, an agent can list and read conversations in your shared inboxes, assign a conversation to a teammate, set or change reminders, add a message to a thread, and create new conversations. It can also look up teammates, teams, inboxes, accounts and recent events, and create inboxes, teams and accounts when you ask. Front has a lot it can do, so short concrete asks such as "show unassigned conversations in the billing inbox" work better than long instructions.
Does connecting Front give the AI access to every inbox?
No. Every call runs inside the Front access of the person who signed in, so the agent only sees the inboxes, conversations and accounts that person can already see in Front. Elaichi can narrow that access further with restrictions, and it can never widen it beyond what Front itself allows.
Can I stop an agent from deleting or changing things in Front?
Yes. Restrictions in Elaichi work per action, so you can allow reading Front conversations while blocking deleting conversations, teams or accounts, or blocking updates entirely. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt can reach it.
What happens to a Front connection when someone leaves?
Offboarding a person in Elaichi ends their access to Front through every client at once, with nothing to revoke inside Claude, ChatGPT or Cursor separately. A Front connection shared with a team keeps working for everyone else. If you ever want Front gone entirely, disconnecting it once in Elaichi removes it from every client.
Put Front in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.