loomem ← Home
Guide · 2 minutes

How to connect your Loomem

Pick your tool — the address and key from your email work in all of them. Keep that email open beside you.

The first connection may take a moment

Your Loomem "wakes up" the first time you use it — a few seconds. It's normal, whichever tool you connect from, and every time after that is instant. If a first attempt or tool scan times out, wait a few seconds and retry.

1

Open Connectors in Claude

In the Claude app go to Settings → Connectors, click the + at the top, and choose Add custom connector.

2

Add your address

Give it any Name (e.g. My Loomem). In Remote MCP server URL, paste the address from your email:

https://0000042.loomem.ai/mcp

Leave the OAuth fields empty, then click Add.

3

Sign in with your key

A small Loomem sign-in page opens. Paste the key from your email and click Authorize:

xxxx-your-key-from-the-email-xxxx

That's it — your Loomem is connected. 🎉

Encrypted at rest

Your Loomem stores everything you save under an AES-256 key unique to your instance. We're not zero-knowledge — as the operator we can read it to support you — but a stolen storage dump can't read your context.

Running a self-hosted agent? Go fully local

OpenClaw Hermes

Both speak MCP, so they can use your hosted trial too. But self-hosted agents pair best with a self-hosted Loomem — a single small binary running right beside your agent, so its memory never leaves your machine. Get the standalone version →

Check that it works

The simplest test that your assistant really knows your context.

Tell it something about yourself

Write e.g.: "Remember that I work in marketing and run the Spring project."

Then start a new conversation and ask: "What do I do?" If it answers correctly — your context works. 🙂 (On ChatGPT Pro/Plus, which is read-only, test recall of something you saved from Claude or Codex instead.)

Something not working?

Check that you pasted the address and key exactly as in the email (no spaces), and that the URL ends in /mcp. On ChatGPT, if the scan stalls, re-run Scan Tools after signing in. Still stuck? Just reply to the email.