How do AI agents use Front through Open Connector?

Your user connects Front once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Front tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a Front MCP server?

Yes. Open Connector can serve Front as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Front actions with credentials injected server-side.

Where do Front credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Front integration

Front integration for AI agents.

Front integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Front tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real Front actions, managed and audited.

Your user connects Front once; your agent can then secure AI-agent actions — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants Front access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Front tools.

244 tools are generated from the published Front catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 244 tools. All published catalog entries are included in this page's server-rendered HTML.

Add comment: Add a comment to a [conversation](https://dev.frontapp.com/reference/conversations). If you want to create a new comment-only conversation, use the [Create discussion conversation](https://dev.frontapp.com/reference/create-conversation) endpoint. Required scope: `comments:write`; Comments
Add comment reply: Add a reply to a comment on a [conversation](https://dev.frontapp.com/reference/conversations). Comment replies visually indicate which comment is being responded to, helping users follow the conversation. Required scope: `comments:write`; Comments
Add teammate group team inboxes: Links non-public inboxes to the teammate group. The inbox must be part of a team that has been added to the teammate group. Required scope: `teammate_groups:write`; Teammate groups
Add teammate group teammates: Add teammate group teammates. Note - You cannot modify a teammate group that is managed by SCIM. Required scope: `teammate_groups:write`; Teammate groups
Add teammate group teams: Adds teams to the teammate group. Any teams added to the teammate group will automatically link public inboxes. Non-public inboxes can be added to the teammate group separately. Required scope: `teammate_groups:write`; Teammate groups
Add contact handle: Adds a new handle to a contact. Required scope: `contacts:write`; Contact Handles
Add contact to Account: Adds a list of contacts to an Account Required scope: `accounts:write`; Accounts
Add contacts to contact list: Add contacts to the requested contact list. Required scope: `contacts:write`; Contact Lists
Add contacts to group: Add contacts to the requested group. > ⚠️ Deprecated endpoint > > This endpoint has been deprecated. Please use the compatible contact list endpoints instead. > - `POST /contact_lists/{contact_list_id}/contacts`. Required scope: `contacts:write`; Contact Groups
Add conversation followers: Adds teammates to the list of followers of a conversation. Required scope: `conversations:write`; Conversations
Add conversation link: Adds one or more links to a conversation For more information on links, see the [Links](https://dev.frontapp.com/reference/links) topic. Required scope: `conversations:write`; Conversations
Add conversation tag: Adds one or more tags to a conversation Required scope: `conversations:write`; Conversations
Add inbox access: Give access to one or more teammates to an inbox. Required scope: `inboxes:write`; Inboxes
Add note: Create a new note on a contact. Required scope: `contacts:write`; Contact Notes
Add teammates to shift: Add teammates to a shift. The selected teammates must be in the team that owns the shift. Required scope: `shifts:write`; Shifts
Add teammates to team: Add one or more teammates to a team (workspace). Required scope: `teams:write`; Teams
Add view to teammate sidebars: Makes this view visible in specified teammates' sidebar navigation. Required scope: `views:write`; Views
API Token details: Fetch the details of the API token.; Token Identity
Create a channel: Create a channel in an inbox. Required scope: `channels:write`; Channels
Create a knowledge base: Creates a knowledge base. Required scope: `knowledge_bases:write`; Knowledge Bases
Create account: Create a new account. Required scope: `accounts:write`; Accounts
Create a new analytics export: Create a new analytics export of messages or events (activities) over a specific time span. The export will be executed asynchronously. The response will include a link that can be used to retrieve the export status & result. Refer to the [Analytics](https://dev.frontapp.com/reference/analytics) topic for details about specific metrics. Required scope: `analytics:read`; Analytics
Create a new analytics report: Create a new analytics report for a set of metrics over a specific time span. Different filters (e.g. Inbox v Tag v Teammates) will be joined with AND logic, but the IDs within a filter will be joined with OR logic (e.g. Inbox A or Inbox B, Tag A or Tag B). The report will be executed asynchronously. The response will include a link that can be used to retrieve the report status & result. Refer to the [Analytics](https://dev.frontapp.com/reference/analytics) topic for details about specific metrics. Required scope: `analytics:read`; Analytics
Create article in a knowledge base in default locale: Creates an article in a knowledge base in the default locale. Required scope: `knowledge_bases:write`; Knowledge Bases
Create article in a knowledge base in specified locale: Create an article for a given locale in a knowledge base. Required scope: `knowledge_bases:write`; Knowledge Bases
Create child folder: Create a new message template folder as a child of the given folder Required scope: `message_templates:write`; Message Template Folders
Create child tag: Creates a child tag. Required scope: `tags:write`; Tags
Create child template: Create a new message template as a child of the given folder Required scope: `message_templates:write`; Message Templates
Create company tag: Create a company tag. Required scope: `tags:write`; Tags
Create teammate group: Create a new teammate group. Required scope: `teammate_groups:write`; Teammate groups
Create contact: Create a new contact at the company level. Required scope: `contacts:write`; Contacts
Create contact list: Create a new contact list in the oldest active workspace that the token has access to. If you need to specify the workspace, we recommend using the [Create team contact list](https://dev.frontapp.com/reference/create-team-contact-list) endpoint instead. Required scope: `contacts:write`; Contact Lists
Create discussion/task conversation: Create a new [conversation](https://dev.frontapp.com/reference/conversations#creating-a-new-conversation) of type discussion or task. Both types only support comments. If you want to create a conversation that supports messages, use the [Create message](https://dev.frontapp.com/reference/post_channels-channel-id-messages) endpoint. If you want to add a comment to an existing conversation, use the [Add comment](https://dev.frontapp.com/reference/post_conversations-conversation-id-comments) endpoint. Required scope: `conversations:write`; Conversations
Create draft: Create a draft message which is the first message of a new [conversation](https://dev.frontapp.com/reference/conversations). Required scope: `drafts:write`; Drafts
Create draft reply: Create a new draft as a reply to the last message in the conversation. Required scope: `drafts:write`; Drafts
Create folder: Create a new message template folder in the oldest active workspace that the token has access to. If you need to specify the workspace, we recommend using the [Create team folder](https://dev.frontapp.com/reference/create-team-folder) endpoint instead. Required scope: `message_templates:write`; Message Template Folders
Create group: Create a new contact group in the default team (workspace). > ⚠️ Deprecated endpoint > > This endpoint has been deprecated. Please use the compatible contact list endpoints instead. > - `POST /contact_lists`. Required scope: `contacts:write`; Contact Groups
Create inbox: Create an inbox in the oldest active workspace that the token has access to. If you need to specify the workspace, we recommend using the [Create team inbox](https://dev.frontapp.com/reference/create-team-inbox) endpoint instead. Required scope: `inboxes:write`; Inboxes
Create knowledge base category in default locale: Creates a knowledge base category in the default locale. Required scope: `knowledge_bases:write`; Knowledge Bases
Create knowledge base category in specified locale: Creates a knowledge base category for a given locale. Required scope: `knowledge_bases:write`; Knowledge Bases
Create link: Create a link. You must supply either `pattern` or `external_url` in the request, but not both (`pattern` is for application objects while `external_url` is for standard links). If `pattern` is provided, the API call updates the application objects matching the exact pattern. Keep in mind this endpoint only creates or updates an existing link from an application object. It does not create new application objects. If the link is resolved to an installed links integration, any name retrieved from the integration will override the provided name in the request. Required scope: `links:write`; Links
Create message: Send a new message from a channel. This is one of the ways to create a new [conversation](https://dev.frontapp.com/reference/conversations#creating-a-new-conversation). The new conversation will support both messages and comments (discussions). Required scope: `messages:send`; Messages
Create message reply: Reply to a conversation by sending a message and appending it to the conversation. Required scope: `messages:send`; Messages
Create message template: Create a new message template in the oldest active workspace that the token has access to. If you need to specify the workspace, we recommend using the [Create team message template](https://dev.frontapp.com/reference/create-team-message-template) endpoint instead. Required scope: `message_templates:write`; Message Templates
Create shift: Create a shift in the oldest active workspace that the token has access to. If you need to specify the workspace, we recommend using the [Create team shift](https://dev.frontapp.com/reference/create-team-shift) endpoint instead. Required scope: `shifts:write`; Shifts
Create tag: Create a tag in the oldest team (workspace). This is a legacy endpoint. Use the Create company tag, Create team tag, or Create teammate tag endpoints instead. Required scope: `tags:write`; Tags
Create team contact: Create a contact for a team (workspace). Required scope: `contacts:write`; Contacts
Create team contact list: Create a new contact list for the requested team (workspace). Required scope: `contacts:write`; Contact Lists
Create team folder: Create a new message template folder belonging to the requested team (workspace). Required scope: `message_templates:write`; Message Template Folders
Create team group: Create a new contact group for the requested team (workspace). > ⚠️ Deprecated endpoint > > This endpoint has been deprecated. Please use the compatible contact list endpoints instead. > - `POST /teams/{team_id}/contact_lists`. Required scope: `contacts:write`; Contact Groups
Create team inbox: Create an inbox for a team (workspace). Required scope: `inboxes:write`; Inboxes
Create team message template: Create a new message template for the given team (workspace). Required scope: `message_templates:write`; Message Templates
Create team shift: Create a shift for a team (workspace). Required scope: `shifts:write`; Shifts
Create team signature: Create a new signature for the given team (workspace). Required scope: `signatures:write`; Signatures
Create team tag: Create a tag for a team (workspace). Required scope: `tags:write`; Tags
Create team view: Create a new view for a team. Required scope: `views:write`; Views
Create teammate contact: Create a contact for a teammate. Required scope: `contacts:write`; Contacts
Create teammate contact list: Create a new contact list for the requested teammate. Required scope: `contacts:write`; Contact Lists
Create teammate folder: Create a new message template folder belonging to the requested teammate. Required scope: `message_templates:write`; Message Template Folders
Create teammate group: Create a new contact group for the requested teammate. > ⚠️ Deprecated endpoint > > This endpoint has been deprecated. Please use the compatible contact list endpoints instead. > - `POST /teammates/{teammate_id}/contact_lists`. Required scope: `contacts:write`; Contact Groups
Create teammate message template: Create a new message template for the given teammate Required scope: `message_templates:write`; Message Templates
Create teammate private inbox: Create a private inbox for a teammate. Required scope: `inboxes:write`; Inboxes
Create teammate signature: Create a new signature for the given teammate Required scope: `signatures:write`; Signatures
Create teammate tag: Create a tag for a teammate. Required scope: `tags:write`; Tags
Create time off: Create a time off for a teammate. Required scope: `time_off:write`; Time Off
Delete a contact: Delete a contact. Required scope: `contacts:delete`; Contacts
Delete a knowledge base category: Deletes a knowledge base category. > ⚠️ Warning > > When a category is deleted, all articles in the category are also deleted. Required scope: `knowledge_bases:delete`; Knowledge Base Categories
Delete an account: Deletes an account Required scope: `accounts:delete`; Accounts
Delete an article: Deletes an article and all its content and translations. Required scope: `knowledge_bases:delete`; Knowledge Base Articles
Delete teammate group: Deletes a teammate group. Note - You cannot delete a teammate group that is managed by SCIM. Required scope: `teammate_groups:delete`; Teammate groups
Delete contact handle: Remove a handle from a contact. Required scope: `contacts:write`; Contact Handles
Delete contact list: Delete a contact lists. Required scope: `contacts:delete`; Contact Lists
Delete conversation: Permanently delete a conversation. The conversation must have status "trashed" (in the trash) before it can be permanently deleted. This action cannot be undone. Required scope: `conversations:delete`; Conversations
Delete conversation followers: Removes teammates from the list of followers of a conversation. Required scope: `conversations:write`; Conversations
Delete draft: Delete a draft message. Required scope: `drafts:delete`; Drafts
Delete folder: Delete a message template folder and child folders/templates Required scope: `message_templates:delete`; Message Template Folders
Delete group: Delete a contact group. > ⚠️ Deprecated endpoint > > This endpoint has been deprecated. Please use the compatible contact list endpoints instead. > - `DELETE /contact_lists/{contact_list_id}`. Required scope: `contacts:delete`; Contact Groups
Delete message template: Delete a message template Required scope: `message_templates:delete`; Message Templates
Delete signature: Delete signature Required scope: `signatures:delete`; Signatures
Delete tag: Delete a tag. Required scope: `tags:delete`; Tags
Delete time off: Delete a time off. Required scope: `time_off:delete`; Time Off
Download attachment: Download an attachment file. Required scope: `attachments:read`; Attachments
Download attachment for a comment: Download an attachment file for a given comment ID Required scope: `attachments:read`; Attachments
Download attachment for a message: Download an attachment file for a given message id. Should be used by partner channels. Required scope: `attachments:read`; Attachments
Download attachment for a message template: Download an attachment file for a given message template ID Required scope: `attachments:read`; Attachments
Download attachment from an article: Downloads the attachment from an article. Required scope: `knowledge_bases:read`; Knowledge Base Articles
Edit draft: Edit a draft message. Required scope: `drafts:write`; Drafts
Fetch an account: Fetches an account Required scope: `accounts:read`; Accounts
Get a knowledge base: Fetches a knowledge base. Required scope: `knowledge_bases:read`; Knowledge Bases
Get a knowledge base article: Fetches a knowledge base article. Required scope: `knowledge_bases:read`; Knowledge Base Articles
Get a knowledge base category: Fetches a knowledge base category. Required scope: `knowledge_bases:read`; Knowledge Base Categories
Get a knowledge base with content in default locale: Fetches a knowledge base with its content in the default locale. Required scope: `knowledge_bases:read`; Knowledge Bases
Get a knowledge base with content in specified locale: Fetches a knowledge base with its content for a given locale. Required scope: `knowledge_bases:read`; Knowledge Bases
Fetch an analytics export: Fetch an analytics exports. Refer to the [Analytics](https://dev.frontapp.com/reference/analytics) topic for details about specific metrics. Required scope: `analytics:read`; Analytics
Fetch an analytics report: Fetch an analytics report. Refer to the [Analytics](https://dev.frontapp.com/reference/analytics) topic for details about specific metrics. Required scope: `analytics:read`; Analytics
Get channel: Fetch a channel. Required scope: `channels:read`; Channels
Get child folders: Fetch the child message templates folders of a message template folder. Required scope: `message_templates:read`; Message Template Folders
Get child templates: Fetch the child message templates of a message template folder. Required scope: `message_templates:read`; Message Templates
Get comment: Fetches a comment. Required scope: `comments:read`; Comments
Get teammate group: Fetch a teammate group. Required scope: `teammate_groups:read`; Teammate groups
Get contact: Fetch a contact. Required scope: `contacts:read`; Contacts
Get conversation: Fetch a conversation. Required scope: `conversations:read`; Conversations
Get event: Fetch an event. Refer to the [Events](https://dev.frontapp.com/reference/events) topic for more information, including sorting and filtering. Required scope: `events:*:read`; Events
Get folder: Fetch a message template folder. Required scope: `message_templates:read`; Message Template Folders
Get inbox: Fetch an inbox. Required scope: `inboxes:read`; Inboxes
Get knowledge base article with content in default locale: Fetches a knowledge base article with content in the default locale. Required scope: `knowledge_bases:read`; Knowledge Base Articles
Get knowledge base article with content in specified locale: Fetches a knowledge base article with content for a given locale. Required scope: `knowledge_bases:read`; Knowledge Base Articles
Get knowledge base category content in default locale: Fetches a knowledge base category with content in the default locale. Required scope: `knowledge_bases:read`; Knowledge Base Categories
Get knowledge base category with content in specified locale: Fetches a knowledge base category with content for a given locale. Required scope: `knowledge_bases:read`; Knowledge Base Categories
Get link: Fetch a link. For more information on links, see the [Links](https://dev.frontapp.com/reference/links) topic. Required scope: `links:read`; Links
Get message: Fetch a message. > ℹ️ The HTTP Header `Accept` can be used to request the message in a different format. > By default, Front will return the documented JSON response. By requesting `message/rfc822`, the response will contain the message in the EML format (for email messages only). Required scope: `messages:read`; Messages
Get message seen status: Get the seen receipts for the given message. If no seen-by information is available, there will be a single entry for the first time the message was seen by any recipient. If seen-by information is available, there will be an entry for each recipient who has seen the message. Required scope: `messages:read`; Messages
Get message template: Fetch a message template. Required scope: `message_templates:read`; Message Templates
Get rule: Fetch a rule. Required scope: `rules:read`; Rules
Get shift: Fetch a shift. Required scope: `shifts:read`; Shifts
Get signatures: Get the given signature. Required scope: `signatures:read`; Signatures
Get tag: Fetch a tag. Required scope: `tags:read`; Tags
Get team: Fetch a team (workspace). Required scope: `teams:read`; Teams
Get teammate: Fetch a teammate. Required scope: `teammates:read`; Teammates
Get ticket status: Fetch a ticket status. Required scope: `statuses:read`; Statuses
Get time off: Fetch a time off. Required scope: `time_off:read`; Time Off
Get view: Fetch a view. Required scope: `views:read`; Views
Import message: Use this endpoint to import conversations into Front without sending data through a channel. Typical use cases include importing historical conversations or creating new conversations from non-standard sources, such as web form submissions that can't use the default Form channel (for example, forms that don't have static URLs or form providers that send email notifications after submission). Avoid using this endpoint for conversations that can be handled by a dedicated Front channel—instead, use the [Create message](https://dev.frontapp.com/reference/create-message) endpoint to send (rather than import) a new message. Required scope: `messages:write`; Messages
List account contacts: Lists the contacts associated with an Account Required scope: `contacts:read`; Accounts
List Account's custom fields: Lists the custom fields that can be attached to an Account. Required scope: `custom_fields:read`; Custom Fields
List Accounts: List the accounts of the company. Required scope: `accounts:read`; Accounts
List all company rules: List the company rules. Required scope: `rules:read`; Rules
List articles in a category: List articles in a category. Required scope: `knowledge_bases:read`; Knowledge Base Articles
List articles in a knowledge base: List articles in a knowledge base Required scope: `knowledge_bases:read`; Knowledge Base Articles
List assigned conversations: List the conversations assigned to a teammate in reverse chronological order (most recently updated first). For more advanced filtering, see the [search endpoint](https://dev.frontapp.com/reference/conversations#search-conversations). Required scope: `conversations:read`; Teammates
List categories in a knowledge base: List categories in a knowledge base. Required scope: `knowledge_bases:read`; Knowledge Base Categories
List channels: List the channels of the company. Required scope: `channels:read`; Channels
List comment mentions: List the teammates mentioned in a comment. Required scope: `teammates:read`; Comments
List company tags: List the company tags. Required scope: `tags:read`; Tags
List teammate group team inboxes: List inboxes that the teammate group has access to via its associated teams. Required scope: `inboxes:read`; Teammate groups
List teammate group teammates: List teammate group teammates. Required scope: `teammates:read`; Teammate groups
List teammate group teams: List teams added to the teammate group. Any teams added to the teammate group will automatically link public inboxes. Required scope: `teams:read`; Teammate groups
List teammate groups: List the teammate groups in the company. Required scope: `teammate_groups:read`; Teammate groups
List company ticket statuses: List the ticket statuses available for your company. Required scope: `statuses:read`; Statuses
List contact conversations: List the conversations for a contact in reverse chronological order (newest first). For more advanced filtering, see the [search endpoint](https://dev.frontapp.com/reference/conversations#search-conversations). Required scope: `conversations:read`; Contacts
List Contact's custom fields: Lists the custom fields that can be attached to a Contact. Required scope: `custom_fields:read`; Custom Fields
List contact lists: List contact lists. Required scope: `contacts:read`; Contact Lists
List contacts: List the contacts of the company. Required scope: `contacts:read`; Contacts
List contacts in contact list: List the contacts belonging to the requested contact list. Required scope: `contacts:read`; Contact Lists
List contacts in group: List the contacts belonging to the requested group. > ⚠️ Deprecated endpoint > > This endpoint has been deprecated. Please use the compatible contact list endpoints instead. > - `GET /contact_lists/{contact_list_id}/contacts`. Required scope: `contacts:read`; Contact Groups
List conversation comments: List the comments in a conversation in reverse chronological order (newest first). Required scope: `comments:read`; Comments
List Conversation's custom fields: Lists customer-managed custom fields that can be attached to a Conversation. Front-managed system fields are excluded. Required scope: `custom_fields:read`; Custom Fields
List conversation drafts: List the drafts in a conversation. Required scope: `drafts:read`; Drafts
List conversation events: List the events that occured for a conversation in reverse chronological order (newest first). The order will respect your company's [bump settings](https://help.front.com/t/y729th/customize-when-conversations-bump-up), which determine when conversations bump to the top. Required scope: `events:*:read`; Conversations
List conversation followers: List the teammates following a conversation. Required scope: `teammates:read`; Conversations
List conversation inboxes: List the inboxes in which a conversation is listed. Required scope: `inboxes:read`; Conversations
List conversation messages: List the messages in a conversation in reverse chronological order (newest first). Required scope: `messages:read`; Conversations
List conversations: List the conversations in the company in reverse chronological order (most recently updated first). The order will respect your company's [bump settings](https://help.front.com/t/y729th/customize-when-conversations-bump-up), which determine when conversations bump to the top. For more advanced filtering, see the [search endpoint](https://dev.frontapp.com/reference/conversations#search-conversations). Required scope: `conversations:read`; Conversations
List Contact's custom fields: Lists the custom fields that can be attached to a Contact. > ⚠️ Deprecated endpoint > > This endpoint has been deprecated. Please use the fully compatible `GET /contacts/custom_fields` endpoint instead. Required scope: `custom_fields:read`; Custom Fields
List events: Lists all the detailed events which occurred in the inboxes of the company ordered in reverse chronological order (newest first). Refer to the [Events](https://dev.frontapp.com/reference/events) topic for more information, including sorting and filtering. Required scope: `events:*:read`; Events
List folders: List the message template folders. Required scope: `message_templates:read`; Message Template Folders
List groups: List the contact groups. > ⚠️ Deprecated endpoint > > This endpoint has been deprecated. Please use the compatible contact list endpoints instead. > - `GET /contact_lists`. Required scope: `contacts:read`; Contact Groups
List inbox access: List the teammates with access to an inbox. Required scope: `teammates:read`; Inboxes
List inbox channels: List the channels in an inbox. Required scope: `channels:read`; Inboxes
List inbox conversations: List the conversations in an inbox. For more advanced filtering, see the [search endpoint](https://dev.frontapp.com/reference/conversations#search-conversations). Required scope: `conversations:read`; Inboxes
List Inbox's custom fields: Lists the custom fields that can be attached to an Inbox. Required scope: `custom_fields:read`; Custom Fields
List inboxes: List the inboxes of the company. Required scope: `inboxes:read`; Inboxes
List knowledge bases: List the knowledge bases of the company. Required scope: `knowledge_bases:read`; Knowledge Bases
List link conversations: List the conversations linked to a specific link. For more advanced filtering, see the [search endpoint](https://dev.frontapp.com/reference/conversations#search-conversations). For more information on links, see the [Links](https://dev.frontapp.com/reference/links) topic. Required scope: `conversations:read`; Links
List Link's custom fields: Lists the custom fields that can be attached to a Link. For more information on links, see the [Links](https://dev.frontapp.com/reference/links) topic. Required scope: `custom_fields:read`; Custom Fields
List links: List the links of the company paginated by id. Allows filtering by link type via the q.types param. These links include application objects; for more details, see the [Links](https://dev.frontapp.com/reference/links) topic. Required scope: `links:read`; Links
List message templates: List the message templates. Required scope: `message_templates:read`; Message Templates
List notes: List the notes added to a contact. Required scope: `contacts:read`; Contact Notes
List rules: List the rules of the company. Required scope: `rules:read`; Rules
List Shifts: List the shifts. Required scope: `shifts:read`; Shifts
List shift's teammates: List the teammates assigned to a shift. Required scope: `teammates:read`; Shifts
List tag children: List the children of a specific tag. Required scope: `tags:read`; Tags
List tagged conversations: List the conversations tagged with a tag. For more advanced filtering, see the [search endpoint](https://dev.frontapp.com/reference/conversations#search-conversations). Required scope: `conversations:read`; Tags
List tags: List all the tags of the company that the API token has access to, whether they be company tags, team tags, or teammate tags. Required scope: `tags:read`; Tags
List team channels: List the channels of a team (workspace). Required scope: `channels:read`; Channels
List team contact lists: List contact lists belonging to the requested team (workspace). Required scope: `contacts:read`; Contact Lists
List team contacts: List the contacts of a team (workspace). Required scope: `contacts:read`; Contacts
List team folders: List the message template folders belonging to the requested team (workspace). Required scope: `message_templates:read`; Message Template Folders
List team groups: List contact groups belonging to the requested team (workspace). > ⚠️ Deprecated endpoint > > This endpoint has been deprecated. Please use the compatible contact list endpoints instead. > - `GET /teams/{team_id}/contact_lists`. Required scope: `contacts:read`; Contact Groups
List team inboxes: List the inboxes belonging to a team (workspace). Required scope: `inboxes:read`; Inboxes
List team message templates: List the message templates belonging to the requested team (workspace). Required scope: `message_templates:read`; Message Templates
List team rules: List the rules of a team (workspace). Required scope: `rules:read`; Rules
List team Shifts: List the shifts for a team (workspace). Required scope: `shifts:read`; Shifts
List team signatures: List the signatures belonging to the given team (workspace). Required scope: `signatures:read`; Signatures
List team tags: List the tags for a team (workspace). Required scope: `tags:read`; Tags
List team time offs: List the time offs of all teammates in a team. Required scope: `time_off:read`; Time Off
List team views: List the views of a team. Required scope: `views:read`; Views
List teammate channels: List the channels of a teammate. Required scope: `channels:read`; Channels
List teammate contact lists: List the contact lists belonging to the requested teammate. Required scope: `contacts:read`; Contact Lists
List teammate contacts: List the contacts of a teammate. Required scope: `contacts:read`; Contacts
List Teammate's custom fields: Lists the custom fields that can be attached to a Teammate. Required scope: `custom_fields:read`; Custom Fields
List teammate folders: List the message template folders belonging to the requested teammate. Required scope: `message_templates:read`; Message Template Folders
List teammate groups: List the contact groups belonging to the requested teammate. > ⚠️ Deprecated endpoint > > This endpoint has been deprecated. Please use the compatible contact list endpoints instead. > - `GET /teammates/{teammate_id}/contact_lists`. Required scope: `contacts:read`; Contact Groups
List teammate inboxes: Returns list of inboxes the teammate has access to. Required scope: `inboxes:read`; Teammates
List teammate message templates: List the message templates belonging to the requested teammate. Required scope: `message_templates:read`; Message Templates
List teammate private inboxes: List the private inboxes of a teammate. Required scope: `inboxes:read`; Inboxes
List teammate rules: List the rules of a teammate. Required scope: `rules:read`; Rules
List Teammate Shifts: Lists all the shifts for the teammate. Required scope: `shifts:read`; Shifts
List teammate signatures: List the signatures belonging to the given teammate. Required scope: `signatures:read`; Signatures
List teammate tags: List the tags for a teammate. Required scope: `tags:read`; Tags
List teammate time offs: List the time offs of a teammate. Required scope: `time_off:read`; Time Off
List teammates: List the teammates in the company. Required scope: `teammates:read`; Teammates
List teams: List the teams (workspaces) in the company. Required scope: `teams:read`; Teams
List views: List the views accessible to the authenticated token. Required scope: `views:read`; Views
Mark message seen: Mark an outbound message from Front as seen. Note, the message seen route should only be called in response to an actual end-user's message-seen action. In accordance with this behavior, the route is rate limited to 10 requests per message per hour. Required scope: `messages:write`; Messages
Merge contacts: Merges the contacts specified into a single contact, deleting the merged-in contacts. If a target contact ID is supplied, the other contacts will be merged into that one. Otherwise, some contact in the contact ID list will be treated as the target contact. Merge conflicts will be resolved in the following ways: * name will prioritize manually-updated and non-private contact names * descriptions will be concatenated and separated by newlines in order from oldest to newest with the (optional) target contact's description first * all handles, groups, links, and notes will be preserved * other conflicts will use the most recently updated contact's value Required scope: `contacts:write`; Contacts
Receive custom messages: Receive a custom message in Front. This endpoint is available for custom channels **ONLY**. Required scope: `messages:write`; Messages
Remove teammate group team inboxes: Unlinks non-public inboxes from the teammate group. Required scope: `teammate_groups:write`; Teammate groups
Remove teammate group teammates: Remove teammate group teammates. Note - You cannot modify a teammate group that is managed by SCIM. Required scope: `teammate_groups:write`; Teammate groups
Remove teammate group teams: Remove teams from the teammate group. Unlinks to any associated team inboxes. Required scope: `teammate_groups:write`; Teammate groups
Remove contact from Account: Removes a list of contacts from an Account Required scope: `accounts:write`; Accounts
Remove contacts from contact list: Remove contacts from the requested contact list. Required scope: `contacts:write`; Contact Lists
Remove contacts from group: Remove contacts from the requested group. > ⚠️ Deprecated endpoint > > This endpoint has been deprecated. Please use the compatible contact list endpoints instead. > - `DELETE /contact_lists/{contact_list_id}/contacts`. Required scope: `contacts:write`; Contact Groups
Remove conversation links: Removes one or more links to a conversation. For more information on links, see the [Links](https://dev.frontapp.com/reference/links) topic. Required scope: `conversations:write`; Conversations
Remove conversation tag: Removes one or more tags to a conversation Required scope: `conversations:write`; Conversations
Remove teammates from shift: Remove teammates from a shift. Required scope: `shifts:write`; Shifts
Remove teammates from team: Remove one or more teammates from a team (workspace). Required scope: `teams:write`; Teams
Removes inbox access: Remove access of one or more teammates from an inbox. Required scope: `inboxes:write`; Inboxes
Search conversations: Search for conversations. Response will include a count of total matches and an array of conversations in descending order by last activity. See the [search syntax documentation](https://dev.frontapp.com/docs/search-1) for usage examples. **Note:** This endpoint is subject to [proportional rate limiting](https://dev.frontapp.com/docs/rate-limiting#additional-proportional-limiting) at 40% of your company's rate limit. Required scope: `conversations:read`; Conversations
Trigger application event: Triggers an event on behalf of an application. These events can trigger Front workflows, like rules. For more information, see the [developer docs](https://dev.frontapp.com/docs/application-triggers#/). Required scope: `feature:app_trigger`; Applications
Update a teammate group: Updates a teammate group. Note - You cannot modify a teammate group that is managed by SCIM. Required scope: `teammate_groups:write`; Teammate groups
Update a contact: Updates a contact. Required scope: `contacts:write`; Contacts
Update a link: Update a link. For more information on links, see the [Links](https://dev.frontapp.com/reference/links) topic. Required scope: `links:write`; Links
Update a tag: Update a tag. Required scope: `tags:write`; Tags
Update account: Updates an account. Required scope: `accounts:write`; Accounts
Update article content in default locale.: Updates an article's content in the default locale Required scope: `knowledge_bases:write`; Knowledge Base Articles
Update article content in specified locale: Updates an article's content for a given locale. Required scope: `knowledge_bases:write`; Knowledge Base Articles
Update Channel: Update a channel. Required scope: `channels:write`; Channels
Update comment: Update a comment in a [conversation](https://dev.frontapp.com/reference/conversations). Required scope: `comments:write`; Comments
Update conversation: Update a conversation. Required scope: `conversations:write`; Conversations
Update conversation assignee: Assign or unassign a conversation. Required scope: `conversations:write`; Conversations
Update conversation reminders: Snooze or unsnooze a conversation for the provided user. For private conversations, reminders can only be created and edited through the API for teammates that own the conversation. For shared conversations, reminders created and edited through the API are shared for all teammates within the shared inbox(es) that the conversation belongs to. Required scope: `conversations:write`; Conversations
Update folder: Update message template folder Required scope: `message_templates:write`; Message Template Folders
Update knowledge base category in default locale: Updates a knowledge base category in the default locale. Will republish the knowledge base if the knowledge base is currently published. Required scope: `knowledge_bases:write`; Knowledge Base Categories
Update knowledge base category in specified locale: Updates a knowledge base category for a given locale. Will republish the knowledge base if the knowledge base is currently published. Required scope: `knowledge_bases:write`; Knowledge Base Categories
Update knowledge base in default locale: Updates a knowledge base in the default locale. Will republish the knowledge base if the knowledge base is currently published. Required scope: `knowledge_bases:write`; Knowledge Bases
Update knowledge base in specified locale: Updates a knowledge base for a given locale. Will republish the knowledge base if the knowledge base is currently published. Required scope: `knowledge_bases:write`; Knowledge Bases
Update message template: Update a message template. Required scope: `message_templates:write`; Message Templates
Update shift: Update a shift. Required scope: `shifts:write`; Shifts
Update signature: Update signature Required scope: `signatures:write`; Signatures
Update teammate: Update a teammate. Required scope: `teammates:write`; Teammates
Update time off: Update a time off. Required scope: `time_off:write`; Time Off
Update view: Update a view. Required scope: `views:write`; Views
Validate channel: Asynchronously validate an SMTP channel (this endpoint is irrelevant to other channel types). When you create an SMTP channel via the API, [create a channel](https://dev.frontapp.com/reference/post_inboxes-inbox-id-channels) with type smtp and the send_as set to the needed email address. You then [configure the email provider](https://help.front.com/en/articles/2081), after which you use this endpoint to asynchronously validate the SMTP settings. Required scope: `channels:write`; Channels

FAQ

Front integration, answered

How do AI agents use Front through Open Connector?: Your user connects Front once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Front tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Front MCP server?: Yes. Open Connector can serve Front as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Front actions with credentials injected server-side.
Where do Front credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Front — keep the keys.

Open source, self-hostable, with Front credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →