Skip to main content
Glama
383,189 tools. Last updated 2026-08-03 07:48

"Methods for Analyzing Code in a Project" matching MCP tools:

Matching MCP Servers

Matching MCP Connectors

  • Automatically generate or update documentation for code changes, including new methods and changed signatures, by scanning your local project.
    MIT
  • Provides code completion suggestions for Svelte development by analyzing symbols to reveal available members, methods, and types.
    MIT
  • Initialize indexing for a project by scanning source files to build a searchable index of code identifiers, methods, types, and signatures.
    MIT
  • Generate an OpenAPI specification by analyzing framework source code, removing the requirement for a standalone spec file.
    MIT
  • Delete a project file by UUID, permanently removing it and all its methods/statements. This action is destructive and irreversible.
    MIT
  • Retrieve the assembled source code for a file to verify that methods, handlers, imports, and reactive state are correctly built after saving. Use this to validate your component before deployment.
    MIT
  • Lint and fix KCL code by providing a code string or project path, returning corrected code and a list of unfixed issues.
    MIT
  • Retrieve the currently active project in ZenML to establish the default organizational context for managing pipelines, stacks, and resources.
    MIT
  • Search SDK documentation to discover methods, parameters, and usage examples for interacting with the API. Use before writing code to find the right approach.
    MIT
  • Identifies unused functions and classes in your codebase by analyzing call graphs and import dependencies, filtering out common false positives like dunder methods and entry points.
    MIT
  • Check censorship risk for a domain in a specific country by analyzing the country's censorship profile, including anomaly rate, affected services, and blocking methods.
    MIT