Skip to content

Distribution: 0.1.14 on NuGet and the MCP Registry #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Karzone merged 1 commit into from
Oct 11, 2026
Merged

Distribution: 0.1.14 on NuGet and the MCP Registry #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/DISTRIBUTION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,9 @@ Where TestAtlas is published, and the status of pending directory/registry submi

| Channel | Identifier | Status |
| --- | --- | --- |
| NuGet — server | [`TestAtlas.Mcp`](https://www.nuget.org/packages/TestAtlas.Mcp) | v0.1.13 |
| NuGet — CLI | [`TestAtlas.Cli`](https://www.nuget.org/packages/TestAtlas.Cli) | v0.1.13 |
| Official MCP Registry | `io.github.Karzone/TestAtlas.Mcp` | v0.1.13, active |
| NuGet — server | [`TestAtlas.Mcp`](https://www.nuget.org/packages/TestAtlas.Mcp) | v0.1.14 |
| NuGet — CLI | [`TestAtlas.Cli`](https://www.nuget.org/packages/TestAtlas.Cli) | v0.1.14 (the layered project map) |
| Official MCP Registry | `io.github.Karzone/TestAtlas.Mcp` | v0.1.14, active |
| Anthropic Directory (Claude Code + Cowork) | TestAtlas, by Karzone | Plugin v0.1.1 live since 2026-10-03. v0.1.2 (`/testatlas:report`) and v0.1.3 (finding tests goes to the map; the session note survives `/clear`) pushed 2026-10-04; their directory scans were not checked at the time of writing |
| GitHub MCP Registry (VS Code / Visual Studio *Browse* gallery) | Karzone Test Atlas | Listed 2026-07-30 (ticket #152789 approved); one-click Install live |

Expand All @@ -29,7 +29,7 @@ Where TestAtlas is published, and the status of pending directory/registry submi

| Channel | Reference | Status | Notes |
| --- | --- | --- | --- |
| Glama | [glama.ai/mcp/servers/Karzone/TestAtlas](https://glama.ai/mcp/servers/Karzone/TestAtlas) | Release 0.1.11 published 2026-09-26 (0.1.10 on 2026-09-05). GitHub releases v0.1.12 and v0.1.13 made 2026-10-04; the auto-release build's `serverInfo` version was not checked at the time of writing | The first submission failed with an orphaned-duplicate record (resubmitted 2026-07-30); the server was then claimed and a release made. Glama ignores the repo `Dockerfile` and generates its own Debian image from the build spec on `/admin/dockerfile`: build steps install libicu, the .NET 8 SDK (dotnet-install.sh), `TestAtlas.Cli` + `TestAtlas.Mcp` from NuGet, then index `samples/SampleShop` to `/app/codemap.db`; CMD is `/root/.dotnet/tools/testatlas-mcp /app/codemap.db`; no environment variables. Glama **Auto-Release is on** (Releases tab): every GitHub release triggers a Glama build + publish. The build installs whatever NuGet's index serves at that moment, and `publish.yml` itself waits up to 15 min for NuGet, so an auto-build may run before the new version is indexed and ship the previous one — check the build log's `serverInfo` version after each release and rebuild by hand if it is stale. |
| Glama | [glama.ai/mcp/servers/Karzone/TestAtlas](https://glama.ai/mcp/servers/Karzone/TestAtlas) | Release 0.1.11 published 2026-09-26 (0.1.10 on 2026-09-05). GitHub releases v0.1.12 and v0.1.13 made 2026-10-04; the auto-release build's `serverInfo` version was not checked at the time of writing. 0.1.14 was published on 2026-10-11 by running `publish.yml` by hand (workflow_dispatch) from `main`, with no GitHub release or `v0.1.14` tag, so Glama has not auto-built it; its MCP server is unchanged from 0.1.13 | The first submission failed with an orphaned-duplicate record (resubmitted 2026-07-30); the server was then claimed and a release made. Glama ignores the repo `Dockerfile` and generates its own Debian image from the build spec on `/admin/dockerfile`: build steps install libicu, the .NET 8 SDK (dotnet-install.sh), `TestAtlas.Cli` + `TestAtlas.Mcp` from NuGet, then index `samples/SampleShop` to `/app/codemap.db`; CMD is `/root/.dotnet/tools/testatlas-mcp /app/codemap.db`; no environment variables. Glama **Auto-Release is on** (Releases tab): every GitHub release triggers a Glama build + publish. The build installs whatever NuGet's index serves at that moment, and `publish.yml` itself waits up to 15 min for NuGet, so an auto-build may run before the new version is indexed and ship the previous one — check the build log's `serverInfo` version after each release and rebuild by hand if it is stale. |
| Claude Code plugin marketplace | `claude plugin marketplace add Karzone/TestAtlas` then `claude plugin install testatlas@testatlas` | Live: the repo marketplace, and the Anthropic Directory since 2026-10-03 | The repo is its own marketplace (`.claude-plugin/marketplace.json`); the plugin is `claude-plugin/` (server with no args + skill + `/testatlas:index` + SessionStart map check). Installing clones the whole repo into the plugin cache. Submitted to Anthropic's plugin directory 2026-09-26 (claude.ai/directory/manage, source `Karzone/TestAtlas` @ main, path `claude-plugin`, listed on Claude Code + Cowork only): the first scan refused the commit ("files the scanner won't accept") because `.gitattributes` carried a raw carriage-return byte inside a comment; with that byte removed (11cc824) the scan passed and the version is In review, held on three findings (hook script calls another file, server is a PATH tool not a bundled file, name near the connector "nextatlas"). GitHub push webhook set up 2026-09-26 (repo hook 686233018, push events, JSON; ping delivered 200), so the directory scans a push within minutes. Approved by a reviewer about 2026-09-28 and published 2026-10-03 (v0.1.0, then v0.1.1 the same evening, which says when the two .NET tools are missing). v0.1.2, pushed 2026-10-04, adds `/testatlas:report` and drops the reconnect-after-indexing step, which TestAtlas.Mcp 0.1.12 makes unnecessary. v0.1.3, the same day, makes "find the tests for X" a map question: the session note also runs after `/clear` and compaction and covers finding, listing and counting tests, the skill's description says the same, and TestAtlas.Mcp 0.1.13 returns usage instructions in its handshake. Before it, an agent asked to find tests searched the feature files and called the connected server only when told to. The terminal's `/plugin` Discover tab does not search the Anthropic Directory (the CLI lists it as browse-on-claude.ai only), so terminal users add the repo marketplace; the desktop app and claude.ai find the listing by name. |
| awesome-mcp-servers | — | Unblocked | Was waiting on an installable Glama listing (see row above); PR can be resubmitted. |

Expand Down
Loading