Notion shipped 11 features in 14 days. A 6-tool agent surface reached every one of them on day zero.
Most April 2026 round-ups list what Notion shipped. This one is about the other side of the contract: when a new Notion mic button, AI chat share menu, or Workers for Agents control panel renders inside the desktop app, what does it take for a third-party Mac agent to reach it that day. The answer is a bundled binary called mcp-server-macos-use, version 1.6.0, with exactly six tools.
Every Notion April 2026 release the agent had to absorb
The framing every other April 2026 round-up skips
You can read a dozen Notion-in-April write-ups right now. They will all list the features. Voice input on the 6th, shareable AI chats on the 7th, mute on the 8th, cover art on the 9th, database tab display on the 10th, the big Notion 3.4 Part 2 drop on the 14th. Fine. That is half of the story.
The other half: most of those features have no Notion API endpoint. Voice input is a UI affordance in the desktop app. The shareable-AI-chats menu lives behind Settings, then Public pages, then Shared AI chats, in the Electron window. The Mute item shows up only in the discussion-thread context menu. The cover art picker is a UI flow. The new database tab display modes are a view-level toggle. None of those have a Create endpoint, an Update endpoint, or a Webhook payload to subscribe to.
That is fine if all you want to do is read each release tweet. But if you actually run automations against Notion on a Mac (an EA who books rooms from Notion tasks, a solo founder whose CRM lives in Notion, a research lab whose meeting notes feed a paper tracker) every release is a new question: do my workflows still reach the new feature, today, without waiting for an API or updating a tool?
For an agent that goes through Fazm, the answer was yes for every one of the 11 April releases. The reason is not magic. The reason is that the surface the agent uses to drive Notion is six tools, it has been six tools for the whole month, and the six tools work on whatever the AX tree happens to contain.
The exact 6 tools (verifiable in 30 seconds)
The bundled binary lives at Fazm.app/Contents/MacOS/mcp-server-macos-use. Speak JSON-RPC to it over stdio and it tells you what it exposes.
“Open the Fazm app bundle. Run the binary. Six tools come back. That same six reached every Notion release between April 1 and April 14, 2026.”
Fazm.app/Contents/MacOS/mcp-server-macos-use, version 1.6.0
Why every release lands cleanly: AX tree in the middle
Each new Notion control renders inside an Electron window. The macOS accessibility framework picks it up automatically and exposes it as a node in the AX tree. The 6-tool surface walks the tree and acts on whatever it finds. The agent loop sits on top of that surface.
How an April 2026 Notion release reaches a Fazm agent on day zero
The 9 lines of source that mount the surface
Plumbing the 6-tool binary into the agent loop is not a framework, not a wizard, not a configuration UI. It is a checked-in conditional in the ACP bridge that every Fazm session boots. Here it is verbatim from the public source.
No flags. No env. No version pin against Notion. The binary path resolves to the one inside the running Fazm.app bundle, and the standard MCP discovery flow surfaces the six tools to the agent. When Notion shipped voice input on April 6, the same nine lines were already in production.
Each April 2026 release, mapped to the tool that reaches it
Same six tools across the entire month. The variation is on the label and role of the AX node, not on what the agent has to do with it.
Voice input on desktop (Apr 6)
A new microphone button appears in Notion AI's prompt bar in v7.10.0. It enters the AX tree as an AXButton with an accessible label. The agent uses click_and_traverse with element="voice" or by role="AXButton" plus the label, then refresh_traversal to confirm the dictation panel opened.
Shareable AI chats (Apr 7)
Settings then Public pages then Shared AI chats. Three menu items, three click_and_traverse calls. No new tool needed.
Mute discussion replies (Apr 8)
Right-click a thread. The Mute entry shows up as an AXMenuItem. click_and_traverse with rightClick=true on the thread, then click_and_traverse with element="Mute".
Cover art collections (Apr 9)
The picker exposes each collection (Met, USDA, NMAA, Texturelabs) as a row in the AX tree. scroll_and_traverse on the picker, then click_and_traverse on the chosen image.
Database tab display (Apr 10)
A toggle for text-only, icon-only, or both. press_key_and_traverse with the menu shortcut, then click_and_traverse on the desired option.
Notion 3.4 Part 2 (Apr 14)
Workers for Agents config, Custom Agents to n8n wiring, AI Meeting Notes custom-instructions field, admin auditing controls. Each is a new view inside the same Electron window. open_application_and_traverse to get the fresh tree, then a click+type chain. The fact that the release also added eight Views API endpoints is good for server-side use; the desktop UI parts are reached the same way they were on the 6th.
What one line of the AX tree actually looks like
The tools dump the accessibility tree as plain text, one element per line. The format is exact and stable. The Mac accessibility framework guarantees the role; Notion supplies the label; the geometry comes from the rendered window.
Five lines. Five April 2026 features. The agent does not need to "see" the screen as pixels. It reads structured text where the Role tells it what kind of control to expect (a button, a menu item, a tab, a text area), the label tells it which one, and the geometry tells it where. click_and_traverse uses either the element label or the geometry. The model never guesses.
The numbers that frame this piece
The 11 is from the April 2026 Notion release pages. The 6 is from running tools/list against the bundled binary, which is currently version 1.6.0. The 9 is a literal count of lines 938 through 946 in acp-bridge/src/index.ts. The 0 is the count of Fazm point releases shipped specifically to support new Notion features in the window. There were none. There never need to be.
Three numbers to remember
Notion releases between April 1 and April 14, 2026 (most months are 4-6).
Tools exposed by mcp-server-macos-use 1.6.0. The number held across the whole April wave.
Binary version reported by the bundled SwiftMacOSServerDirect at the time of writing. Same version through the month.
Three surfaces a Mac automation can use against April-2026 Notion
Same goal (drive a workflow against Notion), three different surfaces. The trade-offs are real.
| Feature | Notion API + screenshot agents | Accessibility-tree (Fazm) |
|---|---|---|
| Reaches voice input button (Apr 6) | API: no endpoint. Vision: needs new prompt. | Yes, day zero (AXButton in tree) |
| Reaches Mute item (Apr 8) | API: no endpoint. Vision: model has to learn the menu. | Yes, day zero (AXMenuItem in tree) |
| Reaches database tab display (Apr 10) | API: no endpoint. Vision: small UI element, easy to miss. | Yes, day zero (toggle in tree) |
| Reaches Workers for Agents panel (Apr 14) | API: only the developer-facing endpoints, not the panel UI. | Yes, day zero (panel in tree) |
| Determinism on UI label match | Vision: probabilistic. API: deterministic but only on what is exposed. | Exact: AX label is structured text |
| Cost per turn | Vision: 1-2 MB image per click. API: free but limited. | One stdio call per traversal |
| Day-of-release coverage | API: when Notion ships an endpoint. Vision: when the model retrains or you re-prompt. | Yes, by construction |
| Cross-app workflows | API: Notion only. Vision: yes, but each app is a new prompt. | Yes, same surface drives any Mac app |
The day-of-release playbook (for any future Notion drop)
You do not need a Fazm update to use a feature Notion shipped this morning. You need five steps, none of which involve waiting on anything.
Open Notion through the agent
macos-use_open_application_and_traverse with identifier="Notion". The traversal returns a path to the .txt accessibility tree. Open it, read it. The new feature's UI is somewhere in there.
Find the new control by label
Grep the .txt for the feature name as a string ("Voice", "Mute", "Custom instructions", "Workers"). The line you want has the format [Role] "text" x:N y:N w:W h:H visible.
Click it by label, not pixels
macos-use_click_and_traverse with element="<label>" and pid=<notion-pid>. The tool auto-centers the click using the geometry from the tree. No coordinate math.
Chain type+enter in the same call
If the new control opens a text field (voice prompt, comment box, custom-instructions field), pass text="..." and pressKey="Return" to the same click_and_traverse call. One round trip, one tool call.
Refresh the tree to confirm state
macos-use_refresh_traversal with the same pid. Read the resulting .txt. If the panel changed ("Recording...", "Sent", a new row), you are done. If not, the tool tells you which AX node moved.
Why this keeps working
Five structural facts about the surface that explain why the 11 April releases all landed on day zero, and why the next 11 will too.
The five reasons the 6-tool surface absorbs Notion releases
- Notion's macOS app is Electron, so every rendered control becomes an AX node automatically.
- The mcp-server-macos-use surface is verbs-on-a-tree (open, click, type, press, scroll, refresh), not Notion-specific selectors.
- click_and_traverse takes element="<label>", so a new label works without code or model changes.
- Each tool returns a fresh traversal, so the agent always sees current state after acting.
- The binary lives inside Fazm.app/Contents/MacOS, so the surface ships with the app and is verifiable by anyone who downloads it.
Where Fazm sits in the April 2026 Notion picture
Fazm is the consumer-friendly Mac app for desktop automation. Not a developer framework, not a Python library, not a Chrome extension. It bundles the 6-tool accessibility binary, runs the Claude Code agent loop on top of it, and lets a normal user say "mute every Notion thread that has not had a reply in two weeks" without writing code.
Notion's April 2026 release wave matters here for one reason: every one of those 11 features is reachable from a Fazm session today, with no waiting and no setup beyond installing the app. The bundled binary is already inside the app package. The bridge already mounts it. The agent loop already picks it up. When Notion 3.4 Part 3 lands in May, the same surface will reach it.
Try the 6-tool surface against your own Notion workspace
Install Fazm, open Notion, and ask the agent to do a thing. The bundled binary handles the rest. No API key needed.
Download Fazm →Frequently asked questions
What did Notion ship in April 2026?
Eleven user-facing changes between April 1 and April 14, 2026. Apr 1: a v7.9.1 bug-fix release. Apr 6: voice input for Notion AI on desktop (v7.10.0) plus AI Meeting Notes from Command Search. Apr 7: shareable AI chat links. Apr 8: mute discussion replies. Apr 9: four new museum-sourced page cover art collections. Apr 10: customizable database tab display. Apr 14: Notion 3.4 Part 2, the largest drop of the month, including Workers for Agents, the Views API with eight endpoints, smart filters, AI Meeting Notes API access, Custom Agents to n8n, Salesforce and Box connectors, heading 4 + tab block API support, writable wiki verification, and a 28% faster initial page render. Most month-in-review posts stop at the headline features. The full count matters because it is the input to the question this page answers: how does an automation surface keep up?
How many Notion April 2026 features have an official Notion API endpoint?
A minority. The April 14 Notion 3.4 Part 2 release added the Views API (eight endpoints), heading 4 + tab block writes, smart filters with relative dates, and AI Meeting Notes pull access. That covers maybe a third of the month's surface. Voice input, shareable AI chats, mute discussions, the cover art picker, database tab display, and most of the per-app UX deltas are not exposed as API endpoints at all. They live only in the desktop app's UI.
How does Fazm reach Notion features that have no API on the day they ship?
Through the bundled mcp-server-macos-use binary, which is a stable 6-tool MCP server that operates on whatever element appears in macOS's accessibility tree. When you query its tools/list over stdio (JSON-RPC), it returns exactly six tools every time: macos-use_open_application_and_traverse, macos-use_click_and_traverse, macos-use_type_and_traverse, macos-use_press_key_and_traverse, macos-use_scroll_and_traverse, macos-use_refresh_traversal. The binary identifies as SwiftMacOSServerDirect 1.6.0. Notion is an Electron app on macOS, so a new mic button or a new Mute item enters the AX tree the instant Notion ships the release. The 6-tool surface reaches it on day one without any Fazm update.
Where in Fazm's source is mcp-server-macos-use mounted into the agent loop?
acp-bridge/src/index.ts at lines 938 to 946. The bridge checks if the macosUseBinary path inside the app bundle (Contents/MacOS/mcp-server-macos-use) exists, and if it does it pushes a server entry named macos-use into the MCP server list with no args and no env. That is the only mounting required. Every downstream Claude Code agent process picks up the six tools from the standard MCP discovery flow.
How is this different from a screenshot-based computer-use agent?
A screenshot agent sends a 1-2 MB image to a vision model and asks it to guess where to click. The model can be wrong about button positions, mistake icons, or hallucinate elements that are not on screen. mcp-server-macos-use reads the AX tree directly and returns each element as a single line in this exact shape: [Role] "text" x:N y:N w:W h:H visible. The role is one of AXButton, AXTextField, AXTextArea, AXMenuItem, AXTab, etc. When Notion ships a new control, that line shows up in the tree with the new accessible label, and the click_and_traverse tool can target it by element="label" without any model retraining. The agent operates on structured text, not pixels.
Did the April 14 Notion 3.4 Part 2 release require a Fazm update?
No. The big developer-facing deliveries (Workers for Agents, Views API, smart filters, MCP improvements, Salesforce + Box connectors) are surfaces Notion's own apps consume. The desktop UI changes (custom-instructions field for AI Meeting Notes, faster page render, new admin auditing controls) appear in the AX tree like any other view. Fazm picked them up on April 14 with the same six tools.
What is the relationship between Notion's new MCP server and Fazm's accessibility approach?
Complementary, not overlapping. Notion's new MCP improvements (April 14) let an external agent talk to a remote Notion workspace through Notion-defined tools. Fazm's mcp-server-macos-use lets the same agent talk to Notion's local desktop window through macOS-defined accessibility tools. The first one stops at what Notion exposes; the second one reaches anything the desktop app renders. A single Fazm session can use both at once because both surface as MCP servers to the same Claude Code agent loop.
Will the 6-tool surface keep working as Notion ships more updates in May?
Almost certainly. The number 6 is structural, not a snapshot. Each tool maps to one verb on a generic GUI (open, click, type, press a key, scroll, re-read the tree). New Notion features change the labels and roles on the AX nodes the agent reads, not the verbs the agent has to perform. The same was true through April 2026 (eleven feature drops, zero binary updates) and was true through Q1 2026 before that. The version line said 1.6.0 when this page was written; it has been stable across the wave.
Eleven Notion releases. Six tools. Zero updates.
The features round-ups list are real. The reason a Mac agent still reaches them on the day they ship is structural. Same binary, same six tools, every Notion release.
Try Fazm free
Comments
Public and anonymous. No signup.
Loading…