GEML — a plain-text document format built to be edited in place, one section at a time

One section in, one section out — on Markdown/GEML files, bad writes refused.

使うべきか

品質と安全性

A
説明の品質
100%
スキーマの完全性
100%
命名の品質
80%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~4,323トークン数(ツール定義)
~2.6 KB一般的なレスポンスサイズ
注意への影響は大きい(128k コンテキストの 3.38%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

{
  "mcpServers": {
    "geml": {
      "command": "npx",
      "args": [
        "@geml/geml"
      ]
    }
  }
}

実行可能なパッケージ

npm@geml/geml1.13.1stdio

リモートエンドポイント

https://geml-mcp.supermarket.workers.dev/mcpstreamable-http

できること

ツール一覧

ツール(9)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟢geml_list(source, name, within)

List every addressable block in a GEML document — its address, kind and heading text — in one call, with no paging. Call this FIRST: what it returns is what every other tool here addresses, and it is cheaper and more reliable than reading the file to see what is in it. Rows marked `anon` have no `#id`; geml_get and geml_set take their `address` as `id`, while the other write tools need a real id, so give such a block one first. A file that is not under the server root is an error. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

入力スキーマ

{
  "type": "object",
  "properties": {
    "source": {
      "type": "string",
      "description": "The document's full text. This server keeps no files: what you send is the document."
    },
    "name": {
      "type": "string",
      "description": "The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml."
    },
    "within": {
      "type": "string",
      "description": "Optional: only look inside the blocks this selector names, e.g. `#install` for a section or `=== table` for every table. It takes the same selector forms as geml_get's `id`."
    }
  },
  "required": [
    "source"
  ]
}
🟢geml_find(source, name, pattern, case, head, ...)

Search block CONTENT in the document; each hit is one `<name>\t<address>` row. geml_list says what a document contains, this says which block holds the words — as an address that pastes straight into geml_get or geml_set, not a line number the next edit invalidates. The address is the innermost block holding the match, and a block matching on many lines is reported once. Substring, case-insensitive unless `case` is true. No match is an empty result, not an error. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

入力スキーマ

{
  "type": "object",
  "properties": {
    "source": {
      "type": "string",
      "description": "The document's full text. This server keeps no files: what you send is the document."
    },
    "name": {
      "type": "string",
      "description": "The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml."
    },
    "pattern": {
      "type": "string",
      "description": "Text to look for inside block bodies"
    },
    "case": {
      "type": "boolean",
      "description": "Match case exactly (default: case-insensitive)"
    },
    "head": {
      "type": "boolean",
      "description": "Add the matching line as a third column"
    },
    "within": {
      "type": "string",
      "description": "Optional: only look inside the blocks this selector names, e.g. `#install` for a section or `=== table` for every table. It takes the same selector forms as geml_get's `id`."
    }
  },
  "required": [
    "source",
    "pattern"
  ]
}
🟢geml_get(source, name, id, view, part, ...)

Read ONE block from a GEML document instead of the whole file: only that block comes back, typically a few percent of the document. Pass the `address` geml_list prints as `id` — it also reaches blocks with no `#id`; to locate a block by its words instead, use geml_find first. An `id` that matches nothing, or a file that is not under the server root, is an error naming it. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

入力スキーマ

{
  "type": "object",
  "properties": {
    "source": {
      "type": "string",
      "description": "The document's full text. This server keeps no files: what you send is the document."
    },
    "name": {
      "type": "string",
      "description": "The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml."
    },
    "id": {
      "type": "string",
      "description": "What to read: a block id (with or without `#`), a `## Heading` line (its whole section), `=== type` for every block of a type, `=== code {lang=py}` or `{.warn}` for every block carrying those attributes, a `@<hex>` content address for a block with no id, or `L27`/`L27-58` for the smallest block holding those lines — the forms `geml_list` prints, plus the line numbers an editor or a diff hunk speaks"
    },
    "view": {
      "type": "boolean",
      "description": "Read THROUGH an `embed` block to the entity block it stands for, following a multi-layer chain to its end. An `embed` has no content of its own, so this is the only way to see what it points at; on any other block it changes nothing. Returns {from, content}: `from` names the document the content actually came from, and its references and relative paths resolve against THAT document, not this one."
    },
    "part": {
      "type": "string",
      "enum": [
        "whole",
        "head",
        "intro",
        "body"
      ],
      "description": "How much of the block to return (default: whole). For a SECTION these cut it three ways: `head` is the heading line, `intro` everything under it up to its first subheading, `body` everything under it — so `body` always contains `intro`, and equals it when the section has no subheading. Reach for `intro` to read a section's opening without pulling its subsections into the conversation; a whole `#id` on a top-level heading is often the entire document. Only a heading has an intro. `body` is usually what you want together with `view`."
    },
    "within": {
      "type": "string",
      "description": "Optional: only look inside the blocks this selector names, e.g. `#install` for a section or `=== table` for every table. It takes the same selector forms as geml_get's `id`."
    }
  },
  "required": [
    "source",
    "id"
  ]
}
🟢geml_check(source, name)

Validate a GEML document without changing it: returns every diagnostic with a stable `code`, a severity and a line, and an empty list means the document is valid. Use it to confirm a document is sound before reporting work as finished. Every write through this server runs the same check before it lands, so a refused write already carries this information. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

入力スキーマ

{
  "type": "object",
  "properties": {
    "source": {
      "type": "string",
      "description": "The document's full text. This server keeps no files: what you send is the document."
    },
    "name": {
      "type": "string",
      "description": "The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml."
    }
  },
  "required": [
    "source"
  ]
}
🟢geml_to(source, name, to, from)

Convert a WHOLE document and get the result back as text — the read half of the CLI's `geml <file> --to <fmt>`. `to: "geml"` on a Markdown file is the importer, the one thing the block tools cannot do; `to: "md"` projects a GEML document out (lossy); `to: "json"` returns the full document model, for when geml_list plus geml_get is not enough. Nothing is written — pass the result to geml_add or geml_set to land it. `to: "html"` also works but returns a whole self-contained page, usually tens of kilobytes this server cannot save: prefer the CLI (`geml <file> --to html -o out.html`) unless you want the markup in the conversation. A document with errors returns its diagnostics instead of a conversion, and a file that is not under the server root is an error. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

入力スキーマ

{
  "type": "object",
  "properties": {
    "source": {
      "type": "string",
      "description": "The document's full text. This server keeps no files: what you send is the document."
    },
    "name": {
      "type": "string",
      "description": "The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml."
    },
    "to": {
      "type": "string",
      "enum": [
        "json",
        "md",
        "geml",
        "html"
      ],
      "description": "Target format. Default is the CLI's: a GEML input becomes json, a Markdown input becomes geml. `html` is a whole page — large, and not writable from here."
    },
    "from": {
      "type": "string",
      "enum": [
        "geml",
        "md",
        "json"
      ],
      "description": "Override the input format, which is otherwise inferred from the extension (.md -> md, .json -> json, else geml)."
    }
  },
  "required": [
    "source"
  ]
}
🔴geml_set(source, name, id, body, part)

Replace ONE block and leave every other byte untouched — prefer this to rewriting a file. For content that does not exist yet use geml_add; to remove a block, geml_delete. The replacement is validated before it is written: if it would break the document, nothing is written and the diagnostics come back — fix the body rather than resending it. Removing content is not refused: if the replacement drops blocks, the write goes through and the result names each one, so check it after shortening a section; geml_revert puts one back. `part` replaces the whole block (default), its head line, a section's `intro`, or its body. In a Markdown file a heading's anchor is its text, as on GitHub: new heading text gives the heading a new address, and the document's links to the old one follow in the same write. GEML content written over a Markdown heading or prose is converted to Markdown, as in geml_add; a GEML block already in the file stays GEML. An `id` that matches no block, or several, is refused. Returns `{ok, file, diagnostics, revision}`, with `notes` when the write did something to say out loud (a block it dropped, an address it changed); a refusal is `ok: false` with a `hint`, and the file is unchanged. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

入力スキーマ

{
  "type": "object",
  "properties": {
    "source": {
      "type": "string",
      "description": "The document's full text. This server keeps no files: what you send is the document."
    },
    "name": {
      "type": "string",
      "description": "The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml."
    },
    "id": {
      "type": "string",
      "description": "Which block to replace: an id (with or without `#`), a `@<hex>` content address from `geml_list` for a block with no id, or `L27`/`L27-58` for the smallest block holding those lines. Must match exactly one block"
    },
    "body": {
      "type": "string",
      "description": "The replacement text"
    },
    "part": {
      "type": "string",
      "enum": [
        "whole",
        "head",
        "intro",
        "body"
      ],
      "description": "What to replace (default: whole). `intro` replaces a section's opening — everything under the heading up to its first subheading — and leaves every subsection byte-identical, which is what makes a read-edit-write cycle on a long section safe. An empty intro (a subheading follows the heading immediately) is written into, so this also adds an opening where there was none."
    }
  },
  "required": [
    "source",
    "id",
    "body"
  ]
}
🟡geml_add(source, name, content, position, anchor)

Insert new content — one or more blocks, or prose — at the end of the document (`position: append`) or before/after the block named by `anchor`. Use this for content that does not exist yet; to change a block that does, use geml_set. Ids inside the content are kept. In a `.md` file Markdown lands as written, and GEML content is converted to Markdown as `to: "md"` converts it, the result's `notes` saying so; content Markdown cannot hold, such as a view without its source, is refused. Like every write here it is validated first: a missing anchor, an id that clashes with an existing one, or content that would break the document is refused. Returns `{ok, file, diagnostics, revision}`, with `notes` when the write did something to say out loud (a block it dropped, an address it changed); a refusal is `ok: false` with a `hint`, and the file is unchanged. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

入力スキーマ

{
  "type": "object",
  "properties": {
    "source": {
      "type": "string",
      "description": "The document's full text. This server keeps no files: what you send is the document."
    },
    "name": {
      "type": "string",
      "description": "The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml."
    },
    "content": {
      "type": "string",
      "description": "The GEML fragment to insert"
    },
    "position": {
      "type": "string",
      "enum": [
        "append",
        "before",
        "after"
      ],
      "description": "Where to insert"
    },
    "anchor": {
      "type": "string",
      "description": "The block the insertion is relative to — an id, or any address geml_list prints; it must name one block. Required for before/after"
    }
  },
  "required": [
    "source",
    "content",
    "position"
  ]
}
🔴geml_delete(source, name, ids)

Remove one or more blocks, each named by an id or any address geml_list prints; a filter (`=== type`, `{key=value}`) removes every block it matches. Each block takes the blank line that separated it from its neighbours, so deleting what geml_add inserted leaves the file as it was. To undo a deletion, geml_revert the removed id; to change a block rather than remove it, use geml_set. References left pointing at a removed block come back as diagnostics but do NOT block the deletion — read them, then repair the references or revert. A selector that names nothing is skipped, so repeating a call changes nothing. Returns `{ok, file, diagnostics, revision}`, with `notes` when the write did something to say out loud (a block it dropped, an address it changed); a refusal is `ok: false` with a `hint`, and the file is unchanged. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

入力スキーマ

{
  "type": "object",
  "properties": {
    "source": {
      "type": "string",
      "description": "The document's full text. This server keeps no files: what you send is the document."
    },
    "name": {
      "type": "string",
      "description": "The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml."
    },
    "ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The blocks to remove: ids or addresses"
    }
  },
  "required": [
    "source",
    "ids"
  ]
}
🟡geml_rename(source, name, old, new)

Rename a block id AND every reference to it in the same document, in one id-boundary-safe write. Use this rather than geml_set or a text search-and-replace, which would also hit ids that merely share a prefix. A Markdown heading's anchor is its text, so it is renamed by changing the heading with geml_set (`part: head`), not here. An `old` id that does not exist, or a `new` one already taken, is refused. Returns `{ok, file, diagnostics, revision}`, with `notes` when the write did something to say out loud (a block it dropped, an address it changed); a refusal is `ok: false` with a `hint`, and the file is unchanged. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

入力スキーマ

{
  "type": "object",
  "properties": {
    "source": {
      "type": "string",
      "description": "The document's full text. This server keeps no files: what you send is the document."
    },
    "name": {
      "type": "string",
      "description": "The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml."
    },
    "old": {
      "type": "string",
      "description": "Current id"
    },
    "new": {
      "type": "string",
      "description": "New id"
    }
  },
  "required": [
    "source",
    "old",
    "new"
  ]
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 9 件
検証済みバージョンは記録されていませんツール 9 件
検証済みバージョンは記録されていませんツール 9 件
検証済みバージョンは記録されていませんツール 9 件