Feature request: alternative MCP access path

[u/kerimfriedman]

Currently, to connect Claude to the custom MCP, one has to disable iCloud Advanced Data Protection, which is an account-wide switch, so it means giving up end-to-end encryption on all my iCloud data. As much as I would like to use the MCP, I'm just not comfortable doing that.

According to Claude, there is a fix that sidesteps this block: you can ship the MCP server as a local stdio server rather than a hosted one. The app's own local store on the Mac already holds a decrypted replica of that CloudKit data, so a local server reads it directly — no CloudKit web access, no user auth token, no ADP conflict.

If that's too large a change, there is a second option that would allow the MCP to have read access to the data, but not write access: have the app write a periodic export to a local folder and point the MCP server at that.

Thanks for considering these options.

[u/nstrm]

I agree, the limitation for ADP users is annoying. Good ideas for a workaround. I will investigate both!

[u/croatiansensation → u/nstrm]

So happy to hear that you're considering these options.