Open source AI project releases and updates, past day 2026: how to plug any new MCP into a signed Mac agent in minutes

Fazm v2.4.0 shipped on 2026-04-20 with custom MCP server support. The top CHANGELOG.json entry reads verbatim, 'Added custom MCP server support via ~/.fazm/mcp-servers.json with Settings UI to add, edit, and toggle servers.' Before v2.4.0, only the five built-in MCP servers hard-coded in acp-bridge/src/index.ts:1266 were reachable. After v2.4.0, any open-source MCP server released that morning can be dropped in and used on the next conversation, without a new Fazm build.

acp-bridge/src/index.ts lines 1102-1137. The code resolves `join(homedir(), '.fazm', 'mcp-servers.json')` at line 1104, exists-checks the file at 1106, JSON.parses it at 1107-1108, iterates each entry at 1114, skips any with `cfg.enabled === false` at 1115, skips any missing `cfg.command` at 1116-1119, flattens cfg.env into an Array<{name,value}> at 1120-1125, then pushes the server onto the same servers array as the five built-ins at 1126-1132. The final emitMcpServers(servers) at line 1139 publishes the merged list to the UI.

The same format as Claude Code's mcpServers block. A top-level object where each key is a server name and each value has `command` (required string), optional `args` (string array), optional `env` (object of string to string), and optional `enabled` (boolean, defaults to true). The SettingsPage hint in /Users/matthewdi/fazm/Desktop/Sources/MainWindow/Pages/SettingsPage.swift line 1844 says this verbatim: 'Uses the same format as Claude Code. Changes take effect on next conversation.'

Both. /Users/matthewdi/fazm/Desktop/Sources/MCPServerManager.swift backs a Settings UI rendered at SettingsPage.swift lines 1810-1890 with Add, Edit, and Toggle affordances. Every UI change is serialized back to ~/.fazm/mcp-servers.json, so editing the file directly and editing through the UI are the same operation. The config file row at SettingsPage.swift:1832-1868 shows the path and an Open button that reveals the file in Finder.

No. The bridge reads ~/.fazm/mcp-servers.json on every session spin-up. Changes take effect on the next conversation you start in Fazm, not on the next app relaunch. This is important for the 'past day' release cadence: when a new open-source MCP server ships in the morning, the afternoon workflow already sees it.

For this guide it is a rolling 24-hour window anchored on Fazm v2.4.0's ship date of 2026-04-20. The 'past day' SERP for this query mixes three separate categories: (1) model weight releases on Hugging Face, (2) framework version bumps on GitHub Releases, (3) new or updated MCP servers. Only category 3 is something a consumer Mac agent can plug in same-day. That is the category this page is about.

Any command. The loader at acp-bridge/src/index.ts:1128 passes `cfg.command` and `cfg.args` straight through to the MCP server list that the ACP bridge spawns. That means `python3`, `uvx`, `npx`, `node`, `deno`, or a path to any compiled binary all work. The five built-ins already mix Swift binaries (mcp-server-macos-use, whatsapp-mcp), a Python package (google-workspace-mcp), and an npm package (@playwright/mcp). The user layer inherits the same spawn surface.

No. BUILTIN_MCP_NAMES = new Set(['fazm_tools', 'playwright', 'macos-use', 'whatsapp', 'google-workspace']) at acp-bridge/src/index.ts line 1266 is the reserved-name list. If you name a user server with one of those five, the user entry merges into the array but the built-in definition wins for collision resolution in the UI (SettingsPage.swift:1941). Everything else becomes a first-class MCP server in the same active-servers panel.

Two differences. First, Fazm is a consumer Mac app, not a developer terminal: users who cannot and do not want to install Claude Code or the Claude CLI can still point it at a new MCP server by dropping JSON into ~/.fazm. Second, Fazm's agent reads macOS accessibility APIs directly (the built-in macos-use server, compiled from the open-source mcp-server-macos-use repo), so any new MCP server stacks on top of a real screen-context layer instead of a screenshot OCR loop. That is the product angle, not a feature comparison.

Anything that speaks MCP over stdio. Recent categories: database connectors (Postgres, Redis, SQLite MCPs released on GitHub), search and retrieval (Brave Search MCP, Perplexity MCP, Exa MCP), developer tools (GitHub MCP, Linear MCP, Sentry MCP), agentic browsers beyond the pinned @playwright/mcp v0.0.68, and vertical domain MCPs (financial data, maps, legal research). Each becomes a named tool the Fazm agent can call, merged with the built-in accessibility-API toolkit.

The same way you would judge any npm, brew, or PyPI dependency. The loader does not sandbox the command; it spawns it with the env you specify under the bridge's own process tree. Read the repo, check the maintainers, pin a specific tag in your `args` rather than `latest`, and prefer `uvx --from <repo>@<sha>` over `npx <package>` for anything you have not vetted. Fazm's builtin MCPs go through the signed-bundle lifecycle; user MCPs do not.

Three greps against a Fazm desktop source tree. (1) `rg -n 'mcp-servers.json' acp-bridge/src/index.ts Desktop/Sources` returns the loader at index.ts:1104 and the manager at MCPServerManager.swift:4. (2) `rg -n 'Append user-defined MCP servers' acp-bridge/src/index.ts` returns the comment at line 1102 that opens the merge block. (3) `head CHANGELOG.json` returns the v2.4.0 entry at the top of the releases array dated 2026-04-20 with the custom-MCP line as the first change.