Skip to main content
Glama
612,506 tools. Updated 2026-09-26 15:41

"How to use ESLint and TypeScript for code validation" matching MCP tools:

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    A minimal MCP server with get_weather and create_ticket tools, used for testing MCP servers across protocol, unit, eval, transport, and auth layers.
    MIT

Matching MCP Connectors

  • Generate standardized workspace settings and recommended extensions for TypeScript, ESLint, Tailwind CSS, and MCP development to establish consistent team configurations across VS Code and Cursor.
    MIT
  • Generates a TypeScript snippet for smart pay, automatically selecting escrow for agent addresses or instant payment for HTTPS endpoints. Use for direct payments without negotiation.
    Apache 2.0
  • Validate TypeScript intent definitions using 134 diagnostic rules. Returns JSON diagnostics with severity, code, line, column, message, and suggestions.
    Apache 2.0
  • Generate zero-dependency JavaScript or TypeScript modules for state stores, event buses, scroll observers, theme toggles, and form validators, with built-in memory cleanup and error boundaries.
    MIT
  • Automatically fix lint errors in code files by applying VS Code source.fixAll or falling back to eslint, biome, or ruff.
    MIT
    Destructive
  • Generate a TypeScript skeleton for an n8n custom node from a plain-English description. Returns a complete code file with description, credentials, and an execute method stub.
    MIT
  • Generate Zod validation schemas with TypeScript types from Pydantic models, FastAPI apps, or OpenAPI URLs, ensuring type-safe frontend validation that matches backend definitions.
    MIT
  • Scaffold a production-ready Express.js + TypeScript backend project with your choice of ORM, Zod validation, Swagger docs, Docker, ESLint, Vitest, and more.
    MIT
  • 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
  • Answers free-text questions about a repo by semantic search over its README, docs, and issues. Use for queries other tools can't answer, like 'Does this support TypeScript?' or 'How do I configure X?'
    MIT
  • Rank JavaScript and TypeScript files in a directory by risk density to identify failure-prone code before review. Excludes test files by default; choose includeTests to rank them as well.
    MIT
  • Verify TypeScript code correctness by running type-checking on a specified service path, receiving structured error details for pre-commit validation.
    MIT
  • Read VS Code workspace settings, filtering by section like 'editor' or 'typescript', and returning the scope of each setting.
    MIT