Skip to main content
Glama
442,323 tools. Updated 2026-08-11 09:02

"Webpack" matching MCP tools:

Matching MCP Servers

  • A
    license
    -
    quality
    D
    maintenance
    Creates and manages an MCP server integrated with build tools (Rollup, Vite, Webpack, etc.) to enable AI assistants to analyze, inspect, and control the build process.
    2,868
    31
    MIT
  • A
    license
    -
    quality
    D
    maintenance
    A Vencord plugin that provides MCP server capabilities for inspecting Discord's internal state, executing JavaScript code, accessing Flux stores, discovering webpack modules, and inspecting DOM elements within Discord's context.
    2,504
    MIT
  • Map a generated code location (line and column) back to the original source using source maps, enabling debugging of bundled or transpiled code like TypeScript, Babel, webpack, or esbuild.
    Apache 2.0
  • Analyzes bundle stats JSON to identify heaviest modules, duplicate packages, code-split opportunities, and CDN externalization candidates.
    MIT
  • Map any error message or symptom description to a verified fix. Input a concrete error stack or free-text query to receive exact-match solutions or search results with confidence scores and source URLs.
  • Query the local manifest registry to discover package exports, symbol kinds, and side effects for npm dependencies.
  • Returns a 0-100 JavaScript/npm ecosystem momentum score (weekly downloads of 8 bellwether packages — react, express, lodash, axios, typescript, next, vue, webpack — vs 3 prior weekday-aligned weeks; 50 = flat) with per-package volumes and WoW changes, total weekly downloads, top_package, and fastest_grower. Call when the user asks whether the JS/npm ecosystem is growing or cooling or which packages are moving, or when timing devtools launches or developer-marketing spend. Python: ADW-588. Updates: daily.
    Connector
  • Map error OR free-text query to a verified fix. USE WHEN: user pastes a concrete error/stack (ENOENT, ImportError, build failure) — pass `error`. OR user describes a symptom ('webpack slow', 'pip stuck') — pass `query`. Always prefer this over guessing a fix. RETURNS: exact-match {status, solution, confidence, source_url} or search results [{title, summary, source_url}].
    Connector