More reliable MCP URLs for remote boards
Agent setup for remotely reachable projects now writes the public board address into .mcpekan/config.json. Previously a remote server advertised whatever address it had bound locally, which behind a reverse proxy is a loopback upstream such as http://127.0.0.1:3847/mcp. Repair Agent Setup copied that value verbatim into the project, so a correctly issued access token was paired with an address pointing at the developer's own machine. Coding agents then either failed to connect or reached an unrelated local MCPekan that rejected the token, producing an Unauthorized error that gave no hint the URL was the problem. Remote deployments now declare their public MCP URL explicitly and refuse to start without it, so the failure surfaces once at boot with a clear message instead of silently spreading into every project configuration.
The desktop startup sync is also more careful. It refreshes .mcpekan/config.json for local projects on every launch, and it now leaves alone any config that carries a bearer token or points at a remote host. A folder linked to a remotely hosted board keeps its connection details instead of being quietly rewritten to localhost and stripped of its credential.