glossary-mcp 0.1.0__tar.gz

glossary_mcp-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,39 @@
+name: CI
+
+on:
+  push:
+    branches: ["main"]
+  pull_request:
+
+# Least privilege: the test job only reads the repo.
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12"]
+    env:
+      UV_PYTHON: ${{ matrix.python-version }}
+    steps:
+      # SHA-pinned, node24-runtime actions.
+      - name: Checkout
+        uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10  # v6.0.3
+        with:
+          persist-credentials: false
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39  # v8.2.0
+        with:
+          enable-cache: true
+
+      - name: Install Python ${{ matrix.python-version }}
+        run: uv python install ${{ matrix.python-version }}
+
+      - name: Sync dependencies (frozen)
+        run: uv sync --frozen
+
+      - name: Run tests with branch coverage
+        run: uv run pytest

glossary_mcp-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,35 @@
+name: Release
+
+# Publish to PyPI via Trusted Publishing (OIDC — no stored token) when a
+# v* tag is pushed. Configure the trusted publisher on PyPI first (see the
+# release notes): project glossary-mcp, owner dhh1128, repo
+# glossary-mcp, workflow release.yml.
+on:
+  push:
+    tags: ["v*"]
+
+# Least privilege by default; the publish job additionally requests id-token.
+permissions:
+  contents: read
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      id-token: write  # mint the OIDC token uv exchanges for a PyPI upload token
+    steps:
+      # SHA-pinned, node24-runtime actions (match CI).
+      - name: Checkout
+        uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10  # v6.0.3
+        with:
+          persist-credentials: false
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39  # v8.2.0
+
+      - name: Build sdist and wheel
+        run: uv build
+
+      - name: Publish to PyPI (Trusted Publishing)
+        run: uv publish --trusted-publishing always

glossary_mcp-0.1.0/.gitignore

@@ -0,0 +1,31 @@
+# ── Python ────────────────────────────────────────────────────────────────────
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+*.egg
+*.egg-info/
+dist/
+build/
+eggs/
+develop-eggs/
+wheels/
+share/python-wheels/
+MANIFEST
+
+# Virtual environments
+.venv/
+venv/
+env/
+ENV/
+.env
+
+# Test / tooling caches
+.pytest_cache/
+.coverage
+htmlcov/
+.mypy_cache/
+.ruff_cache/
+
+# codebase-memory-mcp graph
+.codebase-memory/

glossary_mcp-0.1.0/AGENTS.md

