npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

claviz-ai-tools

v0.0.14

Published

Tools and guides that let AI assistants work in Claviz over MCP.

Readme

claviz-ai-tools

Tools and guides that let AI assistants work in Claviz over MCP.

What's inside

  • Building: find, read, validate and save entities (also in bulk), preview functions, look up typings, manage branches and merges.
  • Apps: list apps and inspect their screens and components.
  • Facts: find, read, summarize, create, update and delete facts, and read their history.
  • Diagnosis: executions, execution logs and running work.
  • Access: users, user groups, roles and who can use what.
  • Add-ons: list, install, update, uninstall and publish add-ons.
  • Connection: who the connected user is and which AI tools they can use.
  • Guides and code examples the AI reads before it works.

Other add-ons can bring their own AI tools and guides; their AI tools build on this add-on.

Setup

  • Needs a Claviz version with MCP: AI clients connect at <your Claviz URL>/mcp.
  • Claviz AI needs this add-on: until it's installed on a branch, AI clients are told that AI isn't set up there.
  • Every tool except Current user and connection status is for administrators until you give groups access to it. Access stays with each Claviz: updates keep it.
  • Tools act as the connected user: they change entities only on the user's working branch and merge only after the user agrees.

Changelog

0.0.14 (19.11.2026)

  • Install or update add-on goes to the newest version this Claviz can install when no version is named. When npm's latest needs a newer Claviz build, the preview names it as held back with what it needs, instead of refusing the update. Any version this Claviz can install can be named, an older one too; going back says what it undoes. Needs Claviz build 2026.11.19.1146 or newer; older ones refuse this version.
  • Get add-ons and Get add-on show the installable version next to npm's latest, the latest version when it is held back, and for each listed version what it needs when this Claviz can't install it. Get add-on compares an entity with any version named.
  • Tests stored in the add-on cover it (AI tools › Tests › Tests: add-ons).

0.0.13 (17.11.2026)

  • Merges by AI say who may see the release: Create, switch or merge branch takes releaseVisibility (everyone, group or admin) and, for a release for user groups, releaseUserGroupIds. There is no default, so AI asks the user with the merge. Earlier versions stored a visibility Claviz didn't know, which showed those releases to administrators only. Needs Claviz build 2026.11.17.1332 or newer; older ones refuse this version.
  • Tests stored in the add-on cover it (AI tools › Tests › Tests: branches and merges).

0.0.12 (16.11.2026)

  • Take master's changes: when master changed entities a branch left alone, a merge by AI says so and waits. Create, switch or merge branch gives the branch master's copies of them (takeMasterChanges), so the work can be checked against them before the merge, and Get branches and changes lists them with the branch's changed entities that use them. Needs Claviz build 2026.11.16.1541 or newer; older ones refuse this version.
  • Conflicts (entities changed on both sides) no longer need the merge page. Get branches and changes shows what master and the branch each changed since the branch took the entity; the building guide says how AI sorts conflicts, settling the simple ones together after one yes and the others one by one; and a merge takes the agreed copies (conflictChoices), refusing a choice made for copies that changed since.
  • Tests stored in the add-on cover it (AI tools › Tests › Tests: branches and merges).

0.0.11 (16.11.2026)

  • The components guide says to debounce continuous events (pointer, mouse and touch moves, scroll, wheel) instead of sending each one to the server.

0.0.10 (12.11.2026)

  • Publish add-on can say which Claviz build a version needs (requiredBuild): instances on an older build refuse to install it. The preview shows the build the version will need and the build of this Claviz, and a publish keeps what the latest version needs. Needs a Claviz that has builds (2026.11.12 or newer); older ones refuse this version.
  • Current user and connection status says which Claviz it is connected to: its version, its build (the date of its code) and its engine's build.
  • The add-ons guide says when to raise the build a version needs, and that an instance refusing an update for it has its Claviz updated first.

0.0.9 (11.11.2026)

  • Run stored tests and Get stored test run: snippets with extension spec.ts are tests stored in Claviz. AI lists them, runs them on a test runner with a copy of the working branch (entities with access, user groups, roles, KeyVault, packages and users; no facts) and follows the results. The runner's token is entered in the Function explorer's Tests tab, never through AI. Needs a Claviz that runs stored tests; older ones refuse the run.
  • A new guide, Stored tests, says what a test must bring itself: its facts, the setup functions an add-on relies on, and the background functions it starts. The entities, add-ons and read-first guides point to it.
  • Get element and package typings reads claviz-e2e too, the fixtures and helpers stored tests import.
  • When the user's test runner is ready (address and token saved, and it answers), AI writes stored tests for what it builds, keeps them in a Tests folder next to the work, and runs them. Without a ready runner it verifies as before and doesn't push the user to set one up. Get stored test run says whether the runner is ready.
  • Tests stored in the add-on (AI tools › Tests): reading and writing through the AI tools, members' rights, hidden secrets, and the add-on tools matching Claviz's own add-on API. They moved here from Claviz's own test suite.

