drawspec 0.3.0__tar.gz → 0.3.2__tar.gz

{drawspec-0.3.0 → drawspec-0.3.2}/.github/workflows/release.yml

@@ -173,6 +173,34 @@ jobs:
       - name: Upload
         uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # release/v1
 
+  mcp-registry:
+    name: Publish to the MCP Registry
+    needs: [tag, publish]
+    if: needs.tag.outputs.tag != ''
+    runs-on: ubuntu-latest
+    permissions:
+      # The registry checks io.github.nuncaeslupus/* against this workflow's OIDC
+      # token, and the package by the `mcp-name:` line in the README now on PyPI.
+      id-token: write
+      contents: read
+    steps:
+      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4
+        with:
+          persist-credentials: false
+
+      - name: Install mcp-publisher (pinned, checksum-verified)
+        env:
+          MCP_PUBLISHER_VERSION: v1.8.1
+          MCP_PUBLISHER_SHA256: a06c9096dcb9727c13555b6be26c7effa707b01f06a4c561ba7a3635443cf2cc
+        run: |
+          curl -fsSLo mcp-publisher.tar.gz "https://github.com/modelcontextprotocol/registry/releases/download/${MCP_PUBLISHER_VERSION}/mcp-publisher_linux_amd64.tar.gz"
+          echo "${MCP_PUBLISHER_SHA256}  mcp-publisher.tar.gz" | sha256sum -c -
+          tar xzf mcp-publisher.tar.gz mcp-publisher
+
+      - run: ./mcp-publisher login github-oidc
+
+      - run: ./mcp-publisher publish
+
   announce:
     name: Cut the GitHub release
     needs: [tag, publish]

{drawspec-0.3.0 → drawspec-0.3.2}/AGENTS.md