@@ -0,0 +1,40 @@
+# Agent instructions — glossary-mcp
+
+A general-purpose MCP server over the [conlangkit](https://github.com/dhh1128/conlangkit)
+glossary format. It reads, searches, and **safely edits** a glossary file for any
+project. conlangkit is the format authority (a normal PyPI dependency); glossary
+handling lives in `conlangkit.glossary`, which this server wraps — do not
+reimplement parsing. All conlangkit imports are funnelled through `glossary_io`.
+
+## Methodology
+
+Non-trivial work runs under the `cc` craft methodology (`~/code/me/cc`, edition
+0.1) — this repo is a *consumer*, referencing it by path. Read
+`~/code/me/cc/constitution.md` first; skim `ledger.md` for a pre-mortem.
+
+## Testing protocol (strict TDD)
+
+1. Write one or more failing tests capturing each requirement (happy path **and**
+   edge/unhappy paths) before implementing.
+2. Implement until all tests pass.
+3. Never commit unless all tests pass; coverage of code you touch must not
+   decrease. The **write path** (`add_term`/`update_term`, atomic save,
+   minimal-diff, escape round-trip) is the risky part — cover it hard.
+
+## Engineering standards
+
+- Python 3.11+, **uv** (`uv sync`, `uv run pytest`); 100% branch-coverage gate.
+- **DCO sign-off** (`-s`) on every commit. Commit locally; the maintainer pushes.
+- CI actions pinned to **node24-runtime** versions (SHA-pinned `actions/checkout@v6`,
+  `astral-sh/setup-uv`); verify each tag's runtime before bumping.
+- Writes go through conlangkit (`insert`/`update` + `save`): conlangkit owns sort
+  order (byte order) and re-emits the file. Keep the glossary in that canonical
+  order so writes stay minimal-diff. Saves are atomic (temp + `os.replace`); the
+  file is re-read before each write. Do not add line-level editing on top of conlangkit.
+
+## Format note
+
+A literal `/` in a definition is stored backslash-escaped on disk (`\/`); the
+server escapes/unescapes transparently so callers deal only in plain prose. Never
+hand-write an unescaped literal slash into a definition cell — conlangkit reads a
+bare `/` as the sense separator.

glossary_mcp-0.1.0/CLAUDE.md

@@ -0,0 +1 @@
+YOU MUST read and follow `AGENTS.md` at the repository root before making any change; `AGENTS.md` is the authoritative instruction file for this repository, and the current file is only a pointer for tools that look for tool-specific instruction files.

glossary_mcp-0.1.0/GEMINI.md

@@ -0,0 +1 @@
+YOU MUST read and follow `AGENTS.md` at the repository root before making any change; `AGENTS.md` is the authoritative instruction file for this repository, and the current file is only a pointer for tools that look for tool-specific instruction files.

glossary_mcp-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

glossary_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,169 @@
+Metadata-Version: 2.4
+Name: glossary-mcp
+Version: 0.1.0
+Summary: General-purpose MCP server to read, search, and safely edit a conlangkit-format glossary
+Project-URL: Homepage, https://github.com/dhh1128/glossary-mcp
+Project-URL: Repository, https://github.com/dhh1128/glossary-mcp
+Project-URL: Issues, https://github.com/dhh1128/glossary-mcp/issues
+Author-email: Daniel Hardman <daniel.hardman@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: claude,conlangkit,glossary,mcp,terminology
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Libraries
+Requires-Python: >=3.11
+Requires-Dist: conlangkit>=0.1
+Requires-Dist: mcp>=1.0
+Requires-Dist: pydantic>=2.0
+Description-Content-Type: text/markdown
+
+# glossary-mcp
+
+[![CI](https://github.com/dhh1128/glossary-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/dhh1128/glossary-mcp/actions/workflows/ci.yml)
+
+A small, **general-purpose** MCP server that lets an AI **read, search, and safely
+edit a glossary file** in the [conlangkit](https://github.com/dhh1128/conlangkit)
+glossary format — for *any* glossary, not tied to any one project.
+
+The glossary is a Markdown pipe-table with four columns:
+
+```
+lemma | tags | definition | notes
+----- | ---- | ---------- | -----
+core  | tier | the constitutive tier-1 material of a party | never shared
+```
+
+Writes go through conlangkit, which owns the file: it keeps entries sorted (by byte
+order) and re-emits the glossary on save. On an already-sorted file that yields a
+**minimal diff** — only the touched row moves. The file is re-read from disk before
+each write (so a long-lived server picks up external hand-edits) and the write is
+atomic (temp file + `os.replace`).
+
+## Prerequisites
+
+- Python 3.11+
+- [uv](https://docs.astral.sh/uv/)
+- A glossary directory or file, pointed to by `GLOSSARY_PATH`
+
+[conlangkit](https://github.com/dhh1128/conlangkit) (the glossary format library)
+is a normal PyPI dependency, pulled in by `uv sync`.
+
+## Installation
+
+```bash
+uv sync   # creates .venv, installs glossary-mcp (editable) + conlangkit + dev deps
+```
+
+## Running tests
+
+```bash
+uv run pytest   # runs the suite with branch coverage (gate: 100%)
+```
+
+The smoke tests run without `GLOSSARY_PATH`. Integration tests run against a
+fixture glossary.
+
+## Running the server
+
+```bash
+export GLOSSARY_PATH=/path/to/glossary        # a directory containing glossary.md …
+export GLOSSARY_PATH=/path/to/glossary.md     # … or a direct path to the file
+uv run glossary-mcp
+```
+
+`GLOSSARY_PATH` may be a **directory** (the server looks for `glossary.md` inside
+it) or a **file**. The server uses stdio transport. For a local checkout, set
+`command` to a resolvable path, e.g. the project's
+`/path/to/glossary-mcp/.venv/bin/glossary-mcp`:
+
+```json
+{
+  "mcpServers": {
+    "glossary": {
+      "command": "glossary-mcp",
+      "env": {
+        "GLOSSARY_PATH": "/path/to/glossary"
+      }
+    }
+  }
+}
+```
+
+For consuming the **published** package from *another* repo without a local
+checkout or absolute paths, use `uvx` — see the next section.
+
+## Consuming from another repo (portable `.mcp.json`)
+
+`glossary-mcp` is published to [PyPI](https://pypi.org/project/glossary-mcp/),
+so any other repo can wire it into its MCP configuration with **no local checkout,
+no venv, and no absolute paths**. `uvx` fetches and caches the package (and its
+`conlangkit` / `mcp` dependencies) on demand:
+
+```json
+{
+  "mcpServers": {
+    "glossary": {
+      "type": "stdio",
+      "command": "uvx",
+      "args": ["glossary-mcp==0.1.0"],
+      "env": {
+        "GLOSSARY_PATH": "${CLAUDE_PROJECT_DIR:-.}/../glossary"
+      }
+    }
+  }
+}
+```
+
+- **`command: "uvx"`, `args: ["glossary-mcp"]`** — the console-script name
+  equals the package name, so **no `--from` flag is needed**. `uvx` resolves the
+  package from PyPI into an ephemeral, cached environment on first launch.
+- **`GLOSSARY_PATH`** is the only required environment variable. It may point at a
+  directory (the server looks for `glossary.md` inside) or directly at a file. The
+  `${CLAUDE_PROJECT_DIR:-.}/../glossary` value assumes the standard sibling layout
+  where the consuming repo and its `glossary` repo are checked out side by side.
+  `${CLAUDE_PROJECT_DIR}` resolves the project root and requires **Claude Code ≥
+  v2.1.195**; the `:-.` fallback keeps it working (relative to the current
+  directory) on older versions and other MCP clients.
+- **Pin the version while pre-1.0.** Because the tool surface may still change
+  before 1.0, pin so a new release can't reach every consuming repo at once and
+  break them in lockstep: `"args": ["glossary-mcp==0.1.0"]`. Bump
+  deliberately (repo by repo, or via your propagation tooling). Float the version
+  (bare `"glossary-mcp"`, always latest) only once the surface stabilizes
+  at ≥ 1.0.
+
+## Tools
+
+| Tool | Description |
+|---|---|
+| `lookup_term` | Exact lemma lookup → tags, definition, notes |
+| `search_by_definition` | Find entries whose definition matches a query |
+| `search_notes` | Free-text search over the notes column |
+| `glossary_stats` | Entry count, tag histogram, unique-tag count |
+| `list_terms` | All lemmas, optionally filtered by tag |
+| `add_term` | Append a new entry (refuses a duplicate lemma) |
+| `update_term` | Edit an existing entry's tags/definition/notes by lemma |
+
+### A note on slashes in definitions
+
+In the conlangkit format, `/` separates alternative senses in the definition column.
+A definition that contains a *literal* slash (e.g. `allow/ask/deny`) is stored
+escaped on disk as `allow\/ask\/deny` — which renders as a plain `/` on GitHub
+(CommonMark/GFM). **You never type the escape**: pass ordinary prose (with plain
+slashes) to `add_term`/`update_term`, and read ordinary prose back — the server
+escapes and unescapes transparently.
+
+### Case sensitivity
+
+Lemma lookup, insertion, and sorting are **case-sensitive** (byte order) — conlangkit
+targets writing systems where case-folding is not meaningful, so `core` and `Core`
+are distinct entries. Use each term's canonical case: lowercase for ordinary terms,
+uppercase for acronyms (`AID`, `GCD`). This keeps you from creating near-duplicates.
+
+## Methodology
+
+Non-trivial work in this repo runs under the `cc` craft methodology
+(`~/code/me/cc`); read `constitution.md` first. Follow strict TDD (see
+`AGENTS.md`).

glossary_mcp-0.1.0/README.md

@@ -0,0 +1,147 @@
+# glossary-mcp
+
+[![CI](https://github.com/dhh1128/glossary-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/dhh1128/glossary-mcp/actions/workflows/ci.yml)
+
+A small, **general-purpose** MCP server that lets an AI **read, search, and safely
+edit a glossary file** in the [conlangkit](https://github.com/dhh1128/conlangkit)
+glossary format — for *any* glossary, not tied to any one project.
+
+The glossary is a Markdown pipe-table with four columns:
+
+```
+lemma | tags | definition | notes
+----- | ---- | ---------- | -----
+core  | tier | the constitutive tier-1 material of a party | never shared
+```
+
+Writes go through conlangkit, which owns the file: it keeps entries sorted (by byte
+order) and re-emits the glossary on save. On an already-sorted file that yields a
+**minimal diff** — only the touched row moves. The file is re-read from disk before
+each write (so a long-lived server picks up external hand-edits) and the write is
+atomic (temp file + `os.replace`).
+
+## Prerequisites
+
+- Python 3.11+
+- [uv](https://docs.astral.sh/uv/)
+- A glossary directory or file, pointed to by `GLOSSARY_PATH`
+
+[conlangkit](https://github.com/dhh1128/conlangkit) (the glossary format library)
+is a normal PyPI dependency, pulled in by `uv sync`.
+
+## Installation
+
+```bash
+uv sync   # creates .venv, installs glossary-mcp (editable) + conlangkit + dev deps
+```
+
+## Running tests
+
+```bash
+uv run pytest   # runs the suite with branch coverage (gate: 100%)
+```
+
+The smoke tests run without `GLOSSARY_PATH`. Integration tests run against a
+fixture glossary.
+
+## Running the server
+
+```bash
+export GLOSSARY_PATH=/path/to/glossary        # a directory containing glossary.md …
+export GLOSSARY_PATH=/path/to/glossary.md     # … or a direct path to the file
+uv run glossary-mcp
+```
+
+`GLOSSARY_PATH` may be a **directory** (the server looks for `glossary.md` inside
+it) or a **file**. The server uses stdio transport. For a local checkout, set
+`command` to a resolvable path, e.g. the project's
+`/path/to/glossary-mcp/.venv/bin/glossary-mcp`:
+
+```json
+{
+  "mcpServers": {
+    "glossary": {
+      "command": "glossary-mcp",
+      "env": {
+        "GLOSSARY_PATH": "/path/to/glossary"
+      }
+    }
+  }
+}
+```
+
+For consuming the **published** package from *another* repo without a local
+checkout or absolute paths, use `uvx` — see the next section.
+
+## Consuming from another repo (portable `.mcp.json`)
+
+`glossary-mcp` is published to [PyPI](https://pypi.org/project/glossary-mcp/),
+so any other repo can wire it into its MCP configuration with **no local checkout,
+no venv, and no absolute paths**. `uvx` fetches and caches the package (and its
+`conlangkit` / `mcp` dependencies) on demand:
+
+```json
+{
+  "mcpServers": {
+    "glossary": {
+      "type": "stdio",
+      "command": "uvx",
+      "args": ["glossary-mcp==0.1.0"],
+      "env": {
+        "GLOSSARY_PATH": "${CLAUDE_PROJECT_DIR:-.}/../glossary"
+      }
+    }
+  }
+}
+```
+
+- **`command: "uvx"`, `args: ["glossary-mcp"]`** — the console-script name
+  equals the package name, so **no `--from` flag is needed**. `uvx` resolves the
+  package from PyPI into an ephemeral, cached environment on first launch.
+- **`GLOSSARY_PATH`** is the only required environment variable. It may point at a
+  directory (the server looks for `glossary.md` inside) or directly at a file. The
+  `${CLAUDE_PROJECT_DIR:-.}/../glossary` value assumes the standard sibling layout
+  where the consuming repo and its `glossary` repo are checked out side by side.
+  `${CLAUDE_PROJECT_DIR}` resolves the project root and requires **Claude Code ≥
+  v2.1.195**; the `:-.` fallback keeps it working (relative to the current
+  directory) on older versions and other MCP clients.
+- **Pin the version while pre-1.0.** Because the tool surface may still change
+  before 1.0, pin so a new release can't reach every consuming repo at once and
+  break them in lockstep: `"args": ["glossary-mcp==0.1.0"]`. Bump
+  deliberately (repo by repo, or via your propagation tooling). Float the version
+  (bare `"glossary-mcp"`, always latest) only once the surface stabilizes
+  at ≥ 1.0.
+
+## Tools
+
+| Tool | Description |
+|---|---|
+| `lookup_term` | Exact lemma lookup → tags, definition, notes |
+| `search_by_definition` | Find entries whose definition matches a query |
+| `search_notes` | Free-text search over the notes column |
+| `glossary_stats` | Entry count, tag histogram, unique-tag count |
+| `list_terms` | All lemmas, optionally filtered by tag |
+| `add_term` | Append a new entry (refuses a duplicate lemma) |
+| `update_term` | Edit an existing entry's tags/definition/notes by lemma |
+
+### A note on slashes in definitions
+
+In the conlangkit format, `/` separates alternative senses in the definition column.
+A definition that contains a *literal* slash (e.g. `allow/ask/deny`) is stored
+escaped on disk as `allow\/ask\/deny` — which renders as a plain `/` on GitHub
+(CommonMark/GFM). **You never type the escape**: pass ordinary prose (with plain
+slashes) to `add_term`/`update_term`, and read ordinary prose back — the server
+escapes and unescapes transparently.
+
+### Case sensitivity
+
+Lemma lookup, insertion, and sorting are **case-sensitive** (byte order) — conlangkit
+targets writing systems where case-folding is not meaningful, so `core` and `Core`
+are distinct entries. Use each term's canonical case: lowercase for ordinary terms,
+uppercase for acronyms (`AID`, `GCD`). This keeps you from creating near-duplicates.
+
+## Methodology
+
+Non-trivial work in this repo runs under the `cc` craft methodology
+(`~/code/me/cc`); read `constitution.md` first. Follow strict TDD (see
+`AGENTS.md`).