TypeScript MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| move_fileB | Move a TypeScript/JavaScript file to a new location and update all import statements |
| mcp__typescript__move_directoryA | Move a directory to a new location, updating all TypeScript imports and references automatically |
| rename_symbolB | Rename a TypeScript symbol (variable, function, class, etc.) across the codebase |
| delete_symbolB | Delete a TypeScript/JavaScript symbol (variable, function, class, etc.) and all its references |
| find_referencesC | Find all references to a TypeScript/JavaScript symbol across the codebase |
| get_definitionsC | Get the definition(s) of a TypeScript symbol |
| get_diagnosticsB | Get TypeScript diagnostics (errors, warnings) for a single file |
| get_module_symbolsC | Get all exported symbols from a TypeScript/JavaScript module without detailed signatures |
| get_type_in_moduleC | Get detailed signature information for a specific type (function, class, interface, type alias, etc.) from a module |
| get_type_at_symbolC | Get type information for a TypeScript/JavaScript symbol at a specific location |
| get_symbols_in_scopeA | Get all symbols (variables, types, functions, etc.) visible at a specific location in a TypeScript/JavaScript file |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.