Your Claude Code setup,
on one page.

Claude Storehouse is a free local dashboard. It shows every skill, agent, plugin, hook, MCP server, setting, and CLAUDE.md for your global ~/.claude and for your project. Switch them on or off in one click.

Try the live demo

1 command, any folder
1 runtime dependency
0 data leaves your machine
20 backups kept per file

Claude Storehouse dashboard: API-equal cost, token usage by model, counts for skills, agents, plugins, hooks and MCP servers, favorites, and project files

Skills page with an on/off switch, a star, and the file each switch writes

Live demo

Click around the real dashboard

This is the real app code, running in your browser with a sample setup. Switches, stars, and edits change only this page. Reload to start again. Things to try:

Switch api-design off on Skills, then undo it on the Activity page
Drag a favorite into the Review category
Open CLAUDE.md, edit it, and press ⌘S
Press / and type review
Switch the toolkit plugin off and look at its skills
Open Settings, then Effective: model comes from the local file

Open full screen ↗

127.0.0.1 · Dashboard

On a phone the demo is small. Open it full screen, or try it on a computer.

Features

Everything `/plugin` and raw JSON do not show you

Dashboard and usage

One look at your whole setup: how many items are on and off, your favorites, recent changes, and which Claude Code files this project has.

API-equal cost of your Claude Code use, by model
Tokens, sessions, projects, and prompt-cache savings
Reads token counts and tool names, never prompts or message text
Counts for skills, agents, plugins, hooks, and MCP servers

Open the Dashboard in the demo →

Dashboard with an API-equal value band, token totals, item counts, favorites, and the project file list

Skills and agents

Global, project, and plugin skills and agents in one list. Each switch shows the file it writes before you click, and a toast names the file after.

Filter by scope and press / to search
Use in the last 30 days, an Unused filter, and a sort by use
Plugin skills show "via plugin X" and follow their plugin
Fork a plugin skill to ~/.claude/skills

Try the switches →

Skills page with switches, 30-day use chips, an Unused 30 d filter, a sort by use, and a banner to switch off unused skills

Favorites

Star the skills, agents, and plugins you use most. Group them in your own categories and drag them into order.

A favorite stays in the list when you switch it off
A favorite whose item is gone shows "missing"
Rename and delete a category, with undo
Stored in ~/.claude/storehouse.json

Drag favorites in the demo →

Favorites page with items grouped into Plan, Build, and Review categories

Plugins and mods

Every installed plugin with its marketplace, version, skills, agents, hooks, and MCP servers. Switch a plugin off and all its parts go off with it.

Uses enabledPlugins, the key Claude Code reads
Uninstall runs claude plugin uninstall with the right scope
Mods page: installed mods and mods in development

Open Plugins in the demo →

Plugins page with three plugins from two marketplaces, their versions, and on/off switches

Hooks and MCP servers

Hooks from every settings file and plugin, by event and matcher. MCP servers from ~/.claude.json, .mcp.json, and plugins, with secrets masked.

Switch a hook off: it parks safely and comes back on undo
MCP switches use Claude Code's own disable lists
Add a hook or an MCP server from a form

See MCP servers in the demo →

MCP servers page with transport, command, source, masked environment values, and 30-day use for each server

Edit in place, undo anything

Open any file you own in the drawer: a skill, an agent, settings.json, or CLAUDE.md. Edit it and save with ⌘S. The CLAUDE.md page lists each CLAUDE.md that Claude Code loads in this folder and creates a missing one.

Every switch, star, and save shows on the Activity page with Undo
The latest save of each file can be restored
Plugin cache files stay read-only
A JSON file that does not parse is never written

Edit CLAUDE.md in the demo →

A skill open in the drawer editor with its file path and the Save button

Find duplicates

The Duplicates page groups skills, agents, and MCP servers that use the same name, so you know which one Claude Code loads.

Conflict when more than one item in a group is on
Keep only this switches off the others in one click
Plugin items name the plugin that controls them

Find duplicates in the demo →

Duplicates page with two same-name groups, each marked Conflict, and a Keep only this button on each item

