Problem
The desktop-generated MCP integration (zn mcp, no token environment variable) fails authentication for a token-protected remote workspace even though the desktop app connects successfully.
I understand from #688 that supplying ZENNOTES_REMOTE_TOKEN separately is intentional. This is an onboarding request, not a new report of that known limitation.
Request
Could Settings → MCP detect this setup and explain/configure the required authentication during installation? Ideally provide a supported secure credential handoff without copying tokens into every agent config or maintaining custom launchers.
I want one server vault across Linux, macOS, Android, Codex, and Claude Code. Linux/Android/browser edits work, but agent credential setup was unexpected and paused my migration.
Observed
- Desktop/CLI 2.53.0 on Omarchy Linux; Docker server 2.51.0.
- Generated Codex integration fails remote authentication; local MCP works.
- Explicit
ZENNOTES_REMOTE_TOKEN allowed remote MCP access and CLI reads/writes.
- Only Codex was tested end-to-end; Claude Code is part of the intended workflow.
Problem
The desktop-generated MCP integration (
zn mcp, no token environment variable) fails authentication for a token-protected remote workspace even though the desktop app connects successfully.I understand from #688 that supplying
ZENNOTES_REMOTE_TOKENseparately is intentional. This is an onboarding request, not a new report of that known limitation.Request
Could Settings → MCP detect this setup and explain/configure the required authentication during installation? Ideally provide a supported secure credential handoff without copying tokens into every agent config or maintaining custom launchers.
I want one server vault across Linux, macOS, Android, Codex, and Claude Code. Linux/Android/browser edits work, but agent credential setup was unexpected and paused my migration.
Observed
ZENNOTES_REMOTE_TOKENallowed remote MCP access and CLI reads/writes.