Skip to main content
Glama
204,280 tools. Last updated 2026-06-14 23:34

"Using a TypeScript codebase as context for a tool or service" matching MCP tools:

  • Refresh codebase context by analyzing React/TypeScript/Node.js projects and generating structured bundles with component summaries, dependency information, and a snapshot ID for AI-assisted analysis.
    MIT
  • Returns a TypeScript snippet to mark a transaction as delivered (IN_PROGRESS → DELIVERED) after specifying the deliverable. Running the code triggers the requester dispute window.
    Apache 2.0
  • Generate TypeScript schema definitions from JSON files or URLs to validate data structures and reduce context size in LLM applications.
    MIT
  • Verify TypeScript code correctness by running type-checking on a specified service path, receiving structured error details for pre-commit validation.
    MIT
  • Retrieve Token Savior tool candidates matching a natural-language query via embedding cosine similarity. Outputs schema or TypeScript signature for each.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • Get answers to questions about any codebase using AI with full repository context. Combines static analysis and key file contents for evidence-based responses.
    MIT
  • Execute a broad TypeScript typecheck on selected files, persist diagnostics as ProjectFinding rows, and return findings within limit.
    Apache 2.0
  • Improves developer prompts by adding quality requirements, codebase context, and tool recommendations to help AI coding assistants generate better structured code.
    MIT
  • Ask programming questions and get explanations from Kimi's model without codebase context. Use for algorithms, code reviews, or general coding advice.
    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
  • Search for keywords or patterns across the codebase and retrieve file path, line number, and surrounding context.
    MIT
  • Analyze TypeScript files for syntax and semantic errors using project-aware configuration to identify coding issues and ensure code quality.
    MIT
  • Set a specific browser page as the active context for subsequent Chrome DevTools automation commands, enabling targeted debugging and inspection tasks.
    Apache 2.0
  • Check TypeScript files for errors and warnings by analyzing code in a specified directory or using virtual content for diagnostics.
    MIT
  • Choose a page to set as the active context for subsequent operations. Specify page ID and optionally bring the page to the foreground.
    Apache 2.0
  • Rename TypeScript symbols (variables, functions, classes) across your entire codebase to maintain consistency and update references automatically.
    MIT
  • Rename TypeScript symbols (variables, functions, classes) across the entire codebase by specifying the root directory, file path, line, old name, and new name for consistent refactoring.
    MIT