April 2026 was the month MCP config left the editor and started running system-wide. The round-ups did not notice.

What every other round-up has, and what it leaves out

Read three or four of the existing pages on this question and you can almost guess the section list before you scroll. Cursor minor releases get a paragraph. Windsurf gets a paragraph. Claude Code skill hooks get a paragraph. Aider, Cline, Continue, get a paragraph each. Then a model section: Opus 4.7, GPT-5.4, Gemini 3.1 Ultra, Llama 4 Scout and Maverick, Gemma 4, DeepSeek V3.2. Then a token-pricing comparison and a short note on context windows. Then a CTA to a newsletter.

Useful, partial. The frame is the editor. The frame is wrong. Most knowledge work happens outside the editor, and the AI agent layer that operates on that surface is moving fast enough this month that it deserves its own paragraph at minimum. Here it gets the whole page, with file names and line numbers.

The specific claim: between April 3 and April 27, Fazm shipped 13 releases, two of which (v2.2.0 on April 11 and v2.4.0 on April 20) brought the dev-tool primitives MCP server config and custom OpenAI-compatible endpoint to a consumer Mac AI agent that operates on every app on the system. The MCP config file at ~/.fazm/mcp-servers.json is wire-compatible with Claude Code's mcpServers shape. That is a deliberate design choice, and it is documented in the source comment, not just in marketing.

The anchor: two config files, four fields per server, one outer wrapper

The fastest way to verify the wire-compat claim is to read the two files side by side. Per-server fields match: command, args, env, enabled. Top-level shape is a record keyed by server name. The only structural difference: Claude Code wraps the record in a mcpServers key; Fazm reads the bare record. So the migration is a JSON unwrap or a JSON wrap, depending on direction.

// ~/.claude/mcp.json (Claude Code)
// Same four fields per server, wrapped in mcpServers.
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/me/Documents"],
      "enabled": true
    },
    "linear": {
      "command": "npx",
      "args": ["-y", "@tacticlaunch/mcp-linear"],
      "env": { "LINEAR_API_KEY": "lin_api_..." },
      "enabled": true
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_..." },
      "enabled": true
    }
  }
}

If you want to see the loader yourself, the relevant span is acp-bridge/src/index.ts lines 1102 to 1137. The function reads the file, parses it as Record<string, ServerConfig>, iterates each entry, drops any with enabled: false, and pushes the rest into the servers array that goes to the Claude Agent SDK. The Swift side, Desktop/Sources/MCPServerManager.swift, is the editor for the same file from inside Settings. Both read and write the same shape.

Seven dev-tool primitives that landed in a consumer Mac agent in April

Most of these you already know from the editor side. The novelty is the host. Each item is a real changelog entry from the dates listed, not a roadmap promise.

Why this works for the consumer surface and not just the editor

The technical reason the two layers can share an MCP config file is that MCP is, by design, transport-agnostic about the host. A server speaks the protocol; whatever is on the other side of stdio is fine. The cultural reason the round-ups missed it is that the audience for round-ups is developers, and developers who write round-ups about developer tools tend to think about the editor first and the OS second. April flipped that for one specific kind of agent.

The reason Fazm in particular can run that agent across every app is that the perception layer is built on macOS accessibility APIs, not on screenshots. Accessibility APIs return structured trees: roles, values, focus state, hierarchy. They cost orders of magnitude less to query than a vision pass over a PNG, and they preserve semantics that a model can act on without a captioning step. So an MCP server that wants to read a Linear ticket the user is looking at gets the actual ticket text, not a screenshot to OCR. That is the half of the story that has nothing to do with April releases. The April releases are about the configuration plumbing.

Together, the two halves are why a developer can copy a working mcp.json from ~/.claude/ to ~/.fazm/ and have the same servers run against the entire Mac, with the same JSON shape and the same security posture.

Migration recipe, three lines of shell

For developers who already have a populated ~/.claude/mcp.json and want to try the same fleet system-wide:

mkdir -p ~/.fazm
# Unwrap the outer mcpServers key (Claude Code wraps, Fazm reads the bare record).
jq '.mcpServers' ~/.claude/mcp.json > ~/.fazm/mcp-servers.json
# Or, if your Claude Code config is already a bare record, just copy.
# cp ~/.claude/mcp.json ~/.fazm/mcp-servers.json

On next app launch (or via Settings, MCP Servers, Reload), the bridge re-reads the file at acp-bridge/src/index.ts line 1104, iterates each entry, skips any with enabled: false, and forwards the rest into the Claude Agent SDK. Tail /tmp/fazm-dev.log on a dev build (or /tmp/fazm.log on production) and look for "User MCP server loaded:" lines, one per server, on every session start.

What the dev-tool round-ups will eventually catch up to

Three things, on a guess. First, that the MCP shape is now stable enough across hosts that copy-paste between editor and OS-level agent is the default migration path, not a curiosity. Second, that release cadence on the consumer side is closing the gap with the IDE side, because the consumer side ships Sparkle binaries and not App Store review queues. Third, that the model layer (Opus 4.7, GPT-5.4, Gemini 3.1) shows up in editors and consumer agents within minutes of each other, because both consume the same SDKs.

Whether April 2026 turns out to be the inflection or just an inflection is a question for May. Either way, if the next round-up you read on this question still frames the story as IDE-only, you can read this page as the missing column.

Frequently asked questions