activate_domain
Activate all tools in a domain at once. Domains: . Use reload_extensions first to include external plugin/workflow domains.
LABSCO SUMMARY
A catalog that size, without carrying it every turn.
What it takes off you is the context cost of breadth. Eight definitions stay resident on the search profile and everything else is pulled in when a task calls for it, then dropped — and the router answers is there something for this instead of leaving the model to guess.
What it is
A dynamic tool layer for JavaScript analysis and security research — browser automation and CDP debugging, network interception, JS hooks, WASM and binary work, process and memory inspection. The catalog spans dozens of capability domains, none of them resident: you search or route to what a task needs, activate it, and remove it again afterwards.
What you get
- The catalog searched by query, with the option to activate what matches
- A task described in words routed to recommended tools, in activation order, with example arguments
- One tool's full input schema read before you call it
- Tools registered by name, or a whole domain at once with a time limit on it
- Activated tools removed again to free context
- An already-active tool called by name, for clients that did not refresh their tool list
- A report of which tools have been called this run and which have not
- Domains covering browser and debugger work, network, proxy and GraphQL capture, memory, process and syscall inspection, WASM, WebGPU, sourcemaps, encoding and AST transforms
- A resident set you choose: MCP_TOOL_PROFILE=search keeps only these eight meta tools loaded, and the workflow and full profiles start with progressively more
Requirements
Node.js 22.12 or newer and npx on your PATH. The published quick start sets MCP_TOOL_PROFILE=search and npm_config_omit=optional, which skips the optional ONNX, Z3, Binaryen, Camoufox and Playwright packages — drop npm_config_omit when you need the browser and analysis runtimes those provide. The catalog is not resident, so a tool has to be found and activated before it can be called; call_tool does not activate anything by itself.
Setup effort
One command — npx -y @jshookmcp/jshook@latest
USE CASES
01
Finding out whether a capability exists at all
The catalog is searched or the task routed, so the answer to is there a tool for this comes from the index rather than from the model's memory.
02
Enabling exactly the tools one task needs
Named tools are registered, their input schemas read, and then called — without loading the domains around them.
03
Freeing context when a task is done
Tools added during the task are removed again, so the next task starts from the same small resident set.
04
Turning on a whole area of work
When a task spans a domain rather than a few calls, the domain is activated at once and expires after the time you set.
05
Seeing what you actually used
The coverage report separates the tools called this run from the ones that were never touched, across the full catalog rather than the active set.
8 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
activate_tools
Dynamically register specific tools by name, regardless of current base tier. Use after search_tools to enable exactly the tools you need. In search-tier sessions this is usually enough; you do not need boost_profile just to use a few exact tools. Activated tools appear in the tool list immediately. If tools do not appear after activation, use call_tool to invoke them directly.
call_tool
Execute an already-active tool by name. Use this when activate_tools/activate_domain registered a tool but your client did not refresh its tool list. Does not auto-activate inactive tools.
coverage_report
Report which tools have been called in the current runtime and which known tools remain uncalled. Loads all domains first so the uncalled list reflects the full tool catalog, not just currently active tools.
deactivate_tools
Remove previously activated tools to free context. Only affects tools added via activate_tools, not base profile tools.
describe_tool
Get detailed information about a specific tool, including its input schema. Use this to see the exact parameters a tool expects before calling it.
route_tool
One-stop tool router: accepts a natural language task description, returns recommended tools and next actions. Automatically detects workflow patterns, recommends activation order, and provides example arguments. Use this instead of search_tools when you want guided tool discovery with actionable next steps.
search_tools
Search 668 tools across 34 capability domains. This includes built-in tools plus any loaded plugin/workflow tools (0 currently loaded). In search-tier sessions, call this before assuming a capability is unavailable. Use activate_tools for exact matches, activate_domain for an entire domain.
BEFORE YOU INSTALL
What to know first
Tools you get
8 tools when we connected. The recommended config sets MCP_TOOL_PROFILE to search, exposing only these 8 meta tools. Without it the default workflow profile loads analysis, browser, debugger, network and other domains; full preloads all 34 domains.
Requires
npx on PATH
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @jshookmcp/jshook@latestMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"jshook": {
"command": "npx",
"args": [
"-y",
"@jshookmcp/jshook@latest"
],
"env": {
"MCP_TOOL_PROFILE": "search",
"npm_config_omit": "optional"
}
}
}
}On Windows, use the absolute path to npx.cmd if npx is not found.
