Skip to main content
Glama
230,198 tools. Last updated 2026-06-24 12:16

"Debugging and Navigating Code in a Project" matching MCP tools:

Matching MCP Servers

Matching MCP Connectors

  • Retrieve a file's contents from a QuantConnect project by specifying the project ID and file name. Omitting the file name returns all files in the project, enabling efficient code review or backup.
    Apache 2.0
  • Lists scripts in a project by ID or name, with optional filtering by space or search term. Returns script ID, name, description, and schedule type.
    MIT
  • Create multiple test cases at once in a Qase project by specifying project code and an array of case details including title, steps, and custom fields.
    MIT
  • Retrieve a specific milestone by providing the project code and milestone ID to get detailed milestone data.
    MIT
  • Retrieve the overall code health score, grade, technical debt, problem counts, and project statistics to assess codebase quality.
    MIT
  • Retrieve details of a specific test run using project code and run ID. Optionally include related entities like cases.
    MIT
  • Retrieve all configuration groups and items for a project. Use the project code to get details on available configurations for test runs.
    MIT
  • Assemble prior code, dataset variables, and cleaning steps from a project to create a new script in the user's own conventions. Call this before writing the script.
    AGPL 3.0
  • Paste a stacktrace, failing test, or diff to identify the most relevant code nodes, ranked by personalized PageRank for targeted debugging.
    MIT
  • Search for reusable code, variables, and cleaning steps by submitting a query. Optionally restrict results by project or language.
    AGPL 3.0