Skip to main content
GUI chat apps connect to Atlaso through a remote connector (MCP) instead of the plugins the CLI tools use. Same account, same memory — but a different way of working.

​
Adding the connector

Anywhere you see “custom connectors” (Claude Desktop and claude.ai support this), the recipe is the same:
1

Open connector settings

In Claude Desktop: Settings → Connectors → Add custom connector. On claude.ai: Settings → Connectors.
2

Name and URL

Name: Atlaso · URL: https://mcp.atlaso.ai/mcp
3

Authorize

Click Add → Connect — a browser window opens on Atlaso’s authorization page; click Authorize.
This works for any tool that speaks MCP — Zed, Cline, a client that shipped last week. See Any MCP tool; your tool shows up in Connections under its own name. ChatGPT connector support is coming — the same URL pattern will apply when it ships.

​
What you get

The connector gives the model a set of memory tools on your account: save a memory, recall memories, list recent ones, forget one. Anything it saves or recalls is the same memory your CLI tools and dashboard see.

​
The important difference from CLI tools

In GUI apps there is no automatic loop: nothing is captured or recalled unless the model decides to call a memory tool. That’s a platform constraint of connectors, not an Atlaso setting.
In practice:
  • The model often checks memory on its own when it’s clearly relevant — but not reliably every message.
  • You can always steer it: “check my Atlaso memory first” or “remember this.”
  • For the fully automatic experience — recall before every prompt, capture after every turn — use one of the CLI/IDE tools.

​
One account, one memory

A memory you save from Claude Desktop is there when Claude Code recalls on your next prompt, and vice versa — subject to the Free plan’s one-active-tool rule.