@@ -11,7 +11,7 @@ drawspec schema --out schema.json             # the full JSON Schema
 drawspec theme from site.css -o house.toml    # a theme from a brand's CSS or design tokens
 ```
 
-**If your client speaks MCP**, `drawspec-mcp` serves `validate`, `render` and `kinds` as tools,
+**If your client speaks MCP**, `drawspec-mcp` serves `list_kinds`, `get_example`, `get_schema`, `validate_document` and `render_document` as tools,
 each violation a `{"pointer": "/edges/0/to", "message": …}` object: `pip install 'drawspec[mcp]'`, [`docs/guide.md`](docs/guide.md).
 
 ## The one rule

{drawspec-0.3.0 → drawspec-0.3.2}/CHANGELOG.md

@@ -10,6 +10,34 @@ against it would stop working. Everything below is about the *package*.
 
 ## [Unreleased]
 
+## [0.3.2] — 2026-10-15
+
+### Changed
+
+- **The MCP tools are renamed to one verb_noun convention**: `validate` →
+  `validate_document`, `render` → `render_document`, `kinds` → `list_kinds`. The CLI
+  commands keep their names.
+- **Sharper tool descriptions**: when to validate and when to render, the shape of
+  every answer and of every refusal, and read-only annotations on all tools. JSON
+  answers also come back as structured content matching an output schema.
+
+### Added
+
+- **`get_example`** and **`get_schema`** MCP tools: the smallest valid document of a
+  kind (what `drawspec example` prints), and that kind's slice of the published
+  schema with only the definitions it uses (a few thousand characters, not the whole
+  file's two hundred thousand).
+
+## [0.3.1] — 2026-10-15
+
+### Added
+
+- **The official MCP Registry** lists drawspec as `io.github.nuncaeslupus/drawspec`:
+  `server.json`, the `mcp-name` line the registry looks for in the PyPI README, and a
+  release job that publishes it through GitHub's OIDC once PyPI has the version.
+- **`drawspec mcp`**, the same server as `drawspec-mcp`, so a launcher that only runs the
+  package's own command reaches it: `uvx --from 'drawspec[mcp]' drawspec mcp`.
+
 ## [0.3.0] — 2026-10-14
 
 ### Added

{drawspec-0.3.0 → drawspec-0.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: drawspec
-Version: 0.3.0
+Version: 0.3.2
 Summary: Declarative diagram spec to clean, themeable SVG — writable by an LLM with no coordinates.
 Project-URL: Homepage, https://github.com/nuncaeslupus/drawspec
 Project-URL: Documentation, https://github.com/nuncaeslupus/drawspec/blob/main/docs/guide.md
@@ -40,10 +40,14 @@ Description-Content-Type: text/markdown
 
 # <img src="https://raw.githubusercontent.com/nuncaeslupus/drawspec/main/docs/logo.png" width="40" height="40" alt="" align="top"> drawspec
 
+<!-- mcp-name: io.github.nuncaeslupus/drawspec -->
+
 <!-- claude-arsenal:attribution: added by claude-arsenal's /init. Delete this block to drop it (it is not put back), or set `attribution = false` in the arsenal config.toml. -->
 [![Built with claude-arsenal](https://img.shields.io/badge/built%20with-claude--arsenal-d97756)](https://github.com/nuncaeslupus/claude-arsenal)
 <!-- /claude-arsenal:attribution -->
 
+[![drawspec MCP server – quality and maintenance score on Glama](https://glama.ai/mcp/servers/nuncaeslupus/drawspec/badges/score.svg)](https://glama.ai/mcp/servers/nuncaeslupus/drawspec)
+
 <p align="center">
   <img src="https://raw.githubusercontent.com/nuncaeslupus/drawspec/main/docs/hero.png" width="100%" alt="drawspec: a blueprint sheet with the wordmark, a JSON flow spec and the flow chart drawspec renders from it, with large faint venn and pie drawings behind the wordmark, a mind map and a project file tree drawn by drawspec, and beside them a small sequence diagram as drawspec's text output, once in box drawing and once in ASCII">
 </p>
@@ -399,7 +403,8 @@ what the guide and the references are for. [`llms.txt`](llms.txt) is the index
 that points at it.
 
 And if your client speaks **MCP**, `pip install 'drawspec[mcp]'` gives you
-`drawspec-mcp`: `validate`, `render` and `kinds` as tools, so a refusal arrives as
+`drawspec-mcp`: `list_kinds`, `get_example`, `get_schema`, `validate_document` and
+`render_document` as tools, so a refusal arrives as
 `{"pointer": "/edges/0/to", "message": …}` in the model's own loop instead of as
 prose on stderr it has to read. Same checks, same messages, no shell. See
 [the guide](docs/guide.md#using-it-from-an-agent-the-mcp-server).

{drawspec-0.3.0 → drawspec-0.3.2}/README.md

@@ -1,9 +1,13 @@
 # <img src="https://raw.githubusercontent.com/nuncaeslupus/drawspec/main/docs/logo.png" width="40" height="40" alt="" align="top"> drawspec
 
+<!-- mcp-name: io.github.nuncaeslupus/drawspec -->
+
 <!-- claude-arsenal:attribution: added by claude-arsenal's /init. Delete this block to drop it (it is not put back), or set `attribution = false` in the arsenal config.toml. -->
 [![Built with claude-arsenal](https://img.shields.io/badge/built%20with-claude--arsenal-d97756)](https://github.com/nuncaeslupus/claude-arsenal)
 <!-- /claude-arsenal:attribution -->
 
+[![drawspec MCP server – quality and maintenance score on Glama](https://glama.ai/mcp/servers/nuncaeslupus/drawspec/badges/score.svg)](https://glama.ai/mcp/servers/nuncaeslupus/drawspec)
+
 <p align="center">
   <img src="https://raw.githubusercontent.com/nuncaeslupus/drawspec/main/docs/hero.png" width="100%" alt="drawspec: a blueprint sheet with the wordmark, a JSON flow spec and the flow chart drawspec renders from it, with large faint venn and pie drawings behind the wordmark, a mind map and a project file tree drawn by drawspec, and beside them a small sequence diagram as drawspec's text output, once in box drawing and once in ASCII">
 </p>
@@ -359,7 +363,8 @@ what the guide and the references are for. [`llms.txt`](llms.txt) is the index
 that points at it.
 
 And if your client speaks **MCP**, `pip install 'drawspec[mcp]'` gives you
-`drawspec-mcp`: `validate`, `render` and `kinds` as tools, so a refusal arrives as
+`drawspec-mcp`: `list_kinds`, `get_example`, `get_schema`, `validate_document` and
+`render_document` as tools, so a refusal arrives as
 `{"pointer": "/edges/0/to", "message": …}` in the model's own loop instead of as
 prose on stderr it has to read. Same checks, same messages, no shell. See
 [the guide](docs/guide.md#using-it-from-an-agent-the-mcp-server).

{drawspec-0.3.0 → drawspec-0.3.2}/docs/cli.md

@@ -4,7 +4,7 @@
 
 ```
 usage: drawspec [-h] [--version]
