What's Loaded

MCP文档知识

提供方 未标注

文档知识 stdio · 本地进程 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

在对话开始前显示占用智能体上下文窗口的内容——按token成本排名的技能描述、重复技能、记忆文件及其导入,以及每个已配置的MCP服务器。

一句话选型结论

按资料字段整理

What's Loaded 属于文档知识类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
claude mcp add --scope user whats-loaded -- npx -y whats-loaded-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
What's Loaded当前 未标注 stdio · 本地进程 本地部署 有 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

9.0 KB
来自项目仓库与上游目录的原文,未做删改

whats-loaded-mcp

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:```

Context budget — cost before you type a single character

~95,316 estimated tokens always loaded.
For scale: ~47.7% of a 200K window, ~9.5% of a 1M window.

Source Count Est. tokens
Skill descriptions 1,767 92,884
Memory files (CLAUDE.md/AGENTS.md + imports) 3 2,432
MCP servers configured 10 not measured
Total measurable 95,316

> 79 duplicate skill names are costing ~9,435 tokens.


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

| Tool | What it answers |
|---|---|
| `context_budget` | The headline: how much is loaded before you type, split by source. Start here |
| `skill_costs` | Skills ranked by token cost, so you trim where it actually pays |
| `duplicate_skills` | The same skill installed more than once — usually pure waste |
| `memory_files` | `CLAUDE.md`/`AGENTS.md` sizes **and** what their `@import` lines silently pull in |
| `mcp_servers` | Every MCP server configured across your clients, and which config declares it |

## Install

**Claude Desktop (one-click, no terminal):** download the latest `whats-loaded-mcp-.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):```bash
claude mcp add --scope user whats-loaded -- npx -y whats-loaded-mcp

Or in any MCP client config:```json
{
"mcpServers": {
"whats-loaded": {
"command": "npx",
"args": ["-y", "whats-loaded-mcp"]
}
}
}


From source```bash
git clone https://github.com/stcmain/whats-loaded-mcp.git
cd whats-loaded-mcp
npm install && npm run build
# then point your client at node /path/to/whats-loaded-mcp/dist/index.js

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.

Variable Default Meaning
WL_PROJECT_ROOT the server's working directory Directory treated as "the project" for project-scoped skills, memory files and .mcp.json.

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.json { "mcpServers": { "whats-loaded": { "command": "npx", "args": ["-y", "whats-loaded-mcp"], "env": { "WL_PROJECT_ROOT": "/path/to/the/project" } } } }

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 + description is what loads at startup. The body of a SKILL.md is 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() or cwd(). 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.md routinely 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

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
What's Loaded 怎么安装?

在客户端按下面的安装命令接入:claude mcp add --scope user whats-loaded -- npx -y whats-loaded-mcp。装完在客户端配置里引用同一个包或端点。

What's Loaded 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

What's Loaded 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

What's Loaded 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

What's Loaded 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Gemini CLI;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

What's Loaded 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

What's Loaded 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

What's Loaded 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。