See context cost

The Context page estimates how many tokens each item adds to every session before you type a word, and sorts the biggest first.

CLAUDE.md files, rules, skill and agent descriptions
An Off chip shows what each switched-off item saves
Switch an item off and the total goes down
A token chip on the Skills and Agents pages

See context cost in the demo →

Context page with the tokens loaded in every session, a bar by type, filter chips, and items sorted by tokens

Check your setup with Doctor

Doctor finds config that is broken or that does not do what it says. Claude Code often fails on these without a message.

Invalid JSON, missing hook scripts, MCP commands not on your PATH
Unset ${VAR} names, stale plugin and skill keys, same-name conflicts
Each row opens the file or the item
Read-only: it never writes a file or runs a command

Run Doctor in the demo →

Doctor page with Errors, Warnings, and Info filter chips and warning rows, each with an Open button

Settings, and which file wins

Three files can set one key. The Settings page shows one file at a time, and the Effective view shows the value Claude Code uses in this folder.

One form for the global, project, and local file, with plain names and help
Effective view: the value that wins, its file, and the values it overrides
Lists such as permissions.allow add up from all files
Env values that look like secrets are masked

See which file wins in the demo →

Settings page, Effective view: a table of keys with the value Claude Code uses, the file it comes from, and crossed-out values from lower files

How on / off works

The keys Claude Code itself reads

Native switches. Plugins, skills, and MCP servers use the keys that Claude Code reads. The dashboard never says "off" while Claude still loads the item.

Scope-safe. Global switches write ~/.claude/settings.json. Project switches write .claude/settings.local.json, never the shared settings.json.

Safe writes. Each write copies the old file to a backup first, writes a temp file, then renames it. Changes apply at the next session.

PluginenabledPlugins[id] = false

SkillskillOverrides[name] = "off"

MCP · .mcp.jsondisabledMcpjsonServers

MCP · globalprojects.<dir>.disabledMcpServers

Hookparked in storehouse.json

Agentname.md → name.md.disabled

✓

Wrote ~/.claude/settings.json · backup savedThe toast after each switch names the file that changed.

Install

Ready in one command

No install step, no account, no config. You need Node 20 or newer.

claude-storehouse

Latest on npm

npm · Releases · What is new

Install it once instead

npm i -g claude-storehouse
claude-storehouse

Then run claude-storehouse in any project folder.

Check Node

Claude Storehouse needs Node 20 or newer. Claude Code users have it already.
Open your project folder

The dashboard shows the global ~/.claude and the project in the current folder.
Run the command

npx downloads the package and starts a server on 127.0.0.1.

npx claude-storehouse
Use the page, then stop

Your browser opens on a local address with a one-time token. Press Ctrl+C in the terminal to stop.

CLI options

`--dir <path>`	Project folder to manage. Default: the current folder.
`--home <path>`	Folder that holds `.claude`. Default: your home folder.
`--port <n>`	Port to listen on. Default: a free port.
`--no-open`	Do not open the browser.
`--help`, `--version`	Print usage or the version.

Keyboard shortcuts

`/`	Search names and descriptions
`⌘S` / `Ctrl+S`	Save the open file
`⌘B`, `⌘I`	Bold and italic in the editor
`Esc`	Close the drawer or a dialog
`↑` `↓` `Home` `End`	Move between items in a list

Safety and privacy

No server outside your machine, no account, no analytics. Session files give only token counts, tool names, and the skill, agent, or MCP server name of each call. Never prompts or message text.

Backups	Each write copies the old file to `~/.claude/backups/storehouse/`. The last 20 per file stay.
Local only	Listens on `127.0.0.1` and rejects a foreign `Host` header.
Token	Every API call needs the random token from the start URL.
Doctor	Reads only. It never writes a file or runs a command, and it shows env key names, never values.
Env	The Effective view masks env values that look like secrets before they leave the server.
Allow-list	Writes go only to `~/.claude`, `~/.claude.json`, and the project folder.
Delete	Moves the file to a trash folder. Restore it from the Backups panel.

Your Claude Code setup,on one page.