Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

Lumberroom

✓ service owner · lumberroom.cloud

by lumberroomversion 0.2.0i★ 1iRuns in the cloudOfficial site ↗
Registry namecloud.lumberroom/lumberroom

How to install

What it does

Durable shared memory for AI agents: search, write and correct facts, with per-client policy.

  • Connects Runs in the cloud
  • Account or key Sign in to the service when you connect (OAuth)
  • Category Search & AI memory

Use together with

Skills that teach the AI this kind of work; they work alongside this one

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

by google-research★ 35,6381 skills

Skill · How-to guide

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

by BigBodyCobain★ 11,6051 skills

Skill · How-to guide

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

by gosom★ 8,2361 skills

Skill · How-to guide

Why it ranks here

This one is in the “Apps that connect to AI” tab, which is ordered without stars, in this order

1. In Claude’s connector directoryNo
2. Tried by our teamNo
3. Works for Thai usersNo
4. Usage without stars20/100Popularity 0 · Freshness 12 · Still answering 8 · Likes from users +0
5. Listed on2026-11-10

Likes from users: 0 · Adds at most 5 points to the order (1 per person). It cannot be bought.

Quality: Passed 4/4 basic checks (shown, not used for ordering)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Lumberroom. Follow https://mcp.popnx.com/i/cloud-lumberroom-lumberroom.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 4/4 checks · What you ask goes through the maker’s server (mcp.lumberroom.cloud) · ✓ Commands checked Nov 20, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude · about 2 min

No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it

  1. Open Claude’s Connectors page

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. Click “Add” → “Custom” → “Web” and fill in these 2 fields

    Copy each value into the field with the same name in Claude, then click Continue

    Name · NameLumberroom
    Remote MCP server URL · Addresshttps://mcp.lumberroom.cloud/mcp

    Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add

  3. Turn it on in a chat

    +ConnectorsLumberroom

  4. Try it

    Use Lumberroom and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Lumberroom or shows a Lumberroom tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with ChatGPT, depending on your plan

Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only

  1. Open ChatGPT’s add-MCP page on the web

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. Fill in the name and address

    Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin

    Name · NameLumberroom
    Connection · Addresshttps://mcp.lumberroom.cloud/mcp
  3. Pick Lumberroom in a chat

    Start a new chat and pick Lumberroom from your plugins before typing

  4. Try it

    Use Lumberroom and tell me what you can do for me, then show me one thing

    ✓ If ChatGPT says it is using Lumberroom or shows a Lumberroom tool in the answer, you are connected

Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Claude Code · about 2 min

No key, nothing to install

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  2. Paste this command and press Enter

    claude mcp add --transport http --scope user lumberroom https://mcp.lumberroom.cloud/mcp
  3. Type /mcp in Claude Code

    You should see Lumberroom listed as connected

  4. Try it

    Use Lumberroom and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Lumberroom or shows a Lumberroom tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor · about 2 min

No key, nothing to install

  1. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  2. Open the AI chat in Cursor in Agent mode

  3. Try it

    Use Lumberroom and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Lumberroom or shows a Lumberroom tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code · about 2 min

No key, nothing to install

  1. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  2. Open the AI chat in VS Code in Agent mode

  3. Try it

    Use Lumberroom and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Lumberroom or shows a Lumberroom tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

Address for apps that connect over the web

Addresshttps://mcp.lumberroom.cloud/mcp

JSON settings are under “For developers” below

Stuck? Ask people who use Lumberroom💬 Discussion →
For developers: Terminal commands and JSON settings

Over the web

Claude Code

claude mcp add --transport http --scope user lumberroom https://mcp.lumberroom.cloud/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "lumberroom": {
      "url": "https://mcp.lumberroom.cloud/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "lumberroom": {
      "type": "http",
      "url": "https://mcp.lumberroom.cloud/mcp"
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
Not on npm/PyPI
Verified domain
✓ lumberroom.cloud
Licencei
Apache-2.0
Connection
Runs in the cloud
Transport
streamable-http
Latest versioni
0.2.0
Published to registryi
Nov 10, 2026
Code last changedi
Nov 16, 2026
Last checked
Nov 15, 2026
Maker
lumberroom
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

