
What's Loaded
io.github.stcmainPublished by GitHub account stcmainv0.2.5Updated Oct 24, 2026
What fills your agent's context window before a session starts: skill descriptions, memory files.
Overview
A local MCP server that reports what fills an AI agent's context window before a session starts, ranked by estimated token cost.
- What you can do
- Report the total estimated context budget, split by source, as the starting point for review. Rank installed skills by token cost so trimming targets the most expensive ones. Find skills installed more than once, separating byte-identical copies from same-name skills with different content. Measure memory files such as CLAUDE.md and AGENTS.md, including what their import lines pull in. List every configured MCP server across supported clients and which config file declares it.
- When to use it
- Useful when sessions seem to compact sooner than they used to, or when you have installed many skills, plugins and memory files and want to know which ones cost the most context. Also handy for auditing which MCP servers are configured across Claude Desktop, Cursor, Windsurf and VS Code.
- Requirements
- Runs locally over stdio, typically via npx or a bundled desktop extension. Node.js is needed for the npm route; the desktop bundle ships its own dependencies. No credentials or API keys. One optional setting, WL_PROJECT_ROOT, sets the directory treated as the project. Reads Claude Code layout under the home directory and JSON client configs.
Installation
In SourceWeft
- Open What's Loaded in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
whats-loaded-mcp
[npm] [License: MIT] [stcmain/whats-loaded-mcp MCP server]
Your context window is already half spent before you type. An MCP server that shows what is consuming it — every skill description, every memory file and its hidden @imports, every configured MCP server — ranked by cost, with duplicates called out.
Why
Skills are cheap to install and permanently expensive to keep. A skill's name and description go into the system prompt of every session, forever — only the body is loaded on demand. Install a few hundred and you've quietly mortgaged half your window before the first message.
Nothing surfaces this. You notice it as sessions that compact sooner than they used to, and you have no idea which of the things you installed six months ago is responsible.
On the machine this was written on:
79 names were installed more than once — the same skill picked up from several sources, like agent-browser appearing three times from three authors. But a shared name does not always mean a redundant copy: on that install only 34 groups were byte-identical (~1,523 tokens genuinely recoverable), while 45 shared a name and differed in content — different work wearing the same label, where deleting a copy loses something. duplicate_skills compares content hashes and reports those two groups separately, so the cleanup advice is safe to act on rather than merely impressive.
Tools
Install
Claude Desktop (one-click, no terminal): download the latest whats-loaded-mcp-<version>.dxt from Releases and open it with Claude Desktop (double-click, or Settings → Extensions → Install Extension…). The server and its dependencies ship inside the bundle — no npm, no Node install.
Register with Claude Code (available in every session):
Or in any MCP client config:
From source
Published as whats-loaded-mcp on npm and as
io.github.stcmain/whats-loaded-mcp in the MCP Registry.
Configuration
One optional setting, and it takes no credentials.
Personal and plugin scopes are read from ~/.claude either way. Setting this is
worth it when a desktop client launches the server: the process inherits that
client's working directory, which is rarely the project you are asking about.
What it counts, and what it refuses to guess
Getting this wrong in the flattering direction would be easy, so the accounting is deliberately conservative:
- Skill descriptions only.
name+descriptionis what loads at startup. The body of aSKILL.mdis fetched on demand and is not counted, even though it is 100× larger. - Enabled plugins only. Skills belonging to disabled plugins sit on disk costing nothing, and are reported separately rather than folded into the total.
- One version per plugin. The plugin cache keeps several content-hash copies of the same plugin; only the live one is counted. Counting them all would inflate the total and invent duplicates you cannot act on.
marketplaces/is never counted. That tree is a git checkout of marketplace source, not installed content.
Honest limitations
- Token counts are estimates (~4 chars/token). Real counts depend on the tokenizer; prose runs lighter, code and CJK run denser. Treat the numbers as a ranking and a rough scale, not as billing. Anthropic's tokenizer is not public, so nothing local can do better than an estimate.
- MCP tool definitions are not measured. They can be a large share of your context, but measuring them means launching every server and enumerating its tools. This server does not launch anything, so it reports the server count and says so rather than guessing.
- JSON configs only. TOML-based clients (Codex
config.toml) are not parsed. - Client-specific. Built around the Claude Code layout (
~/.claude). The MCP inventory reads Claude Desktop, Cursor, Windsurf and VS Code configs too, but skill accounting is Claude Code's model. - It reports; it does not edit. Nothing is deleted, disabled or rewritten. Acting on the findings is your call.
Design notes / threat model
This server's output goes straight into a model's context, so the interesting risk is not what it does to your machine — it is what it hands to the model.
- No child processes. No network. It only reads files. There is no
exec, no shell, and no outbound connection anywhere in the codebase. - No model input ever becomes a path. Every path is derived from
homedir()orcwd(). The only model-controlled parameters are a clamped integer and a substring matched in memory against names already collected. Path traversal is not possible because there is no path construction to traverse. - Memory file contents are never read into the report.
CLAUDE.mdroutinely contains private operational detail. This server reports size and the import graph, never a line of content. - MCP environment values are never read. Config files are where people leave API keys in plaintext. Only variable names are emitted — never values, not even masked.
- Skill names and descriptions are emitted, which is a deliberate exception: they are already in the model's context by definition, so reporting them discloses nothing new.
- Bounded work: depth-capped directory walks, symlink-loop protection via realpath, and a file size ceiling.
Who makes this
Built by Shift The Culture — we run a one-person company on AI agents and ship the tooling we needed ourselves. This server is free and MIT-licensed, no strings.
It has three siblings, all also free and MIT:
- whats-running-mcp — what is actually running on the box right now, instead of what an old transcript claims.
- whats-inherited-mcp — what a checkout you did not write tells your agent to do: instruction files, hooks, and the MCP servers it declares.
- whats-allowed-mcp — what your agent can do without asking you: merged permission rules, which settings file wins, and the rules your client accepts and then ignores.
The rest of that tooling is paid:
- Agent Fleet Ops Kit ($29) — the other failure modes of running three or four agents on one box: two sessions editing the same checkout, a dev server nobody owns (so the agent tests a different app than it edits), and MCP servers leaked from crashed sessions that hold ports and RAM for weeks. Prefer PayPal? Same kit on Payhip.
- Agent Reliability Kit ($29) — a Stop hook and two CLIs that block a turn when an agent claims "done" against a repo, URL, or build that was never actually checked. Prefer PayPal? Same kit on Payhip.
The server above stays free and MIT either way — it has no upsell in it, no telemetry, and no dependency on the paid kits.
Sponsors
This server is MIT and stays MIT. There is no pro edition, no telemetry, and nothing held back from the free build. Sponsorship is how the maintenance gets paid for without any of that changing.
No sponsors yet — the first slot is open. Company sponsors get their name or logo in this section, in the two sibling servers, and on the sponsor page. Tiers, exactly what the placement is, and what it explicitly does not buy: https://shifttheculture.media/sponsor
Individuals: https://paypal.me/ShiftTheCultureLLC — any amount, no perks, no tier.
License
MIT © Zachary Pampu
Source: README.md at commit 7342b8a
Tools
0Version history
1- v0.2.5LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts