Skip to main content
Glama
674,844 tools. Updated 2026-10-18 23:33

"Techniques for Analyzing Typescript Code in a Project" matching MCP tools:

Matching MCP Servers

  • F
    license
    Not graded
    quality
    B
    maintenance
    Enables any MCP-compatible AI assistant to search, filter, and retrieve information from a local document collection using a hybrid search pipeline with vector, BM25, reranking, and LLM enrichment.
    4
    -

Matching MCP Connectors

  • Scans a TypeScript or JavaScript project to identify unused imports, variables, and exported functions without cross-file references. Results are stored for automatic removal.
    ISC
  • Retrieve available code fixes for specific error codes at a defined range in a TypeScript or JavaScript file. Uses diagnostic error codes and range to return tsserver's suggested code actions.
    MIT
  • Verify TypeScript code correctness by running type-checking on a specified service path, receiving structured error details for pre-commit validation.
    MIT
  • Retrieve all diagnostics for a TypeScript/JavaScript file in a tsconfig project, including errors, warnings, and suggestions for type errors, unused code, and imports.
    MIT
  • Sort, coalesce, and remove unused imports in TypeScript or JavaScript files. Uses TypeScript's native organizeImports to clean up import statements for files in a tsconfig.json project.
    MIT
    Destructive
  • Find the best Context Engineering technique for your task. Filter by reasoning, workflow, code, project, or all to get a tailored guide.
    MIT
  • Retrieve exploit source code by platform ID to analyze attack techniques, understand exploit mechanics, or review PoC code.
    MIT
  • Scan project files to build a code graph: extracts definitions and resolves call/import relationships across Python, TypeScript, and JavaScript. Use force for a full rebuild or view indexing stats.
    MIT
  • Run TypeScript compiler diagnostics on selected JavaScript or TypeScript files using local project settings and declarations to catch type errors before runtime.
    MIT
  • Parse a repository to build its code graph in Neo4j for analyzing dependencies and change impact. Re-index after changes; unchanged files are skipped by content hash.
    MIT
  • Expands TypeScript macros and @derive decorators to show generated code with diagnostics for debugging and understanding transformations.
    MIT
  • Analyze TypeScript code quality by calculating cyclomatic complexity and lines of code per function or file. Identify complexity hotspots across a project or in a specific file.
    Apache 2.0