Related guides

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain lumberroom.cloud (the registry checks domain ownership)

  • ✓ Pass

    Still maintained

    Code last changed 4 days ago

  • – Not applicable

    Has a licence

    Not applicable: a cloud server run by the owner of lumberroom.cloud; you don't run code from the repo

  • ✓ Pass

    Endpoint responds

    Responded in 532 ms (HTTP 401)

  • ✓ Pass

    Sign-in with OAuth

    Declares OAuth sign-in, so your AI app can take you to log in

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/cloud-lumberroom-lumberroom.svg)](https://mcp.popnx.com/en/servers/cloud-lumberroom-lumberroom)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Search & AI memoryi

  • More stars than 76% of the other 6470 servers in this category
  • Published to the registry more recently than 80% of the other 6470 servers in this category
  • Basic checks equal to or better than 99% of the other 6470 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Lumberroom safe?

It passed 4 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed 4 days ago, and the latest version (0.2.0) reached the registry 10 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

OpenSEO

Keyword research, site audits, rank tracking and AI visibility for your AI agent.

by every-appWidely used★ 28.3KUpdated 6 days ago

Runs in the cloud✓ everyapp.com

Exa

Official Exa MCP for web search, content fetching, and multi-step research.

by exa-labsWidely used★ 5.2KUpdated today

Runs in the cloud✓ service owner · exa.aiTried by the PopNx team

Microsoft Learn MCP

Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.

by MicrosoftDocsWidely used★ 2KUpdated 12 months ago

Runs in the cloud✓ service owner · microsoft.comTried by the PopNx team

Docs

Search and read Empryo's documentation. Read-only, no auth, no local access.

by proxysoulGrowing★ 1.6KUpdated 2 months ago

Runs in the cloud✓ empryo.com
Compared with similar ones
This one
Lumberroom
OpenSEOExaMicrosoft Learn MCPDocsCOTAL actions (cotal.ai)
Runs whereRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoYesYesYesNoNo
Basic checks4/45/52/44/44/44/4
LicenseApache-2.0MITMITCC-BY-4.0NOASSERTIONApache-2.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Lumberroom

lumberroom.cloud

One memory that every AI tool you use can read from and write to, with you deciding what each one is allowed to see.

More videos: Lumberroom playlist · lumberroom.cloud/videos

You run seven AI surfaces. Each keeps its own memory. None of them share. You re-explain your setup to ChatGPT, then again to Claude, then again to your coding agent, and when you correct one of them the others never find out. Lumberroom holds the facts once, on infrastructure you own, and every tool reads from the same place.

Three layers, doing three different jobs:

  • Memory remembers. Fuzzy semantic recall. Commodity, kept deliberately thin and swappable.
  • Registry knows. Exact structured facts with a canonical key and provenance. A memory holds "Dana mentioned her box runs Ubuntu"; the registry holds machines.desktop.os = Ubuntu 26.04, confirmed by you, on a date, superseding an older value.
  • Policy decides. Which tool sees which facts. The layer that makes it safe to store anything worth storing.

The value is in the second and third. Full thesis: docs/prd/system-prd.md.

Claude Code, Hermes, OpenWebUI, lumberroom CLI ──── static bearer token ────┐

│ Claude.ai, Cowork, mobile, ChatGPT ── OAuth 2.1 + PKCE ───────────────┤ ▼ Caddy (auto-TLS) ──▶ lumberroom (Rust: axum + rmcp) │ ▼ Postgres 16 + pgvector (127.0.0.1)

One Rust binary, a Postgres database with pgvector, and two clients that talk to them. Ten MCP tools behind four capabilities, mounted at /mcp. A built-in OAuth 2.1 authorization server for the surfaces that need a browser, with static bearer tokens honoured beside it whatever AUTH_MODE says. Envelope encryption for private, client-side encryption for sealed. A console at /console for the decisions a person has to make.

Install the server

git clone https://github.com/lumberroom/lumberroom.git && cd lumberroom

sudo ./deploy/install.sh

That is token mode on loopback: the server binds 127.0.0.1:8787, opens no public port, and prints the command to run on your Mac. The client token is the first "token" field in the .env the installer writes (mode 600) in the clone. Add --domain and --auth-mode oauth when a browser has to reach it. The installer pulls ghcr.io/lumberroom/lumberroom-server:0.6.0 and falls back to building from this tree when the pull fails; --build-local skips the pull. It pins a version rather than tracking latest, because a memory store that upgrades itself while you sleep is not a feature.

Watch the self-host walkthrough: youtu.be/Km7CcmcsS2w.

Moved: the engine used to publish as ghcr.io/the-cybersapien/lumberroom-server. That image stays public, frozen at 0.4.0, and takes no new versions; pull ghcr.io/lumberroom/lumberroom-server instead.

Install the client

The client runs on the machine holding your transcripts and your credentials, and talks to a server you host. Four ways in, in the order most people want them.

brew install lumberroom/lumberroom/lumberroom

Installed from the old the-cybersapien/lumberroom tap? The next brew update follows the move and renames the tap. Homebrew stops trusting a tap whose owner changed, so run brew trust lumberroom/lumberroom once, or brew upgrade refuses the formula.

cargo install lumberroom

A binary, with no package manager. Four targets, macOS and Linux on arm64 and x86_64:

tag=v0.6.0; target=aarch64-apple-darwin      # or x86_64-apple-darwin,

aarch64-unknown-linux-musl, x86_64-unknown-linux-musl

base=https://github.com/lumberroom/lumberroom/releases/download/$tag curl -fsSLO "$base/lumberroom-${tag#v}-$target.tar.gz" curl -fsSL "$base/SHA256SUMS" | grep "$target.tar.gz" | shasum -a 256 -c - tar -xzf "lumberroom-${tag#v}-$target.tar.gz" && install -m 755 lumberroom ~/.local/bin/

Check the archive before you run what came out of it. Every release carries one SHA256SUMS over every asset, written by the job that collected them all.

On a machine where apt or dnf is how software arrives, the release also carries a .deb and an .rpm per architecture. Both hold the musl binary, statically linked, so neither declares a runtime dependency:

sudo dpkg -i lumberroom_0.6.0-1_amd64.deb     # or lumberroom_0.6.0-1_arm64.deb

sudo rpm -i lumberroom-0.6.0-1.x86_64.rpm # or lumberroom-0.6.0-1.aarch64.rpm

Then point it at your server:

lumberroom doctor

doctor reports the endpoint, whether your credential is accepted, and which tools it opens. It is the first command to run and the one to run when something is wrong.

To wire a Mac into Claude Code, which installs the MCP server, the session hook and the CLAUDE.md rule in one pass:

LUMBERROOM_TOKEN=<token> ./client/wire-mac.sh --url http://127.0.0.1:8787

For Hermes Agent, lumberroom-hermes is a memory provider: recall on every turn and the engine's own tools for writes. It uses lumberroom.cloud unless base_url names your own engine, which runs the same code.

Then prove the loop, which states a fact in one session and recovers it in a fresh one:

LUMBERROOM_URL=http://127.0.0.1:8787 LUMBERROOM_TOKEN=<token> ./scripts/done-when-test.sh

Back up secrets/lumberroom-kek somewhere this box does not hold. Losing it makes every private row unreadable, in the database and in every backup.

Where to go next

docs/faq.mdThe questions people actually ask: deploying, granting a client, keys, refusals
docs/managing.mdRunning a live store: approving a client, changing what it may reach, the two queues
DEPLOY.mdThe runbook: both deploy paths, the KEK, backups, troubleshooting
deploy/oauth.mdThe OAuth production path, per surface, with the consent screen
docs/permissions.mdEvery grant field, both axes, and which tools each capability opens
docs/connect-claude-code.mdWiring Claude Code on a Mac, end to end
docs/connect-claude-ai.mdThe memory rules for claude.ai, Cowork and other connector clients: instructions to paste, or a skill
docs/architecture.mdThe ports-and-adapters shape and where each part lives
docs/decisions/Why each part is shaped the way it is, one record per choice
docs/traps.mdFindings that cost real time, and what to do instead
VERIFY.mdThe gates: what each checks, how to run it, what a pass looks like
docs/benchmarks.mdEvery retrieval figure, with the run that produced it
CONTRIBUTING.mdBuilding, testing, and what a pull request needs
docs/README.mdThe full index: PRDs, phase specs, research, design

The ten tools

Every tool sits behind one grant, and src/mcp/capability.rs holds the single table that decides which. tools/list filters on it, so a model never sees a tool its credential cannot call, and the service checks the grant again on the call. Signatures are additive: they have gained arguments and never lost one.

GrantTools
Open to every authenticated clientcontext_bootstrap, memory_search, memory_write, registry_get, alias_list
mayDeletememory_forget
mayReadHistorymemory_history, registry_history
registryWriteregistry_set, alias_set

Namespace and sensitivity still apply inside every call. Full signatures and what each one does: docs/permissions.md.

possible_conflicts is what makes a correction stick. When a write lands close to an existing fact but not close enough to collapse into it, the server returns the neighbours it refused to merge, and the model calls memory_write again with supersedes. The store cannot tell a correction from a restatement; the model in the conversation is the only party that can.

Namespaces and sensitivity

  • user:me facts about you and how you work
  • project: facts scoped to one codebase
  • global facts true everywhere: infrastructure, conventions, credential locations
  • personal:* and credentials:* classify above open by default

A grant pairs a namespace glob with a sensitivity ceiling, on each of the read and write axes. {"namespace": "project:*", "max": "private"} grants every project namespace up to private. Two patterns matching one namespace resolve to the more generous ceiling.

The three levels are three different mechanisms:

  • `open` is stored in the clear, indexed lexically and semantically.
  • `private` is encrypted at rest under a per-row key and drops out of the lexical index (decision 0005).
  • `sealed` arrives encrypted by the client. The server holds no key for it and cannot read it under any circumstance.

What `private` does not protect, stated here rather than buried in a research file. The embedding stays plaintext, because there is no ANN index over ciphertext and an unsearchable level would push everything worth protecting back into open. Published inversion work recovers most of a short text from its embedding: Morris et al. report 92% exact recovery of 32-token inputs with black-box query access, a 2025 reproduction confirms it, and later work drops the need for the victim's model. Those are figures from the literature, not measurements on this system. The claim lumberroom makes is narrow and it is the one to hold it to: private protects the verbatim text of a row from whoever holds the database, and leaks its gist. It protects nothing against the live server, which decrypts to answer a search. Evidence: docs/research/encryption-and-sensitivity.md §1.

Operating it

lumberroom help is the authoritative list. One client, the Rust one, shipped as a release binary and on the Homebrew tap.

lumberroom doctor                       # connectivity, auth, readiness, tool list

lumberroom clients # registered OAuth clients, how each registered, consent state lumberroom search "how do we deploy" lumberroom write "..." --namespace user:me --tags preference lumberroom review [--source conflict,stale,proposal] [--limit N] [--days N] [--min-similarity X] [--json] lumberroom review --dates # undated facts whose own text names a day lumberroom review --registry # registry entries due for review, non-canonical keys lumberroom review --dismissed # lists the dismissed-pair ledger lumberroom review --undismiss , # removes one pair from the ledger lumberroom registry get|set|alias ... lumberroom stats [--hours 168] [--by-client] lumberroom export --obsidian ~/vault lumberroom seal --namespace credentials:aws lumberroom tools

The lumberroom Rust CLI (crates/lumberroom) carries the archive commands:

lumberroom archive export ~/store.lumber --passphrase-stdin

lumberroom archive import ~/store.lumber --passphrase-stdin --dry-run

The con

Only the beginning is shown; read the rest in the repo