-                {render,validate,theme,schema,kinds,example} ...
+                {render,validate,theme,schema,kinds,example,mcp} ...
 ```
 
 Nothing is printed to stdout but the thing that was asked for — the SVG, the
@@ -143,6 +143,14 @@ usage: drawspec example [-h]
 |---|---|
 | `kind` | Which kind to write. One of `flow`, `tree`, `cycle`, `stack`, `timeline`, `columns`, `matrix`, `pyramid`, `rings`, `funnel`, `chart`, `quadrant`, `scatter`, `curve`, `files`, `states`, `sequence`, `lanes`, `entities`, `gantt`, `board`, `fishbone`, `venn`, `journey`, `treemap`, `sankey`, `numberline`, `barmodel`, `waterfall`, `pie`, `mindmap`, `argument`, `familytree`, `meter`, `rag`, `clock`. |
 
+### `drawspec mcp`
+
+The MCP server; needs the extra: pip install 'drawspec[mcp]'.
+
+```
+usage: drawspec mcp [-h]
+```
+
 ## Embedding profiles
 
 `render --profile` takes `inline`, `standalone`.

{drawspec-0.3.0 → drawspec-0.3.2}/docs/guide.md

@@ -466,7 +466,7 @@ cross-links or groups is drawn this way too; `bands` have no text form yet.
   side by side.
 
 From Python, `render_text(document, width=80, charset="unicode")` returns the
-string; the MCP `render` tool takes `"format": "text"` with the same `width` and
+string; the MCP `render_document` tool takes `"format": "text"` with the same `width` and
 `charset`.
 
 ## Validating in a build
@@ -760,14 +760,19 @@ picking a winner would be drawspec deciding which of two things you meant.
 ## Using it from an agent: the MCP server
 
 If the thing writing your documents is a language model rather than a person,
-there is a third interface. `drawspec-mcp` serves the same work as three MCP
-tools over stdio:
+there is a third interface. `drawspec-mcp` serves the same work as five MCP
+tools over stdio, one per step of writing a document:
 
 | Tool | Answers |
 |---|---|
-| `validate` | would `render` refuse this, and **where** — every violation as `{"pointer", "message"}` |
-| `render` | the SVG, with the same optional `theme`, `width` and `height` — or, with `"format": "png"` (and optional `scale`, `background`), a base64 PNG image block, when the server has `drawspec[png]` |
-| `kinds` | every kind and what it is for, so a model chooses one instead of guessing |
+| `list_kinds` | every kind and what it is for, so a model chooses one instead of guessing |
+| `get_example` | the smallest valid document of one kind — what `drawspec example <kind>` prints |
+| `get_schema` | one kind's fields, cut from the published schema with only the definitions it uses |
+| `validate_document` | would `render_document` refuse this, and **where** — every violation as `{"pointer", "message"}` |
+| `render_document` | the SVG, with the same optional `theme`, `width` and `height` — or, with `"format": "png"` (and optional `scale`, `background`), a base64 PNG image block, when the server has `drawspec[png]`; or with `"format": "text"`, the plain-text form |
+
+All five are read-only; the JSON answers also come back as structured content
+matching each tool's output schema.
 
 ```bash
 pip install 'drawspec[mcp]'
