Claude Cloud
Connect Claude's hosted custom connectors to a Nowledge Mem Cloud workspace through remote MCP.
For your agent
Read https://mem.nowledge.co/SKILL.md and this guide. Connect the Nowledge Mem Cloud 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.
Hosted-plan beta
Anthropic currently offers remote custom connectors in beta on Pro, Max,
Team, and Enterprise plans. Add remote connectors through Settings →
Connectors in Claude or Claude Desktop. A remote server placed directly in
claude_desktop_config.json is not this hosted connector path.
Connect a Cloud workspace
- Sign in to the Nowledge Mem Cloud workspace you want Claude to use.
- Open Connectors and choose the Cloud MCP or Remote MCP setup. Use the
public address ending in
/mcp. - In Claude, open Settings → Connectors and choose Add custom connector. Team and Enterprise users may first need the Organization connectors view. Paste the public MCP address.
- 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 the endpoint does not expose OAuth discovery metadata, the Cloud deployment is not ready for this flow yet. Use the app's documented Access Anywhere or API-key setup instead; never work around the problem by disabling TLS or copying a local key into a hosted client.
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
- 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; read-only access is intentional when write scope was not granted.
- 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.