Bug Report?

When I shutdown and come back I have an odd issue with MCP. Here’s what Claude reported:

The connection to Elements just dropped again, mid-diagnosis — same failure as yesterday, and this time right after I’d been querying the app successfully. Given it’s now happened twice since the app update, the new build’s automation server may be unstable; that pattern is worth passing along to Realmac. Nothing in your project was touched — I was still reading, not writing.

Found the log:

2026-09-20T15:09:28.568Z [RapidWeaver Elements] [info] Server started and connected successfully { metadata: undefined }
2026-09-20T15:09:28.662Z [RapidWeaver Elements] [error] Couldn’t start for Cowork and Code sessions. Error: Cannot reach RapidWeaver Elements at http://localhost:9712/mcp. Is the Elements app running? (Network.NWError 61) { metadata: { context: ‘shared-pool’, stack: undefined } }
2026-09-20T15:09:28.680Z [RapidWeaver Elements] [info] Message from client: method=“initialize” id=0 params { metadata: undefined }
2026-09-20T15:09:28.686Z [RapidWeaver Elements] [info] Message from server: id=0 error(code=-32001) { metadata: undefined }
2026-09-20T15:09:28.705Z [RapidWeaver Elements] [info] Client transport closed { metadata: undefined }
2026-09-20T15:09:28.705Z [RapidWeaver Elements] [info] Server transport closed (renderer released port); shutting down server { metadata: undefined }
2026-09-20T15:09:28.705Z [RapidWeaver Elements] [info] Shutting down server… { metadata: undefined }
2026-09-20T15:09:28.705Z [RapidWeaver Elements] [info] Client transport closed { metadata: undefined }
2026-09-20T15:09:28.710Z [RapidWeaver Elements] [info] Server transport closed { metadata: undefined }
2026-09-20T15:09:28.710Z [RapidWeaver Elements] [info] Client transport closed { metadata: undefined }
2026-09-20T15:09:29.008Z [RapidWeaver Elements] [error] Couldn’t start for Cowork and Code sessions. Error: Cannot reach RapidWeaver Elements at http://localhost:9712/mcp. Is the Elements app running? (Network.NWError 61) { metadata: { context: ‘shared-pool’, stack: undefined } }

Can you try connecting with another client when Claude reports this?

The only reason I ask is that Claude can be a little iffy sometimes, and report it’s an elements issue when actually the connect is still live and it’s Claude at fault.

Incidentally, I’ve noticed my connection is much more stable using Claude via Cursor.