@@ -783,7 +788,7 @@ Then point a client at it. For anything that reads the conventional JSON config:
 }
 ```
 
-**`validate` is the one that earns the server.** Shelling out to the CLI works,
+**`validate_document` is the one that earns the server.** Shelling out to the CLI works,
 and it hands a model prose on stderr that it has to read to discover that
 `/edges/2/to` names nothing. As a tool the same refusal comes back as data, in
 the model's own loop, and the write-validate-fix cycle closes without a shell in

{drawspec-0.3.0 → drawspec-0.3.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "drawspec"
-version = "0.3.0"
+version = "0.3.2"
 description = "Declarative diagram spec to clean, themeable SVG — writable by an LLM with no coordinates."
 readme = "README.md"
 requires-python = ">=3.12"

drawspec-0.3.2/server.json

@@ -0,0 +1,35 @@
+{
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
+  "name": "io.github.nuncaeslupus/drawspec",
+  "title": "drawspec",
+  "description": "Validate and render declarative diagram specs to clean SVG or PNG; no coordinates needed.",
+  "repository": {
+    "url": "https://github.com/nuncaeslupus/drawspec",
+    "source": "github"
+  },
+  "version": "0.3.2",
+  "packages": [
+    {
+      "registryType": "pypi",
+      "identifier": "drawspec",
+      "version": "0.3.2",
+      "runtimeHint": "uvx",
+      "runtimeArguments": [
+        {
+          "type": "named",
+          "name": "--from",
+          "value": "drawspec[mcp]"
+        }
+      ],
+      "transport": {
+        "type": "stdio"
+      },
+      "packageArguments": [
+        {
+          "type": "positional",
+          "value": "mcp"
+        }
+      ]
+    }
+  ]
+}

{drawspec-0.3.0 → drawspec-0.3.2}/skills/drawspec/SKILL.md

@@ -11,7 +11,8 @@ rather than guess at.
 
 1. **Install.** `pip install drawspec`. If your client speaks MCP and the
    `drawspec-mcp` server is available (`pip install 'drawspec[mcp]'`), use its
-   `kinds`, `validate` and `render` tools instead of the shell commands below.
+   `list_kinds`, `get_example`, `get_schema`, `validate_document` and
+   `render_document` tools instead of the shell commands below.
 2. **Read the format.** `AGENTS.md` at
    https://github.com/nuncaeslupus/drawspec/blob/main/AGENTS.md — read it whole,
    once. Offline, `drawspec kinds` lists the kinds and `drawspec example <kind>`

{drawspec-0.3.0 → drawspec-0.3.2}/src/drawspec/__init__.py

@@ -19,7 +19,7 @@ from drawspec.scene import Ellipse, Path, Polygon, Rect, Scene, TextRun
 from drawspec.schema import Document, load_document, parse_document, validate_document
 from drawspec.theme import Theme, load_theme
 
-__version__ = "0.3.0"
+__version__ = "0.3.2"
 
 __all__ = [
     "Box",

{drawspec-0.3.0 → drawspec-0.3.2}/src/drawspec/cli.py

@@ -198,6 +198,15 @@ def build_parser() -> argparse.ArgumentParser:
     )
     example.add_argument("kind", choices=KINDS, help="which kind to write")
 
+    # The same server as `drawspec-mcp`, reachable as `drawspec mcp` so a launcher
+    # that can only run the package's own command (`uvx --from 'drawspec[mcp]'
+    # drawspec mcp`, the MCP Registry's entry) gets to it too.
+    commands.add_parser(
+        "mcp",
+        help="serve validate, render and kinds as MCP tools over stdio",
+        description="The MCP server; needs the extra: pip install 'drawspec[mcp]'.",
+    )
+
     return parser
 
 
@@ -224,6 +233,11 @@ def main(argv: Sequence[str] | None = None) -> int:
         return _validate(arguments)
     if arguments.command == "kinds":
         return _kinds()
+    if arguments.command == "mcp":
+        from drawspec.mcp import main as serve_mcp
+
+        serve_mcp()
+        return OK
     if arguments.command == "example":
         return _example(arguments)
     if arguments.command == "theme":