Claude Cloud
Connect Claude's hosted custom connectors to a Nowledge Mem Cloud or App workspace through remote MCP.
For your agent
Read https://mem.nowledge.co/SKILL.md and this guide. Connect the public Nowledge Mem MCP endpoint through Claude's remote custom connector flow, approve only the requested workspace access, then verify one memory search and one scoped write. Do not use localhost, and do not claim that this connection captures Claude conversations automatically.
What this is
Claude Cloud is Claude's hosted experience. It is separate from Claude Code and Claude Desktop, which run on a user's computer and can have different connector capabilities.
Available on every Claude plan
Anthropic offers remote custom connectors on Free, Pro, Max, Team, and
Enterprise. Free accounts can add one custom connector. Add it through
Customize → Connectors in Claude; putting a remote server directly in
claude_desktop_config.json is a different, local Claude Desktop path.
Connect a Cloud or App workspace
- Choose the workspace Claude should use.
- Nowledge Mem Cloud: Connect Nowledge Mem to Claude with the Cloud name and URL prefilled.
- Mem App: open Settings → Preferences → Access Anywhere and enable a public HTTPS address. If the App shows Claude beside that address, use it for the prefilled flow. On an earlier App release, copy the address and paste it into Claude's Add custom connector form instead. Quick link works without a subscription; Plus and Max include the stable managed Nowledge Link.
- Review the prefilled connector name and full public address, keeping
?space_protocol=exact-v1for Nowledge Cloud, then confirm. If you enter it manually, use Customize → Connectors → Add custom connector. - Complete Claude's OAuth approval in the same browser session. Review the workspace and requested read/write access before approving.
- Ask Claude to search a known memory, then save one test decision to the intended Space.
If Claude cannot discover OAuth, confirm that you copied the current public
/mcp address and that the Cloud or App release serving it is up to date.
Do not work around discovery failures by disabling TLS or copying a local Mem
key into a hosted client.
Both choices are direct connections to the selected workspace. Nowledge does not proxy App MCP traffic through a shared gateway.
The install link only prefills the form. Claude still shows the name and URL for review and asks the user to approve access.
Directory status
The custom connector above works without a public directory listing. Anthropic uses the same MCP runtime for custom and directory connectors; directory review adds discovery and a branded listing, not a different data path.
Submitting the remote connector to Anthropic's directory requires a Team or Enterprise organization and directory-management access. An Admin or Owner must submit it. Nowledge Mem is not yet listed in Claude's directory, so do not describe the custom connection as an official directory install.
What is and is not shared
Claude can search and update the Mem data that the approved workspace member is allowed to access. The connector does not give Mem access to Claude's private conversation history. Use Claude's supported export, or the local Claude Code connector, when you need transcript import or automatic session capture.
Configure a durable agent identity explicitly when several Claude agents share
one workspace. A client name or source_app is provenance, not an identity
selector, and connecting a new client must not create a new Space implicitly.
If you operate an OAuth server with an explicit redirect allowlist, allow both
Claude callback origins documented by Anthropic:
https://claude.ai/api/mcp/auth_callback and
https://claude.com/api/mcp/auth_callback.
Troubleshooting
- Mem asks you to upgrade for Spaces: copy the current Cloud URL from
Connectors → AI Tools, including
?space_protocol=exact-v1, into the existing connector and reconnect. Keep your credentials and Space selection. - Claude cannot discover OAuth: confirm the exact public
/mcpaddress and check that its protected-resource metadata endpoint is deployed. - The connector can search but cannot write: review the approved write scope and the selected Space. On Team or Enterprise, an Owner may also restrict write actions for the whole organization.
- You expected automatic transcript capture: this is a remote MCP connection, not a Claude Code hook. Use a supported export or local connector.
For the local coding-agent path, see Claude Code.