> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atlaso.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Any MCP tool

> Connect any tool that speaks MCP — Zed, Cline, a client that shipped last week — with the same URL.

Atlaso isn't limited to the tools we've built integrations for. Anything that
supports MCP can reach the same memory over one URL, so a new client doesn't have
to wait for us to add it.

## Connect it

<Steps>
  <Step title="Add a new MCP server in your tool">
    Wherever your tool lists MCP servers or connectors, add one and name it
    **Atlaso**.
  </Step>

  <Step title="Use the Atlaso URL">
    ```
    https://mcp.atlaso.ai/mcp
    ```
  </Step>

  <Step title="Save and connect">
    A browser window opens — check it says **app.atlaso.ai**, then click
    **Authorize**.
  </Step>
</Steps>

Your tool appears in **Connections** under its own name. It identifies itself
when it connects, so it shows up as itself rather than as some other client.

## What you get

The tool gets Atlaso's memory tools — recall, remember, and the rest. Your model
calls them when it decides they're relevant.

That's the important difference from our built-in integrations. With Claude Code,
Cursor, Codex, OpenCode or Antigravity, we install hooks that recall **before**
every prompt and capture **after** every turn, whether or not the model thinks to
ask. Over MCP, memory is model-initiated: it works, but it's only as reliable as
the model's judgment about when to reach for it. Same trade-off as
[Claude.ai and other GUI apps](/tools/gui-apps).

If your tool is one we support natively, use [the CLI](/install) instead — you'll
get the automatic loop rather than the model-initiated one.

<Note>
  A tool connected this way counts as its own device, not as part of the machine
  you installed the CLI on. On **Free**, that matters — see
  [One active tool on Free](/account/one-active-tool).
</Note>

## Removing it

Remove the Atlaso MCP server from your tool's connector settings, then clear it
from **Connections** in the dashboard. `atlaso sync` can't do this one — it only
sees tools installed on the machine running the CLI.