Can AI agents automate Front?

Front is automatable today through the Core API. This record is the Front shared inbox and customer-communication workspace (email, SMS, chat, comments, tags, and assignments), including the vendor-hosted MCP at https://mcp.frontapp.com/mcp. It is not Zendesk, Freshdesk, Intercom, or Freshservice. The Core API host in opened examples is https://api2.frontapp.com. Callers send Authorization Bearer. Tokens come from Front settings or from OAuth 2.0 authorization-code against https://app.frontapp.com/oauth/authorize and https://app.frontapp.com/oauth/token. Public App Store integrations must use OAuth unless Front grants an exception. OAuth access tokens last about 60 minutes; refresh tokens last six months. Core API resources include conversations, messages, comments, contacts, inboxes, tags, and teammates. Conversations are created by sending a message, starting a discussion, or creating a draft. Application webhooks retry failed deliveries and always send the full event; rule webhooks can target a private inbox but do not offer the same retries. First-party MCP is open beta over Streamable HTTP. Auth is OAuth 2.1 plus PKCE. Front does not support Dynamic Client Registration; custom clients need a confidential developer app with the MCP Server feature. Codex and other DCR-only clients are incompatible. Scopes are read, write, and send. Agents inherit the authorizing teammate's inbox permissions. Official language SDKs, a general-purpose CLI, and iPaaS catalogs were not established from the opened pages. Computer-use viability is unassessed. API scores 8 and is the best path because MCP is an open-beta subset that cannot serve DCR-only clients.

Best path today: api · Overall automatability: 8/10