Open source AI project releases, last day 2026: the MCP server layer every roundup skips
Every April 2026 roundup for this query lists model weights and framework version bumps. None covers the MCP server layer where a consumer AI agent actually plugs into your machine. Fazm v2.3.2 shipped on April 16, 2026 with five open-source AI projects bundled inside the signed app. Four of them are MCP servers. The fifth is the Agent Client Protocol runtime that wires them together. Paths, versions, and one-line file pins are below, straight from the Fazm build script.
“Five open-source project names are hard-coded in one Set at acp-bridge/src/index.ts:1266. Each maps to a compiled artifact inside Fazm.app. The build script that compiles and copies them is sixty lines of plain bash.”
acp-bridge/src/index.ts:1266 and /Users/matthewdi/fazm/build.sh:131-235
The anchor fact: five names, one Set, one build script
The whole story of the April 2026 open-source AI release surface for a consumer Mac agent lives in three files: one TypeScript line that enumerates the built-in MCPs, one package.json block that pins versions, and one bash script that compiles and copies the artifacts into the app bundle.
Of those five, `fazm_tools` is internal. The other four each map to an open-source AI project. Two compile from Swift sources under the user home directory at build time. One is a Python MCP server rsynced into Contents/Resources. One is a pinned npm package.
Two of those npm deps are the open-source AI projects the bundle depends on at the JavaScript layer. @playwright/mcp is Microsoft's browser-extension MCP server, pinned at v0.0.68. The ACP runtime is pinned at v0.29.2.
Twenty lines of bash, two compile steps, two `cp` into the app bundle. That is how an open-source Swift MCP server becomes a binary that ships inside a signed and notarized consumer app.
The five open-source AI projects shipped inside Fazm v2.3.2
One grid, five names. These are the open-source AI projects the April 2026 consumer Fazm build depends on. Each is compiled or copied into the app bundle by the build script at /Users/matthewdi/fazm/build.sh.
mcp-server-macos-use (Swift)
Native Swift MCP server that exposes macOS accessibility APIs (AXUIElement tree, AXValue read, press, type, scroll). Built with `xcrun swift build -c release` against $HOME/mcp-server-macos-use. Copied into Fazm.app/Contents/MacOS/mcp-server-macos-use at build time.
whatsapp-mcp (Swift)
Native Swift MCP server for the Catalyst WhatsApp desktop app. Same compile path as mcp-server-macos-use, but from $HOME/whatsapp-mcp-skill-macos. Registered in the bridge under the name `whatsapp`.
google-workspace-mcp (Python)
Python MCP server bundled as a relocatable uv venv under Contents/Resources/google-workspace-mcp/. PYTHONDONTWRITEBYTECODE=1 so .pyc writes cannot invalidate the signed bundle.
@playwright/mcp v0.0.68 (Node)
Browser-extension MCP server from Microsoft's Playwright project. Pinned in acp-bridge/package.json:13 and shipped as node_modules inside the app bundle.
@agentclientprotocol/claude-agent-acp v0.29.2
Agent Client Protocol runtime that stitches the MCP servers to a Claude subprocess. Pinned in acp-bridge/package.json:15. ACP is itself an open spec the Anthropic team co-maintains.
One signed bundle, four MCP servers, one ACP runtime
The ACP bridge starts a Claude subprocess and registers the four MCP servers for it. Each one is a separate open-source project with its own lifecycle upstream. The bridge is the place where they converge inside a single, code-signable Mac app.
Open-source project to bundled binary to registered MCP
How an open-source MCP server release actually reaches a user on 2026-04-16
The roundups stop at the GitHub release tag. The user on a Mac sees a Sparkle update notification. Between those two events are six concrete build-and-sign steps, all in the same file.
1. Compile mcp-server-macos-use from source
build.sh:135 runs `xcrun swift build -c release --package-path $HOME/mcp-server-macos-use`, producing a fat arm64+x86_64 binary.
2. Compile whatsapp-mcp from source
build.sh:146 runs the same Swift build against $HOME/whatsapp-mcp-skill-macos. Both binaries land next to the main Fazm executable inside Contents/MacOS/.
3. Rsync google-workspace-mcp into Contents/Resources
build.sh:205-208 rsyncs the repo, excluding .git, __pycache__, .venv, .ruff_cache, tests, and docs. Then `uv venv --relocatable` and `uv pip install --link-mode copy` materialize a self-contained Python environment.
4. Copy acp-bridge node_modules into the bundle
build.sh:189 copies the pinned @playwright/mcp and @agentclientprotocol/claude-agent-acp node_modules trees so the bundle has no runtime npm fetch.
5. Register all four under one Set of MCP names
At runtime, acp-bridge/src/index.ts:1266 enforces BUILTIN_MCP_NAMES = new Set(['fazm_tools', 'playwright', 'macos-use', 'whatsapp', 'google-workspace']). User-added MCP servers merge into the same list at lines 1102-1137.
6. Code-sign, notarize, Sparkle-update the whole bundle
Every one of these open-source binaries gets co-signed with the Fazm Developer ID, notarized by Apple, and delivered through the Sparkle update framework. That is the part the release notes of each underlying OSS repo cannot guarantee on their own.
The SERP view vs the shipping-app view
Same query, two perspectives. One lists models and tags. The other lists artifacts a user can actually run on their Mac today.
Open source AI releases, last day 2026
LLM weight drops on HuggingFace. Framework minor-version bumps. A graph of GitHub stars. A quote about agentic AI. No mention of MCP servers, bundling, code signing, or how the release transits from repo to real-user machine.
- LLM weights and framework bumps
- HuggingFace trend lines
- Benchmarks and stars
- Zero detail on the consumer distribution path
The last-day 2026 open-source AI stack, by the numbers
Five OSS projects, four MCP servers, one Set that names them, one build script that compiles and copies them. Every number here maps to a specific line in the Fazm desktop source tree.
Verify the release surface with three greps
If you distrust any of the claims on this page, run these against a Fazm desktop source tree. Three greps, one answer each, every line mapped to a real line in the source.
Roundup view vs bundled-app view, side by side
Each row is a question a user searching for open-source AI releases probably had. The SERP view answers by listing headlines. The bundled-app view answers by naming a file and a line.
| Feature | Top SERP roundup view | Bundled-app view (Fazm v2.3.2) |
|---|---|---|
| Number of OSS AI projects covered | Varies, usually dozens, none pinned to a specific user-facing binary | Five, enumerated in one Set |
| How each is distributed | Links to a GitHub release tag | Swift compile, Python uv venv, or npm-pinned node_modules, inside one signed bundle |
| Exact date of the consumer release | Usually a rolling window, rarely a specific app version | 2026-04-16 (Fazm v2.3.2) |
| Where the versions are pinned | Implicit, reader has to go check upstream | acp-bridge/package.json:13, :15 and frozen Swift checkouts |
| Code signing / notarization | Out of scope, not discussed | Every binary co-signed with Fazm Developer ID, notarized by Apple |
| Runtime registration | Out of scope | existsSync-gated push into the `servers` array at acp-bridge/src/index.ts:1049-1100 |
| Fallbacks if a binary is missing | Out of scope | Silently skipped, rest of the bundle still launches |
| Verifiable from | Upstream GitHub release notes | Three greps in a Fazm desktop source tree |
The open-source AI stack shipped into Fazm in April 2026
Every chip corresponds to a real string in acp-bridge/src/index.ts, acp-bridge/package.json, or /Users/matthewdi/fazm/build.sh.
Three reasons this is the right lens for the query
Open-source AI project releases are interesting to different readers for different reasons. For the Mac user asking this query, the interesting part is not the weight drop. It is which MCP servers their next agent update can actually use.
The distribution path is where releases stall
Compiling, code-signing, notarizing, and Sparkle-updating an open-source MCP server into a consumer app is real work. The Fazm build script shows it happening in twenty lines.
Freezing versions matters more for agents
A misbehaving MCP server can click the wrong button in a user's app. Pinning @playwright/mcp at 0.0.68 and the ACP runtime at 0.29.2 is the difference between auditable and not.
MCP server releases are user-facing
A new @playwright/mcp version changes what every downstream agent can do with a browser tab. That shows up for users as new capabilities the same week, not next quarter.
See the five open-source AI projects running on your own Mac
Fazm v2.3.2 bundles mcp-server-macos-use, whatsapp-mcp, google-workspace-mcp, and @playwright/mcp alongside the Agent Client Protocol runtime, all compiled into one signed Mac app. The easiest way to experience the April 2026 open-source AI release wave as a user is to download the consumer app the bundled them.
Download Fazm →Frequently asked questions
Which five open-source AI projects shipped inside the last Fazm build?
Four MCP servers plus the Agent Client Protocol runtime. (1) mcp-server-macos-use, a native Swift MCP server that reads macOS accessibility APIs. (2) whatsapp-mcp, a Swift MCP server for the Catalyst WhatsApp app. (3) google-workspace-mcp, a Python MCP server bundled as a relocatable uv venv under Contents/Resources. (4) @playwright/mcp v0.0.68, the browser-extension MCP server. (5) @agentclientprotocol/claude-agent-acp v0.29.2, the ACP client that stitches everything together. Names are hard-coded in one Set at acp-bridge/src/index.ts line 1266: `new Set(['fazm_tools', 'playwright', 'macos-use', 'whatsapp', 'google-workspace'])`.
What is the exact build date you are calling 'last day 2026' for this guide?
Fazm v2.3.2 shipped on 2026-04-16. The CHANGELOG entry is in /Users/matthewdi/fazm/CHANGELOG.json at the top of the `releases` array. The guide itself is published on 2026-04-18. 'Last day' in the search query is a rolling window around the most recent consumer shipment of this open-source stack, not a single calendar date.
Why does it matter that these open-source projects shipped inside a signed consumer app?
Most 'open source AI releases' coverage stops at repos and benchmarks. Getting an open-source MCP server into a notarized consumer Mac app is a different step. Each binary has to be compiled for both arm64 and x86_64, co-signed with the app's Developer ID, embedded in the Sparkle-updatable bundle, and run as a stdio MCP server under a sandboxed Node process. That transition is where most OSS AI projects stall, and it is the one the SERP roundups never describe.
Where exactly in the Fazm source tree are these binaries wired in?
Four files, three of them in acp-bridge/src/index.ts. (1) Path resolution for the two Swift binaries at lines 63-64: `join(contentsDir, 'MacOS', 'mcp-server-macos-use')` and `join(contentsDir, 'MacOS', 'whatsapp-mcp')`. (2) Python MCP path at lines 67-69 under Contents/Resources/google-workspace-mcp/. (3) MCP registration for all four at lines 1049-1100, each wrapped in existsSync so a developer build without the binary just skips it. (4) Build-time compile/copy at /Users/matthewdi/fazm/build.sh lines 131-235, which runs `xcrun swift build -c release` against `$HOME/mcp-server-macos-use` and `$HOME/whatsapp-mcp-skill-macos`, then rsyncs the Python repo and installs deps with `uv pip install --link-mode copy`.
Is mcp-server-macos-use actually open source?
Yes. It is a Swift package that uses the public MCP protocol to expose macOS AX APIs (AXUIElement, AXValue, press, type, scroll) as MCP tools. Fazm's build.sh at line 133 points to `$HOME/mcp-server-macos-use` and compiles with Swift Package Manager via `xcrun swift build -c release`. The relevant Fazm system-prompt line at Desktop/Sources/Chat/ChatPrompts.swift:59 then tells the model to route desktop-app work through `mcp__macos-use__*` tools rather than screenshot OCR.
What version of @playwright/mcp ships in Fazm v2.3.2?
@playwright/mcp v0.0.68, declared in acp-bridge/package.json line 13 alongside @agentclientprotocol/claude-agent-acp v0.29.2. The package is copied into the bundle at /Users/matthewdi/fazm/build.sh line 189 with `cp -Rf $ACP_BRIDGE_DIR/node_modules $APP_BUNDLE/Contents/Resources/acp-bridge/`, so the runtime resolves the binary through node_modules, not through a global install.
How is google-workspace-mcp packaged, and why is it different from the Swift MCPs?
google-workspace-mcp is a Python MCP server. Fazm's build.sh lines 199-235 rsync `$HOME/google_workspace_mcp` into Contents/Resources/google-workspace-mcp/, create a relocatable venv with `uv venv --python python3.12 --relocatable`, then `uv pip install --python $VENV/bin/python3 --link-mode copy $DEPS`. Because the app bundle must be code-signable and Sparkle-updatable, the bundle sets `PYTHONDONTWRITEBYTECODE=1` at acp-bridge/src/index.ts:1092 so Python cannot drop .pyc files into the signed bundle and invalidate it.
Are there any other open-source components shipping inside Fazm?
Yes, but these five are the MCP/agent layer. Fazm also ships Sparkle (auto-update framework), Highlightr (syntax highlighting), and cloudflared (pulled from GitHub releases at /Users/matthewdi/fazm/build.sh line 86). The five listed here are specifically the open-source AI/agent projects: the MCP servers and the ACP runtime that glues them to a Claude subprocess.
Why is the MCP server layer the right lens for 'open source AI releases'?
LLM weight releases are news for training labs and downstream fine-tuners. Framework releases are news for infrastructure engineers. MCP server releases are news for the end user, because an MCP server is the thing that decides what an agent can actually do on your machine. A new @playwright/mcp version changes the tool surface every ChatGPT-compatible agent sees. A new mcp-server-macos-use version changes what your Mac assistant can touch. That is the release cadence that matters to the user on the other side.
Does Fazm pin or auto-update these open-source dependencies?
Both, depending on the dep. The two Swift MCP servers are compiled from a local checkout at build time, so the Fazm .dmg you downloaded ships a specific commit of each repo, frozen. The Python google-workspace-mcp is rsynced from a local checkout with dependencies installed via `uv pip install`, also frozen. The JavaScript deps in acp-bridge/package.json are pinned via package-lock.json and shipped as node_modules inside the bundle. In other words: everything in that Fazm build is frozen at build time, no runtime network fetch.
How can I audit this myself without downloading Fazm?
Three greps against a Fazm desktop source tree reproduce every claim in this guide: `rg -n 'BUILTIN_MCP_NAMES' acp-bridge/src/index.ts` returns line 1266 with the five-name Set. `rg -n 'xcrun swift build' build.sh` returns the two compile steps at lines 135 and 146. `rg -n 'uv pip install' build.sh` returns the google-workspace-mcp install line at 216. Those three lines are the full story. Every other detail on this page flows from them.
Is Fazm itself open source?
No. The Fazm desktop app and the ACP bridge are proprietary. The five projects named here are the open-source layer Fazm bundles, sharing the same update and code-signing lifecycle as the app. The point of this guide is not that Fazm is open source, it is that Fazm is a real shipping consumer example of the open-source MCP/agent ecosystem being used in production.
What the open-source AI release cycle looks like, from a user's Mac
On 2026-04-16 Fazm v2.3.2 shipped. On 2026-04-18, a user searched for "open source ai projects releases last day 2026" and Google Search Console recorded the impression that triggered this guide. The gap between those two dates is the gap between what open-source AI actually shipped to a consumer Mac and what any roundup article happened to list.
The five projects named here are in /Users/matthewdi/fazm/acp-bridge/src/index.ts at line 1266, in /Users/matthewdi/fazm/acp-bridge/package.json at lines 13 and 15, and in /Users/matthewdi/fazm/build.sh between lines 131 and 235. Every other detail on this page is a restatement of those lines. The SERP version of the story will update when the next open-source AI release goes live. The file pins will not move.
Comments (••)
Leave a comment to see what others are saying.Public and anonymous. No signup.