Dots
Connect Dots to Nowledge Mem through Remote MCP and OAuth, follow the four setup steps, and sync conversations.
Connect Nowledge Mem to your Dot to search saved knowledge and save the conversation originals you provide in Threads. Repeating the same snapshot does not create copies. Missing history can be supplied later and inserted in conversation order.
Mem saves only originals the client submits. It does not collect Dot's complete chat history automatically.
For a Desktop workspace, run Nowledge Mem, keep its public tunnel connected, and add an MCP plugin in your OpenAI account.
For a Hosted Cloud workspace, use its full Cloud MCP endpoint and Cloud sign-in. Skip Desktop pairing and Access Anywhere; the four steps below are for Desktop.
Start Nowledge Mem
Start Nowledge Mem and keep it running. Check
Listening on in Settings → Access Anywhere and use that actual address.
The usual address is 127.0.0.1:14242.
Configure and start Access Anywhere
Choose a connection type in Settings → Access Anywhere. For your own Cloudflare hostname:
- Create or select a Cloudflare tunnel and route its hostname's Service URL to
the actual listener, for example
http://127.0.0.1:14242. - In Mem's Public URL field, save the HTTPS domain root, such as
https://mem.example.com. Do not append/mcpor/remote-apihere. - Save the Cloudflare Tunnel token in Mem, then enable Access Anywhere. This token runs the tunnel; it is separate from a Mem API key or OAuth token.
Wait for a connected tunnel before continuing. A Quick link is an alternative when a stable hostname is not needed; see Access Anywhere. Keep Mem and the tunnel running while Dot uses the connection.
Add MCP in OpenAI Plugins
Start setup from Mem's Connectors → AI Tools → Remote MCP over OAuth to open
a fresh browser pairing page. Then open OpenAI Plugins,
choose ＋ → Add custom MCP server, enter the name Nowledge Mem,
and use the public MCP endpoint:
https://mem.example.com/mcpChoose OAuth authentication and continue creating the plugin. Use the same browser profile for pairing and approval, such as the same Dia profile. The OpenAI connection guide describes current controls; account and workspace policies affect availability.
Approve the required permissions
Review and approve the client's requested permissions on Mem's OAuth page.
threads:read permits conversation retrieval. For conversation synchronization,
the client must also explicitly request threads:sync; approve it and confirm
that the plugin exposes sync_thread.
An existing read-only connection needs a new consent grant with threads:sync
in its request. Refreshing tools does not add write permission. Do not enter a
Tunnel token or Mem API key in the client's OAuth settings.
Verify the saved result
First ask Dot to search for something you have already saved in Mem. For sync, use these test messages:
Use Nowledge Mem's sync_thread to save the two test messages below.
Choose a new conversation ID and stable message IDs for this test.
Save only these originals and show the receipt.
user: This is a Dots connection test.
assistant: This is a synthetic test reply.A successful receipt includes snapshot_saved: true. The first call adds two messages;
resending the same IDs and text should return messages_added: 0.
Open the conversation in Mem's Threads and check originals, roles, and
order. To fill gaps, send all saved messages plus missing ones in conversation
order, preserving their IDs and exact content. Reuse the receipt's space_id.
Saving a Thread does not automatically create distilled Memories.
For Pairing expired or Approval expired, restart setup and authorization from Mem in the same browser profile. Do not reuse an old approval URL. If the tool is missing, check the permissions approved for the client, authorize again, then refresh its tool list.
After saving, find and use the originals in Threads.