JsHookMcp

by vmoranv

2.5k downloads Not rated yet

GitHub Website

About

The js hook toolkit that all you need

Explore

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name JsHookMcp

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "jshookmcp": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@jshookmcp/jshook"
                ]
            }
        }
    }
}

McpServers

{
    "server": {
        "command": "npx",
        "args": [
            "-y",
            "@jshookmcp/jshook"
        ]
    }
}

Transport

"stdio"

Package

"@jshookmcp/jshook"

Registry

"npm"

- 📖 Documentation·🚀 Getting Started·⚙️ Configuration·📚 Tool Reference

No global install needed — add to your MCP client config and you're ready:

Claude Desktop / Cursor (claude_desktop_config.json):

{ "mcpServers": { "jshook": { "command": "npx", "args": ["-y", "@jshookmcp/jshook@latest"], "env": { "MCP_TOOL_PROFILE": "search", "npm_config_omit": "optional" } } } }

(Windows: usenpx.cmdabsolute path ifnpxis not found)

This lightweight configuration skips optional ONNX, Z3, Binaryen, Camoufox, and Playwright packages. Removenpm_config_omitwhen those full-profile runtimes are required.

The default stdio configuration starts one full jshook process per MCP host. To share the embedding model, browser runtime, and caches, start one local Streamable HTTP daemon:

Vector search defaults to off for per-client stdio processes and on (lazy-loaded) for the shared HTTP daemon. SetSEARCH_VECTOR_ENABLED=falsewhen lexical search is sufficient.

Then point every MCP client athttp://127.0.0.1:3000/mcpusing its HTTP/URL server configuration. Each client receives its own MCP session and response route while heavyweight runtime resources remain in one process. Keep the default loopback bind; setMCP_AUTH_TOKENbefore exposing the endpoint beyond localhost.

- 🤖AI-Driven Analysis— LLM-powered deobfuscation, crypto detection, AST comprehension
- ⚡Search-First Context Efficiency—searchprofile ≈ 3K tokens vsfull≈ 40K+ tokens
- 🎯Progressive Tiers—search→workflow→full, activate on demand
- 🌐Full-Stack Browser Automation— Chromium/Camoufox + CDP + anti-detection + CAPTCHA handling
- 🔁Runtime Recovery and Session Isolation— HTTP sessions restore activated domains, browser attach state, coverage state, and isolate browser-side session state per client
- 🧭Schema-First Meta Tools—describe_tool, validatedcall_tool, andcoverage_reportreduce parameter errors and make tool coverage visible
- 📡Network Interception— HTTP/2 frame building, MiTM capture, GraphQL, Burp Suite bridge
- 🛠️Reverse Engineering Toolchain— WASM disassembly, binary analysis, Frida, Ghidra/IDA bridges
- 🧰Process & Memory Forensics— Native FFI scanning, hardware breakpoints, PE introspection
- 🧩Dynamic Extensibility— Hot-reload plugins, declarative workflows, auto-discovered domains

- HTTP transport now multiplexes independent MCP sessions and restores runtime state after reconnects.
- proxy_startauto-generates a local HTTPS interception CA when needed.
- Browser CAPTCHA solving is now explicit-input driven: passtaskKind,siteKey,imageBase64,callbackName, andresponseSelectoras needed. Built-in widget/page signature probing is intentionally not used.

- Runtime Registry— Domains auto-discovered viamanifest.ts; add a domain by creating one file
- Lazy Initialization— Handlers instantiated on first call, not at startup
- BM25 + Vector Search—search_toolsmeta-tool with hybrid ranking and adaptive weights
- MCP ToolAnnotations— Every tool carriesreadOnlyHint/destructiveHint/idempotentHint/openWorldHint

The built-in surface below is generated from the runtime registry and checked in CI.

- Package version:0.3.5
- Built-in Tools:668
- Domains:adb-bridge,binary-instrument,boringssl-inspector,browser,canvas,coordination,core,cross-domain,dart-inspector,debugger,encoding,exploit-dev,extension-registry,graphql,instrumentation,maintenance,memory,mojo-ipc,native-bridge,native-emulator,network,platform,process,protocol-analysis,proxy,sourcemap,streaming,syscall-hook,trace,transform,v8-inspector,wasm,webgpu,workflow
- Note: this snapshot is generated from the runtime registry; do not edit the counts by hand.

Official Playwright MCP server for browser automation, page inspection, screenshots, and web interaction from Claude, Cursor, and other AI agents.

Render website screenshots with ScreenshotOne

Attaches to existing browser sessions using the Chrome DevTools Protocol for automation and interaction.

Help your AI agent finish more browser tasks.

Automate remote browsers using the BrowserCat API.

Remote browser automation using the BrowserCat API.

Take screenshots and read console logs from web pages using Playwright.

Automate browser tasks using the Browser Use API.

A Node.js server that enables AI assistants to control the Chrome browser via WebSocket. Requires the CodingBaby Chrome Extension.

A configurable MCP server for browser automation using Puppeteer.

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Explore

Setting up with Highlight

Claude Desktop / Cursor

McpServers

Transport

Package

Registry

More like this

@mendableai/firecrawl Mcp Server

Playwright

Sentry

Github