Skip to main content
Glama
521,490 tools. Updated 2026-09-06 11:42

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

Matching MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    Enables structured extraction of methods and reproducibility heuristics from academic papers, allowing AI agents to obtain metadata, full text, structured methods, code repository discovery, and a no-clone reproducibility verdict from a paper URL.
    8
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides MCP tool adapters for Bioconductor methods like limma, DESeq2, and fgsea, enabling statistical analysis of omics data through containerized R execution. It serves as a bridge between MCP clients and bioinformatics tools for reproducible research workflows.
    Apache 2.0

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
  • Execute asynchronous JavaScript in a stopped agent to control a browser—navigate, click, scroll, read text—and return the value. Consult app_docs to verify available $ methods before use.
    Apache 2.0
  • Retrieve Uindow SDK documentation for dollar sign ($) object methods and properties. Search by query or list all available entries to get Markdown docs with argument details and code examples.
    Apache 2.0
  • Get a token-optimized outline of a file's classes and methods with line numbers, adjustable depth from names to full signatures.
    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
  • Look up an exact symbol name to retrieve its definition, signature, methods, references, and dependencies in one JSON response. Use after a search to get deep code context.
    MIT
  • Lint and fix KCL code provided as a string or project path, returning corrected code and unfixed lint issues for review.
    MIT