Bug report: Cannot connect Apple Ecosystem MCP - resource file not present in app bundle

[martinlass7]

What happened

Cannot connect Apple Ecosystem MCP connector. Ran tests with AI help. The conclusion:

Apple Ecosystem MCP connector fails because the app is trying to launch:

/Applications/Wayland.app/Contents/Resources/app.asar.unpacked/out/main/builtin-mcp-apple.mjs

but that file is not present in the Wayland Desktop 0.11.18 app bundle.

I searched the bundle with:

find "/Applications/Wayland.app" -iname "apple" -o -iname "builtin-mcp"

The only relevant results were:
builtin-mcp-concierge-diag.js
builtin-mcp-search-skills.js
builtin-mcp-image-gen.js
node_modules/run-applescript

There is no builtin-mcp-apple.mjs.

Core is updated to 0.12.26 and the Desktop override path now points correctly to /usr/local/bin/wayland-core, so this looks like a missing bundled connector script or stale connector configuration in the Desktop app.

Environment

• App: 0.11.18
• Engine: wayland-core 0.12.26
• OS: darwin x64 (23.6.0)

Diagnostics

Scheduled tasks (cron_jobs): 0
MCP servers (mcp.config): 8

• wayland-search-skills — Enabled but exposes 0 tools — it likely failed to connect or registered nothing; check its command, args, or credentials.
• wayland-concierge-diag — Enabled but exposes 0 tools — it likely failed to connect or registered nothing; check its command, args, or credentials.
• com.microsoft-playwright-mcp — Enabled but exposes 0 tools — it likely failed to connect or registered nothing; check its command, args, or credentials.
  Providers (model_registry_providers): 2
  Workspace (projects + conversations): 20
• VoicePrint, etc. — This chat is using a temporary workspace, so files it writes (e.g. "save to the local workspace") land in a throwaway directory you may not be able to find. Open it inside a project that has a workspace folder, or set one.
• We continue the novel series project. Stand by for — This chat is using a temporary workspace, so files it writes (e.g. "save to the local workspace") land in a throwaway directory you may not be able to find. Open it inside a project that has a workspace folder, or set one.
• Give me a 100-word summary of what you understand — This chat is using a temporary workspace, so files it writes (e.g. "save to the local workspace") land in a throwaway directory you may not be able to find. Open it inside a project that has a workspace folder, or set one.
• Suggest ten themes for a new multi-book series of — This chat is using a temporary workspace, so files it writes (e.g. "save to the local workspace") land in a throwaway directory you may not be able to find. Open it inside a project that has a workspace folder, or set one.
• Book blurb — This chat is using a temporary workspace, so files it writes (e.g. "save to the local workspace") land in a throwaway directory you may not be able to find. Open it inside a project that has a workspace folder, or set one.
  Config paths
• app: ~/.wayland-config
• engine: /Library/Application Support/wayland-core
  Recent errors (/Library/Logs/Wayland)

2026-06-16.log: [2026-06-17 13:10:13.177] [warn]  [wiki-auto-sync] could not persist lastSyncAt {
2026-06-16.log: err: "Error: ENOENT: no such file or directory, mkdir '/.ijfw/wiki-state'\n" +
2026-06-16.log: [2026-06-17 13:40:13.144] [warn]  [wiki-auto-sync] could not persist lastSyncAt {
2026-06-16.log: err: "Error: ENOENT: no such file or directory, mkdir '/.ijfw/wiki-state'\n" +
2026-06-16.log: [2026-06-17 14:10:13.108] [warn]  [wiki-auto-sync] could not persist lastSyncAt {
2026-06-16.log: err: "Error: ENOENT: no such file or directory, mkdir '/.ijfw/wiki-state'\n" +
2026-06-16.log: [2026-06-17 14:40:13.079] [warn]  [wiki-auto-sync] could not persist lastSyncAt {
2026-06-16.log: err: "Error: ENOENT: no such file or directory, mkdir '/.ijfw/wiki-state'\n" +

---

📎 A screenshot of the app was copied to your clipboard — paste it here (Cmd/Ctrl+V).

[FerroxLabs]

Triage: Desktop, not Core. The missing file is app.asar.unpacked/out/main/builtin-mcp-apple.mjs — a Desktop bundle artifact. Your own diagnosis is right, and the note that Core is already at 0.12.26 with the override path resolving to /usr/local/bin/wayland-core rules the engine out.

Two shapes this could be, both Desktop-side: the connector script is not in the packaged file list (so it never ships), or it shipped under a different name and the launcher's path is stale. Your find output showing three sibling builtin-mcp-* scripts present and this one absent points at the first.

Routing to the Desktop lane. Thanks for running the search and pasting the actual bundle contents — that turned this from "MCP doesn't connect" into a specific missing artifact.