Muse runs in the cloud, so it cannot reach localhost on your computer. To use Mem on your computer, turn on Access Anywhere and give Muse the public HTTPS address it provides. A workspace on Nowledge Cloud already has a public address.
Common questions
Muse does not show an authorization card
Muse configures its custom MCP client through conversation. The agent must use credentials.request_api_access to show the real OAuth consent card. It must use the endpoint's actual discovery metadata and credential store. The shared skill contains the client procedure. A missing card is a setup failure; report it rather than asking for credentials in chat.
The connection fails
Use the complete public HTTPS MCP address supplied by Nowledge Mem. Keep its query unchanged. For Nowledge Cloud, the endpoint is https://cloud.nowledge.co/mcp?space_protocol=exact-v1.
For Mem running on your computer, keep Mem and Access Anywhere running. A hosted tool cannot reach localhost or a private LAN address. If a temporary address changes, update the host connection; Nowledge Link provides a stable address. Complete pairing and OAuth in the same browser profile. Never paste an API key or token into chat.
A Connect page says parameters are missing, or an address looks wrong
When an agent sets up the connection, it reads one machine-readable file from your Mem address and takes every connection address from it, so no one types the long addresses by hand. Older Mem versions do not have this file; the agent builds the same values from the standard OAuth metadata instead.
If a Connect or authorization page says parameters are missing, or an address on it looks different from your Mem address, ask the agent to rebuild the connection from /.well-known/nowledge-mem-connector and check that every address has the same host as your MCP URL. Then connect again.
Clicking Allow shows "This website is not allowed to access the local Mem server"
This is a known issue in Mem 0.10.109 and 0.10.110 when you connect to Mem on your computer through Access Anywhere: after you click Allow, the page returns a 403 browser_origin_forbidden error. Update to the latest Mem release when it is available, then connect again. Workspaces on Nowledge Cloud are not affected.
The connection works, but conversations are not saved
The host needs the sync_thread tool and explicit threads:sync permission; readback needs threads:read. Memory writes use a separate mem:write scope. Reauthorize a read-only connection with the required permissions. Verify one narrowly scoped write and read back the stored originals in the intended Space.
The setup prompt requests the full current conversation, including each assistant reply, in the same Thread. The host can save only originals it can access. A connected status alone does not prove automatic sync. The shared skill defines verification and recovery; report unavailable tools or reply access instead of claiming success.