TypeScript MCP
Related Servers
Alternatives to TypeScript MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceSelf-contained MCP server providing type-aware code intelligence for TypeScript, JavaScript, and Vue files, exposing tools like hover, definition, references, and diagnostics to Claude Code without requiring global language server installations.MIT
- AlicenseAqualityDmaintenanceA TypeScript-aware MCP server that provides coding agents with repository discovery, code intelligence, and web project context for local codebases. It enables deep symbol navigation, diagnostic reporting, and structural analysis of monorepos without requiring full IDE integration.715 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that indexes TypeScript/JavaScript codebases into precise call and import graphs using the TypeScript compiler API, allowing Claude or any MCP client to query definitions, callers, callees, and perform impact analysis.7MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to interact with TypeScript projects through compiler-level code intelligence, providing tools for navigation, type information, diagnostics, refactoring, and semantic search.29225 npm3Apache 2.0
- AlicenseAqualityDmaintenanceA lightweight MCP server that provides 40 tools for TypeScript/JavaScript refactoring and code intelligence, directly mapping to TypeScript's tsserver protocol commands for accurate structural changes and workspace analysis.4027 npm3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides TypeScript 7 native language server capabilities (go to definition, find references, hover types, diagnostics) to coding agents, using the Go-based tsc compiler for fast and accurate semantic analysis.317 npm1MIT
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose with no overlap: delete_symbol removes symbols, find_references locates usages, get_definitions provides definitions, get_diagnostics checks errors, get_module_symbols lists exports, get_symbols_in_scope shows local symbols, get_type_at_symbol gives type info at a location, get_type_in_module provides detailed signatures, mcp__typescript__move_directory and move_file handle file/directory moves, and rename_symbol renames symbols. The descriptions precisely differentiate their functions.
Most tools follow a consistent verb_noun pattern (e.g., delete_symbol, find_references, get_definitions), but there is a minor deviation with mcp__typescript__move_directory, which uses a prefixed format. This single outlier slightly disrupts the otherwise predictable naming convention, though the pattern remains readable and functional.
With 11 tools, the count is well-scoped for a TypeScript code analysis and refactoring server. Each tool serves a specific, non-redundant purpose, such as symbol manipulation, type checking, and file management, making the set comprehensive yet manageable without bloat.
The tool set provides complete coverage for TypeScript/JavaScript codebase operations, including symbol management (delete, rename, find references), type information retrieval (definitions, types, diagnostics), module analysis (symbols, exports), and file handling (move file/directory with import updates). There are no obvious gaps; agents can perform full CRUD-like workflows and refactoring tasks seamlessly.