mmm-mcp-server 0.1.0 → 0.1.2

package/README.en.md

@@ -0,0 +1,228 @@
+# mmm-mcp-server
+
+[日本語](README.md) | English
+
+A tool that lets you read and write your own maps in Matryoshka Mind Map (a mind map / TODO app) directly from conversations with AI agents. Because it is built on the Model Context Protocol (MCP) open standard, it works with any MCP-compatible AI agent, not just Claude Desktop and Claude Code (**tested on Claude Desktop and Claude Code**; for other clients, see their documentation on how to register an MCP server).
+
+- Say "Show me my current maps" and it lists your maps.
+- Turn ideas from your conversation directly into a hierarchical mind map.
+- Just say "I finished task X" to check it off your TODO list.
+- Import long notes or Markdown straight into a map.
+
+This tool runs entirely on your computer, with no always-on server. It starts only when needed and accesses your own maps with your own login credentials (the developer cannot see your data).
+
+> **For users who installed via `git clone` before September 30, 2026**: Due to a data format migration in the app, older versions will fail when writing to maps. Please replace the registration in Step 5 below with `npx -y mmm-mcp-server` (you do not need to log in again). If you want to keep using your cloned copy, run `git pull && npm install && npm run build` in the `mmm_mcp` folder and restart your AI agent.
+
+> This guide walks you through every step, starting with how to open the terminal (the window where you type commands), so that you can follow along even if you are not used to working with a computer.
+>
+> **Supported OS**: It should work on both macOS and Windows. It runs purely on Node.js and does not depend on OS-specific features. However, **it has only been tested on real machines running macOS.** If you notice anything while trying it on Windows, please let us know via an Issue in this repository. Steps that differ by OS (opening the terminal and installing Node.js) are described separately for macOS and Windows. All other commands are the same on both.
+
+## 1. Prerequisites
+
+- A Matryoshka Mind Map account (**anonymous-only accounts cannot be used.** Make sure you can log in with Google, Apple, or an email address. You can also link one later with the "Link email address" feature in the app).
+- An MCP-compatible AI agent (tested with Claude Desktop / Claude Code; other MCP-compatible clients should generally work too).
+- Node.js (the runtime that runs the tool; you will install it in Step 3).
+
+## 2. Open the Terminal
+
+### On macOS
+
+1. Press `Command` + `Space` on your keyboard (opens Spotlight search).
+2. Type "Terminal".
+3. Click "Terminal" in the results, or press Enter.
+
+### On Windows
+
+1. Press the `Windows` key on your keyboard (opens Start menu search).
+2. Type "PowerShell".
+3. Click "Windows PowerShell" in the results, or press Enter.
+
+Once a dark (or light) window opens, you are ready. For the rest of the steps, paste the commands into this window one line at a time and press Enter (the commands themselves are the same on macOS and Windows).
+
+## 3. Install Node.js
+
+Check whether Node.js is already installed with this command:
+
+```bash
+node --version
+```
+
+If a version number of `v18` or higher is displayed (e.g., `v20.11.0`), it is already installed. If you see an error like "command not found", download the installer from:
+
+https://nodejs.org/
+
+The site shows two large buttons. Click the one labeled **"LTS"** to download (the `.pkg` installer for macOS or the `.msi` installer for Windows is chosen automatically for your OS). Double-click the downloaded file and follow the on-screen instructions (on macOS: "Continue" → "Agree" → "Install"; on Windows: "Next" → "I accept..." → "Install").
+
+When the installation is finished, go back to the terminal and check again:
+
+```bash
+node --version
+```
+
+## 4. Log In
+
+Choose one of the following three options based on how you usually log in to the Matryoshka Mind Map app. **None of these methods require any setup on your part beforehand.** The first run downloads the tool, so it may take a moment.
+
+### If you log in with Google
+
+```bash
+npx -y -p mmm-mcp-server mmm-login login --method google
+```
+
+Your browser opens automatically; log in with the Google account you usually use.
+
+### If you log in with Apple
+
+```bash
+npx -y -p mmm-mcp-server mmm-login login --method apple
+```
+
+Your browser opens automatically; log in with your Apple ID.
+
+### If you log in with an email address and password
+
+```bash
+npx -y -p mmm-mcp-server mmm-login login --method email
+```
+
+You will be asked for your email address and password (the password is not shown on screen).
+
+> **If you get a "wrong password" error**, it does not necessarily mean you mistyped your password. If your account signs in to the app with Google or Apple and has no email/password credentials at all, you get the same error. If that may be the case, try the "Google" or "Apple" steps above.
+
+Once you have logged in, you do not need to log in again each time (your credentials are stored only on your computer, in a form that only you can read).
+
+```bash
+npx -y -p mmm-mcp-server mmm-login status
+```
+
+shows your login status. To log out:
+
+```bash
+npx -y -p mmm-mcp-server mmm-login logout
+```
+
+## 5. Register It with Your AI Agent
+
+Below are the instructions for Claude Desktop and Claude Code, which have been tested. If you use another MCP-compatible client (e.g., Codex), in most cases you only need to register the server launch command (`npx -y mmm-mcp-server`) in that client's MCP server settings. See your client's documentation for the exact steps.
+
+### Claude Code
+
+```bash
+claude mcp add mmm -- npx -y mmm-mcp-server
+```
+
+### Claude Desktop
+
+Open the Claude Desktop configuration file (`claude_desktop_config.json`) and add the following under `mcpServers`:
+
+```json
+{
+  "mcpServers": {
+    "mmm": {
+      "command": "npx",
+      "args": ["-y", "mmm-mcp-server"]
+    }
+  }
+}
+```
+
+Save the file and restart Claude Desktop.
+
+## 6. Try It Out
+
+Try talking to your AI agent like this:
+
+- "Show me my Matryoshka maps."
+- "Add a task called [task] to the [map name] map."
+- "I finished the [task] task in the [map name] map."
+- "I'll paste my notes in Markdown; import them into the [map name] map."
+
+**Only the first time the contents of a map (the element text) are read**, the tool asks for your permission before returning the actual contents. This is out of consideration for personal information that the contents may contain.
+
+Instead of the contents, the tool returns only an instruction: "confirm directly with the user, then call again with `confirmed: true`." This is best-effort: the server has no way to verify whether the agent actually asked you, so whether the confirmation happens properly depends on the AI agent you use. Once confirmed, the same map is not confirmed again while that server is running (roughly one conversation).
+
+(Previously, MCP's standard confirmation dialog, "elicitation", was also used to enforce this. However, some clients advertised support without actually showing a dialog, so contents became unreadable without the user ever seeing a confirmation screen. It was removed on 2026-09-03 in favor of the approach above.)
+
+## Keeping Your Maps Tidy
+
+Letting an AI agent write your maps is convenient, but left alone the maps tend to become hard to read. Paste the following into the instruction file your AI agent loads every time (for Claude Code, `~/.claude/CLAUDE.md`) to keep the writing style consistent:
+
+```markdown
+## How to write in mmm
+
+- Keep each element short enough to read in one line. Do not pack in explanations.
+  If you want to keep reasons or notes, put them one level down as child elements.
+- Put a URL in its own element. Do not mix it with text like "Docs here: https://...".
+  Create an element named "Docs" and put only the URL as its child.
+- Order reminder items chronologically. Name them by when to do them, such as
+  "Right after release", "In 2 weeks", or "When X happens".
+```
+
+The reasons:
+
+- **One line per element**: Matryoshka shows elements nested inside each other, so long elements hurt readability and lose the benefit of drilling down through the hierarchy.
+- **Do not mix URLs with text**: A URL in the same element as other text is not treated as a link in the app, so tapping it does nothing.
+- **Chronological order**: Compared with ordering by task name, checking items off in order makes it easier to notice anything you missed.
+
+## Troubleshooting
+
+| Symptom | Cause / Solution |
+|---|---|
+| `node --version` says "command not found" | Node.js from Step 3 is not installed yet. After installing, close the terminal and open it again. |
+| "Wrong password" when logging in | See the note in Step 4. Try logging in with Google or Apple instead. |
+| The agent does not operate on your maps when asked | Check that the registration in Step 5 is correct. Claude Desktop needs a restart after registration. |
+| The agent will not show map contents / stops at the confirmation | Check that you answered "yes" when asked for permission to read. |
+| The AI cannot load a large map | With several hundred elements or more, the `list_elements` response gets large and may not fit in one go. Some AI agents handle this by saving it to a file and reading only the parts they need. If it happens often, split the map (swiping left on a top-level element turns it and everything under it into a separate map). |
+
+## Advanced Example: Recording Tasks per Folder Automatically
+
+What follows is **just one example of how it can be used**. It is not a standard workflow recommended for everyone, but shows what becomes possible with this kind of setup. Feel free to ignore it if it does not suit you.
+
+**Goal**: Pair each folder (project) you work on in Claude Code with a map of the same name, and have the AI agent record and update tasks that come up during work in that map in real time, without asking.
+
+> Setting (2) below uses Claude Code's "global CLAUDE.md", an instruction file that is always loaded. If your AI agent has a similar feature for instructions loaded every time, the same idea should apply.
+
+### Setup
+
+**(1) Re-register the mmm server so it is available in every folder**
+
+When registering with Claude Code in Step 5, the `mmm` tool is only available in the current folder by default. To use it no matter which folder you start `claude` in, register it with `--scope user`:
+
+```bash
+claude mcp add mmm --scope user -- npx -y mmm-mcp-server
+```
+
+**(2) Write the workflow rules in your global CLAUDE.md (`~/.claude/CLAUDE.md`)**
+
+For example, add something like this:
+
+```markdown
+## Task management with mmm
+
+Record tasks that come up in the working folder in mmm (the Matryoshka Mind Map
+integration) and manage them in real time.
+
+- Use the working folder name as the map title.
+- Check with list_maps whether a map with the same name exists. If not, create it
+  right away with create_map(title=folder name, isTodo=true) without confirming
+  the title (confirmation is not required for this workflow only).
+- Calling list_elements to see existing tasks asks for confirmation only the first
+  time the map is read in that process. After that, add and update tasks in real
+  time with auto_structure_thought / update_task_status.
+```
+
+### Why this works
+
+- `create_map` takes the title directly as an argument; "confirm in the conversation before calling" is only a recommended behavior for AI agents written in the tool description. A more specific instruction in CLAUDE.md takes priority, so maps can be created automatically without confirmation.
+- Only `list_elements`, which reads map contents, has confirmation enforced on the server side out of consideration for confidential information (see "Try It Out" above). This does not change with the per-folder workflow: confirmation happens once, the first time a map is read in that process.
+
+### Caveats
+
+- Maps are created automatically for every folder, so work-log style maps will mix in with your carefully curated mind maps. Some people may find this cluttered. Adjust it to suit you, for example by using a separate account or limiting it to certain folders.
+- Skipping confirmation for `create_map` applies only when you spell out this workflow in your own CLAUDE.md. Without any setup, the agent confirms in the conversation before creating a map, as usual.
+
+## About This Tool
+
+- Your login credentials (refresh token) are stored only on your computer (macOS: `~/.config/mmm-mcp/credentials.json`, Windows: `C:\Users\<username>\.config\mmm-mcp\credentials.json`) and are never sent anywhere else.
+- Your map contents are read from and written to your Firebase account directly, without going through any third-party server, including the developer's (only when logging in with Apple, the last step of login goes through a signing-only relay server, but your map contents never pass through it).
+- There is no always-running process; it runs only while you are in a conversation with your AI agent.

package/README.md

@@ -1,5 +1,7 @@
 # mmm-mcp-server
 
+日本語 | [English](README.en.md)
+
 Matryoshka Mind Map（マトリョシカ、マインドマップ／TODOアプリ）の自分のマップを、
 AIエージェントとの会話から直接読み書きできるようにするツールです。MCP
 （Model Context Protocol）という共通規格に対応したツールなので、Claude
@@ -16,15 +18,17 @@ Desktop・Claude Codeに限らず、MCPに対応したAIエージェントであ
 起動し、あなた自身のログイン情報であなた自身のマップにアクセスします（開発者側は
 あなたのデータを見ることができません）。
 
-> **2026年9月30日より前にダウンロードした方へ**: アプリ側のデータ形式の切り替えに
-> 伴い、古い版ではマップへの書き込みが失敗するようになります。`mmm_mcp` フォルダで
-> `git pull && npm run build` を実行し、AIエージェントを再起動してください。
+> **2026年9月30日より前に `git clone` で導入した方へ**: アプリ側のデータ形式の
+> 切り替えに伴い、古い版ではマップへの書き込みが失敗するようになります。下の手順5の
+> 登録を `npx -y mmm-mcp-server` に置き換えてください（ログインし直す必要はありません）。
+> clone したまま使い続ける場合は、`mmm_mcp` フォルダで `git pull && npm install && npm run build`
+> を実行してからAIエージェントを再起動してください。
 
 > このページは、ある程度パソコン操作に慣れていない方でも迷わず進められるよう、
 > ターミナル（コマンドを打つ画面）の開き方から順に説明しています。
 >
-> **対応OS**: macOS・Windowsの両方で動作するはずです。Node.jsとgitだけで
-> 動くツールで、OS固有の機能には依存していません。ただし**実機での動作
+> **対応OS**: macOS・Windowsの両方で動作するはずです。Node.jsだけで動く
+> ツールで、OS固有の機能には依存していません。ただし**実機での動作
 > 確認はmacOSでのみ行っています。** Windowsで試して気づいた点があれば、
 > このリポジトリのIssueで教えてください。手順のうち、操作方法がOSで
 > 異なる箇所（ターミナルの開き方・Node.jsのインストール）はmacOS/Windows
@@ -85,42 +89,16 @@ https://nodejs.org/
 node --version
 ```
 
-## 4. mmm-mcp-serverをダウンロードする
-
-```bash
-git clone https://github.com/nhorie-canal/mmm_mcp.git
-```
-
-コマンドの実行が終わったら、作られたフォルダに移動します。
-
-```bash
-cd mmm_mcp
-```
-
-## 5. セットアップする
-
-必要な部品を取り込みます（少し時間がかかります）。
-
-```bash
-npm install
-```
-
-続けて、使える状態にビルドします。
-
-```bash
-npm run build
-```
-
-## 6. ログインする
+## 4. ログインする
 
 Matryoshka Mind Mapアプリで普段どのログイン方法を使っているかに合わせて、
 次の3つから選んでください。**いずれの方法も、あなた自身が事前に何かを準備する
-必要はありません。**
+必要はありません。** 初回はツールのダウンロードが入るので、少し時間がかかります。
 
 ### Googleでログインしている場合
 
 ```bash
-node dist/bin/login.js login --method google
+npx -y -p mmm-mcp-server mmm-login login --method google
 ```
 
 ブラウザが自動で開くので、いつも使っているGoogleアカウントでログインします。
@@ -128,7 +106,7 @@ node dist/bin/login.js login --method google
 ### Appleでログインしている場合
 
 ```bash
-node dist/bin/login.js login --method apple
+npx -y -p mmm-mcp-server mmm-login login --method apple
 ```
 
 こちらもブラウザが自動で開くので、Apple IDでログインします。
@@ -136,7 +114,7 @@ node dist/bin/login.js login --method apple
 ### メールアドレスとパスワードでログインしている場合
 
 ```bash
-node dist/bin/login.js login --method email
+npx -y -p mmm-mcp-server mmm-login login --method email
 ```
 
 メールアドレスとパスワードを聞かれるので入力してください（パスワードは
@@ -153,37 +131,27 @@ node dist/bin/login.js login --method email
 あなたのパソコンの中だけに、あなた以外読めない形で保存されます）。
 
 ```bash
-node dist/bin/login.js status
+npx -y -p mmm-mcp-server mmm-login status
 ```
 
 でログイン状態を確認できます。ログアウトしたい場合は次のコマンドです。
 
 ```bash
-node dist/bin/login.js logout
+npx -y -p mmm-mcp-server mmm-login logout
 ```
 
-## 7. AIエージェントにMatryoshkaを教える
+## 5. AIエージェントにMatryoshkaを教える
 
 ここでは動作確認済みのClaude Desktop / Claude Codeへの登録方法を示します。
 他のMCP対応クライアント（例: Codexなど）を使っている場合も、多くは同じように
-「サーバーを起動するコマンド」（`node <mmm_mcpのパス>/dist/src/server.js`）を
-そのクライアントのMCPサーバー設定に登録するだけで使えるはずです。具体的な
-登録方法はお使いのクライアントのドキュメントを確認してください。
-
-このステップで、あなたが今どこのフォルダにいるかによって次のコマンドの一部が
-変わります。次のコマンドで今いる場所（絶対パス）を確認してください。
-
-```bash
-pwd
-```
-
-表示された場所（例: `/Users/あなたの名前/mmm_mcp`）を、以下の
-`<mmm_mcpのパス>`の部分に置き換えて使います。
+「サーバーを起動するコマンド」（`npx -y mmm-mcp-server`）をそのクライアントの
+MCPサーバー設定に登録するだけで使えるはずです。具体的な登録方法はお使いの
+クライアントのドキュメントを確認してください。
 
 ### Claude Codeを使っている場合
 
 ```bash
-claude mcp add mmm -- node <mmm_mcpのパス>/dist/src/server.js
+claude mcp add mmm -- npx -y mmm-mcp-server
 ```
 
 ### Claude Desktopを使っている場合
@@ -195,8 +163,8 @@ Claude Desktopの設定ファイル（`claude_desktop_config.json`）を開き
 {
   "mcpServers": {
     "mmm": {
-      "command": "node",
-      "args": ["<mmm_mcpのパス>/dist/src/server.js"]
+      "command": "npx",
+      "args": ["-y", "mmm-mcp-server"]
     }
   }
 }
@@ -204,7 +172,7 @@ Claude Desktopの設定ファイル（`claude_desktop_config.json`）を開き
 
 保存したらClaude Desktopを再起動してください。
 
-## 8. 使ってみる
+## 6. 使ってみる
 
 AIエージェントとの会話で、次のように話しかけてみてください。
 
@@ -260,8 +228,8 @@ AIエージェントに任せると楽な反面、そのままだと読みにく
 | 症状 | 原因・対処 |
 |---|---|
 | `node --version`が「command not found」になる | 手順3のNode.jsインストールがまだ。インストール後、ターミナルを一度閉じて開き直す |
-| ログイン時に「パスワードが違います」と出る | 手順6の補足を参照。Google/Appleでログインし直してみる |
-| 話しかけてもマップ操作をしてくれない | 手順7の登録が正しいか確認する。Claude Desktopは登録後に再起動が必要 |
+| ログイン時に「パスワードが違います」と出る | 手順4の補足を参照。Google/Appleでログインし直してみる |
+| 話しかけてもマップ操作をしてくれない | 手順5の登録が正しいか確認する。Claude Desktopは登録後に再起動が必要 |
 | マップの中身を教えてくれない・確認だけで止まる | 「読んでいいですか」の確認に「はい」と答えているか確認する |
 | 大きなマップをAIが読み込めない | 要素が数百を超えると`list_elements`の応答が大きくなり、一度に受け取れないことがある。AIエージェントによっては、いったんファイルに保存して必要な部分だけ読む形で対応する。頻繁に起きるならマップを分ける（最上位の要素を左スワイプすると、配下ごと独立したマップになる） |
 
@@ -284,12 +252,12 @@ AIエージェントに任せると楽な反面、そのままだと読みにく
 
 **(1) mmmサーバーを全フォルダ共通で使えるように登録し直す**
 
-手順7でClaude Codeに登録するとき、そのままだと今いるフォルダでしか
+手順5でClaude Codeに登録するとき、そのままだと今いるフォルダでしか
 `mmm`ツールが使えません。どのフォルダで`claude`を起動しても使えるように
 するには、`--scope user`を付けて登録します。
 
 ```bash
-claude mcp add mmm --scope user -- node <mmm_mcpのパス>/dist/src/server.js
+claude mcp add mmm --scope user -- npx -y mmm-mcp-server
 ```
 
 **(2) グローバルのCLAUDE.md（`~/.claude/CLAUDE.md`）に運用ルールを書く**

package/dist/src/domain/levels.js

@@ -8,7 +8,9 @@
 // そのまま兄弟順。子を持つ要素だけドキュメントが存在する(無ければ葉)。
 //
 // MCPは「新形式のみ対応」(移行ロジックはDart側だけに持たせる)。levels/root
-// が無いマップに対する操作は、アプリで一度開いてもらうよう案内して止める。
+// が無いマップに対する操作は、切替前(bodiesとlevelsの両方へ書く間)だけ、
+// アプリで一度開いてもらうよう案内して止める。切替後は空のマップとして扱う
+// (levelsMode.tsのreadLevelsSnapshot)。
 export class LevelsNotInitializedError extends Error {
     constructor(title) {
         super(`「${title}」はまだ新形式(levels)のデータがありません。` +

package/dist/src/domain/levelsMode.js

@@ -9,16 +9,17 @@
 // アプリで足した要素が見つからず、bodiesを読み取り専用にするルールの適用後は
 // コミットごと失敗する。呼び出しのたびに読み直すので、MCPサーバーを
 // 再起動しなくても切替に追従する。
-import { LevelsNotInitializedError } from "./levels.js";
 import { levelsSnapshotFromDocs } from "./levelsOps.js";
 export async function isLevelsOnly(client) {
     const config = await client.getDocument("config/app");
     return config?.data.migrationEnabled !== false;
 }
-/** levels全件を読む。levels/rootが無ければ、アプリで開いてもらうよう案内して止める。 */
-export async function readLevelsSnapshot(client, levelsPath, mapTitle) {
-    const snapshot = levelsSnapshotFromDocs(await client.listDocuments(levelsPath));
-    if (!snapshot.has("root"))
-        throw new LevelsNotInitializedError(mapTitle);
-    return snapshot;
+/**
+ * levels全件を読む。levels/rootが無いマップは空のマップとして扱う
+ * (rootへの最初の書き込みは、存在しないことを前提条件にした新規作成になる)。
+ * 切替後はアプリでマップを開いてもrootが作られないので、「アプリで開いて」と
+ * 止めると中身の無い古いマップへ永久に書き込めなくなる。
+ */
+export async function readLevelsSnapshot(client, levelsPath) {
+    return levelsSnapshotFromDocs(await client.listDocuments(levelsPath));
 }

package/dist/src/server.js

@@ -12,7 +12,7 @@ import { registerDeleteElements } from "./tools/deleteElements.js";
 import { registerMoveElement } from "./tools/moveElement.js";
 const server = new McpServer({
     name: "matryoshka-mindmap",
-    version: "0.1.0",
+    version: "0.1.2",
 }, {
     instructions: "このサーバーはリアルタイム同期を行わない。各ツールは呼び出された瞬間の" +
         "Firestoreの状態を返すだけで、アプリ側でユーザーが直接行った変更は" +

package/dist/src/tools/autoStructureThought.js

@@ -35,7 +35,7 @@ export function registerAutoStructureThought(server) {
         if (await isLevelsOnly(client)) {
             let levelsPathResult = "";
             await client.runOptimistic(async () => {
-                const snapshot = await readLevelsSnapshot(client, levelsPath, map.header.title);
+                const snapshot = await readLevelsSnapshot(client, levelsPath);
                 if (targetParentId !== null && !locateInLevels(snapshot, targetParentId)) {
                     throw new Error(`parentElementId(${targetParentId})がこのマップに見つかりません。list_elementsで確認してください。`);
                 }

package/dist/src/tools/deleteElements.js

@@ -23,10 +23,14 @@ export function registerDeleteElements(server) {
         assertCanEditMap(map, session);
         const levelsPath = levelsPathOf(map);
         const bodiesPath = bodiesPathOf(map);
-        assertLevelsRootExists(await levelsDocExists(client, levelsPath, "root"), map.header.title);
-        if (await isLevelsOnly(client)) {
+        // 切替後はrootが無いマップを空のマップとして扱うので、この確認は切替前だけ。
+        const levelsOnly = await isLevelsOnly(client);
+        if (!levelsOnly) {
+            assertLevelsRootExists(await levelsDocExists(client, levelsPath, "root"), map.header.title);
+        }
+        if (levelsOnly) {
             if (confirmed !== true) {
-                const snapshot = await readLevelsSnapshot(client, levelsPath, map.header.title);
+                const snapshot = await readLevelsSnapshot(client, levelsPath);
                 const allTargets = new Set();
                 const targets = [];
                 for (const elementId of elementIds) {
@@ -61,7 +65,7 @@ export function registerDeleteElements(server) {
             let levelsTotal = 0;
             await client.runOptimistic(async () => {
                 levelsDeleted.length = 0;
-                const snapshot = await readLevelsSnapshot(client, levelsPath, map.header.title);
+                const snapshot = await readLevelsSnapshot(client, levelsPath);
                 for (const elementId of elementIds) {
                     if (!locateInLevels(snapshot, elementId))
                         continue; // 既に削除済み(リトライ時など)

package/dist/src/tools/editElement.js

@@ -21,7 +21,7 @@ export function registerEditElement(server) {
         if (await isLevelsOnly(client)) {
             let levelsPathResult = null;
             await client.runOptimistic(async () => {
-                const snapshot = await readLevelsSnapshot(client, levelsPath, map.header.title);
+                const snapshot = await readLevelsSnapshot(client, levelsPath);
                 const { writes, found } = buildLevelsPatchWrites(levelsPath, snapshot, [
                     { elementId, patch: { detail } },
                 ]);

package/dist/src/tools/importMarkdownContext.js

@@ -35,7 +35,7 @@ export function registerImportMarkdownContext(server) {
         if (await isLevelsOnly(client)) {
             let levelsPathResult = "";
             await client.runOptimistic(async () => {
-                const snapshot = await readLevelsSnapshot(client, levelsPath, map.header.title);
+                const snapshot = await readLevelsSnapshot(client, levelsPath);
                 if (targetParentId !== null && !locateInLevels(snapshot, targetParentId)) {
                     throw new Error(`parentElementId(${targetParentId})がこのマップに見つかりません。list_elementsで確認してください。`);
                 }

package/dist/src/tools/listElements.js

@@ -1,6 +1,7 @@
 import { z } from "zod";
 import { getContext } from "../mcpContext.js";
 import { resolveMap, levelsPathOf } from "../domain/mapResolver.js";
+import { isLevelsOnly } from "../domain/levelsMode.js";
 import { assertLevelsInitialized, buildTreeFromLevels, readAllLevelDocs, } from "../domain/levels.js";
 // ElementNodeの`done`を`checked`という名前で公開する(仕様書の用語に合わせる)。
 function toChecked(nodes) {
@@ -78,7 +79,11 @@ export function registerListElements(server) {
             }
         }
         const levelsById = await readAllLevelDocs(client, levelsPathOf(map));
-        assertLevelsInitialized(levelsById, map.header.title);
+        // 切替前はrootが無ければ未移行(bodiesに中身があり得る)なので止める。
+        // 切替後はアプリで開いてもrootが作られないので、空のマップとして返す。
+        if (!(await isLevelsOnly(client))) {
+            assertLevelsInitialized(levelsById, map.header.title);
+        }
         const tree = buildTreeFromLevels(levelsById);
         return {
             content: [

package/dist/src/tools/moveElement.js

@@ -25,17 +25,21 @@ export function registerMoveElement(server) {
         assertCanEditMap(map, session);
         const levelsPath = levelsPathOf(map);
         const bodiesPath = bodiesPathOf(map);
-        assertLevelsRootExists(await levelsDocExists(client, levelsPath, "root"), map.header.title);
+        // 切替後はrootが無いマップを空のマップとして扱うので、この確認は切替前だけ。
+        const levelsOnly = await isLevelsOnly(client);
+        if (!levelsOnly) {
+            assertLevelsRootExists(await levelsDocExists(client, levelsPath, "root"), map.header.title);
+        }
         if (elementId === newParentElementId) {
             throw new Error("要素を自分自身の子にすることはできません。");
         }
         if (elementId === afterElementId) {
             throw new Error("afterElementIdにelementId自身は指定できません。");
         }
-        if (await isLevelsOnly(client)) {
+        if (levelsOnly) {
             let levelsPathResult = null;
             await client.runOptimistic(async () => {
-                const snapshot = await readLevelsSnapshot(client, levelsPath, map.header.title);
+                const snapshot = await readLevelsSnapshot(client, levelsPath);
                 if (afterElementId !== null && !locateInLevels(snapshot, afterElementId)) {
                     throw new Error(`afterElementId(${afterElementId})がこのマップに見つかりません。`);
                 }

package/dist/src/tools/updateTaskStatus.js

@@ -30,7 +30,7 @@ export function registerUpdateTaskStatus(server) {
         if (await isLevelsOnly(client)) {
             let levelsResults = [];
             await client.runOptimistic(async () => {
-                const snapshot = await readLevelsSnapshot(client, levelsPath, map.header.title);
+                const snapshot = await readLevelsSnapshot(client, levelsPath);
                 const { writes, found } = buildLevelsPatchWrites(levelsPath, snapshot, updates.map((u) => ({ elementId: u.elementId, patch: { done: u.checked } })));
                 levelsResults = updates.map((u) => ({
                     elementId: u.elementId,

package/package.json

@@ -1,6 +1,7 @@
 {
   "name": "mmm-mcp-server",
-  "version": "0.1.0",
+  "version": "0.1.2",
+  "mcpName": "io.github.nhorie-canal/mmm-mcp-server",
   "description": "Matryoshka Mind Map の自分のデータをClaudeから直接読み書きするMCPサーバー",
   "license": "MIT",
   "repository": {