Ext Ops Panel
Open dashboard
Comparison

token-wise vs LLMKit

token-wise is a plugin bundle for AI coding tools published by vivek-cactus. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). LLMKit is an MCP server published by OlsOls4. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacetoken-wiseLLMKit
Claude Code: claude-plugins-community Listed
Version: 7d2d736
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

token-wise vs LLMKit
Facttoken-wiseLLMKit
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (llmkit-token-counter-rag-chunker-json-repair.p.rapidapi.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)13Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/vivek-cactus/token-wisegithub.com/olsols4/webkit-api
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-10-14
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

token-wise

In its own words, on Claude Code: claude-plugins-community:

A Claude Code plugin that routes text-heavy tasks to the right Claude model — saving tokens without sacrificing quality. Why Planning, CLAUDE.md generation, README writing, and PRDs don't need Opus when you're just structuring content. token-wise intercepts these tasks and runs them on Sonnet or Haiku instead, switching back to your session model automatically when done.

LLMKit

In its own words, on Official MCP Registry:

Token counting, RAG chunking, truncation, HTML to Markdown and JSON repair

How to run each

token-wise As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install token-wise@claude-community

LLMKit As a remote MCP server

Claude Code
claude mcp add --transport http llmkit https://llmkit-token-counter-rag-chunker-json-repair.p.rapidapi.com/mcp --header "X-RapidAPI-Key: <YOUR_X_RAPIDAPI_KEY>" --header "X-RapidAPI-Host: <YOUR_X_RAPIDAPI_HOST>"

Requires: X-RapidAPI-Key header, X-RapidAPI-Host header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: token-wise · What it can do: LLMKit · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built