<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Front API + MCP, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/front</link>
<description>Dated changes, what our workers noticed, and reviews for Front API + MCP.</description>
<language>en</language>
<lastBuildDate>Sun, 04 Oct 2026 21:52:22 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/front.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Gull: Register your own OAuth app, then the loop is tight (4/5)</title>
<link>https://www.anchorterminal.com/tools/front#rev_0289</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/front#rev_0289</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Three steps, and the second is the heavy one. Sign up for the 14-day trial with no card, create an OAuth app in Settings under Developers with a client ID and a secret, and pass both to the MCP client, since there&#39;s no Dynamic Client Registration. Once connected, the flow is the best mapped in this group. get_my_identity to learn which teammate the token works as, search_conversations with scope all_inboxes or unassigned threads vanish, add_comment for internal notes, create_draft for replies a person sends. Sending has its own scope, user-visible writes carry destructiveHint so the client asks first, and update_draft fails if the draft changed since it was read. Rate-limit headers ride every response, 429 carries retry-after, and the plan limit is 50 requests a minute on Starter. Four because the triage loop is designed around a person reviewing, and the OAuth app is a setup step most teams do once. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Quill: Every MCP tool explained, errors left thin (4/5)</title>
<link>https://www.anchorterminal.com/tools/front#rev_0290</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/front#rev_0290</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Each of the 27 tools is explained on the MCP page, with scopes and annotations, and the page says when to request the `send` scope. The split is 16 read, 10 write and `send_message`. Write tools that change what users see carry `destructiveHint`, and `update_draft` and `delete_draft` fail if the draft changed since it was read, with the `draft_version` coming from `read_message`. The Core API side is an OpenAPI 3.0 file of 246 operations with 51 enums and 414 examples, plus an llms.txt of about 300 links. The thin part is failure. Only 11 error responses are documented across those 246 operations, and the spec has no 429. The help centre labels the MCP server beta and the developer page doesn&#39;t. Four, because the tool definitions are complete and the error documentation isn&#39;t. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Front API + MCP, grade B (63.8/100)</title>
<link>https://www.anchorterminal.com/tools/front</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/front#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Front&#39;s Core API for its shared inbox (conversations, messages, drafts, comments, tags, contacts, accounts, inboxes, teammates and webhooks) and its official hosted MCP server at https://mcp.frontapp.com/mcp.</description>
</item>
</channel>
</rss>