0.0.8 (06.11.2026)

  • Export facts and Import facts copy facts 1:1 between Claviz instances or branches through the AI client: the same ids, so links between facts keep working, and the same fields, secrets included. Owners stay when the person is a Claviz user there. Large facts travel in parts. Import works like Claviz's fact import, runs its dry run first and writes nothing if one fact is refused; administrators can import without validation after the user agrees. Needs a Claviz whose fact import keeps new ids and has a dry run.
  • The guides no longer say entities move between instances only through add-ons: a one-off copy through the AI tools of both instances is fine.
  • The functions guide says ClavizClient takes a token with or without the Bearer prefix.
  • Working in Claviz: administrators are trusted, so when a rule or tool blocks what one asks for, AI explains the block and the options instead of working around it. Only tools that change entities or preview functions ask for guideAck.

0.0.7 (05.11.2026)

  • Get typings says what a search leaves out: each file counts its matching lines that aren't shown, the package's own files come first, and the results are paged.
  • Listing a package's typings shows its own declaration files and counts its dependencies' files per package, instead of 300 files that were mostly dependencies; for a package typed separately, such as mssql, it names the @types package.
  • The functions guide says which ClavizClient methods every signed-in person may call and which need an administrator, and how to show people by name with getUserList.
  • Get entity pages through everything that uses an entity (usedByOffset), and each entry counts the lines and paths it doesn't show.
  • Preview function says how many earlier log entries it left out and gives the execution id that has them all. Each entry keeps 10,000 characters instead of 2,000, since one entry can hold a second's worth of console output, and says how many more there were.
  • Execution logs keep 10,000 characters of each value and say how many more there were; when they leave older events out, they say how to get them.
  • Get add-on shows every changelog entry an update brings and counts the entries and versions it leaves out.
  • Validation says how many syntax errors it doesn't list, and which stored components a large change uses it didn't check. The hint that functions can't hold JSX comes only with scripts that have JSX tags.
  • Find entities shows a long matching line around the match.

0.0.6 (05.11.2026)

  • The tools and guides cover collection fact access: Explain access names the facts each right covers, and the guides describe rules and the rights table.
  • Validating and saving entities list who gains or loses which facts and the rule and right changes, as Claviz's save preview does.
  • The guides say that rules can't limit what an edit changes, and how a validation script checks that against the stored fact.
  • After access changes, the tools offer a check as a member with Administrator access off before the merge (with the branch's facts), and a non-administrator retest after it.
  • Current user and connection status says when Administrator access is off: Claviz then treats the administrator as a member, with only the tools their user groups give.
  • Explain access works out each person's fact rights from all their roles together, as Claviz does; updating and deleting facts follow Claviz's canUpdate and canDelete.
  • Saving a whole collection keeps its fact access when the change leaves it out.
  • Collections have no privileges: their rights table alone decides who opens them and which facts each role gets, and only Claviz administrators change owners. Claviz gives existing collections their table when it updates. Explain access, Get entity, saves, bulk edits and the guides follow it; a change that gives a collection privileges is refused.
  • A new collection is reported as closed until it has user groups and its rights table gives their roles View or Add.
  • Access changes leave out app and function privileges without roles, as Claviz stores none, and rights table cells that grant nothing, such as a change owner cell from before; screens still show privileges without roles, since there they mean administrators only.

0.0.5 (03.11.2026)

  • Scripts saved by AI keep the line endings they were stored with, so the branch diff shows only the changed lines.

0.0.4 (02.11.2026)

  • Switching branch by AI checks that the target branch has claviz-ai-tools, also from master, so the AI can't lock itself out.
  • Merges by AI and Get branches and changes show an add-on uninstalled on the branch as one line.
  • Explain access lists no AI tools on a branch without claviz-ai-tools.
  • The add-on tools ask not to retry uncertain writes and finish within an MCP call; the publish preview also checks the changelog and description for secrets.
  • The guides describe how updates keep moves, moved-out entities and other add-ons' entities, and the 100 KB result limit.
  • The shared helpers tell other add-ons' AI tools whether anything was hidden (redacted).

0.0.3 (02.11.2026)

  • Merges by AI write release notes like the Claviz merge page: one line per add-on update, then the branch's own changes.
  • Get branches and changes lists an add-on installed or updated on the branch as one entry.
  • Add-on reads say when a version published from here is still waiting for npm, and uninstalling claviz-ai-tools warns that Claviz AI stops.
  • The orders utilities example points to claviz-ai-tools' shared helpers.

0.0.2 (02.11.2026)

  • Add Current user and connection status, which used to come with Claviz Web.
  • Add the add-on rules to the guides: add-ons are self-contained, and only their AI tools may build on claviz-ai-tools.

0.0.1 (01.11.2026)

  • First version.