TypeScript AST MCP Server
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_fileA | Provides a high-level summary of all symbols (classes, interfaces, types, enums, functions) in a TypeScript/JavaScript file |
| analyze_packageB | Analyzes all TypeScript/JavaScript files in a directory, providing a package-level summary |
| list_functionsA | Lists all functions and methods in a TypeScript/JavaScript file with their signatures and line ranges |
| get_function_bodyA | Extracts the full body of a specific function or method. Supports Class.method syntax. |
| list_methodsA | Lists all methods for a specific class in a TypeScript/JavaScript file |
| get_type_definitionA | Extracts the full definition of any type (interface, type alias, class, enum) by name |
| list_declarationsA | Lists package-level constant and variable declarations in a TypeScript/JavaScript file |
| list_exportsA | Lists all exported symbols with their kind (function, class, interface, type, variable, re-export) |
| list_importsA | Lists all import statements in a TypeScript/JavaScript file with their bindings and module paths |
| find_usagesB | Finds all occurrences of a specific identifier (variable, function, type) within a file |
| find_node_at_positionB | Identifies the AST node at a given cursor position (line and column) in a TypeScript/JavaScript file |
| get_docA | Extracts JSDoc/TSDoc comments for a symbol (function, type, class, variable). Supports Class.method syntax. |
| call_graphB | Generates a Mermaid flowchart showing the call graph of functions in a TypeScript/JavaScript file or directory |
| get_callersB | Finds all functions in a file or package that call the specified function (reverse call graph) |
| code_complexityA | Computes cyclomatic complexity for functions in a TypeScript/JavaScript file |
| diff_astA | Compares two TypeScript/JavaScript files structurally, reporting added/removed/modified symbols |
| code_smellsA | Detects code smells: long functions, too many parameters, deep nesting, god classes, 'any' casts, non-null assertions |
| find_errorsA | Analyzes TypeScript-specific error patterns: floating promises, empty catches, unsafe type assertions, double assertions |
| dead_codeA | Finds unreferenced unexported symbols (functions, types, variables) within a directory |
| find_implementationsA | Finds classes that implement a specified interface - explicit 'implements' plus structural matches, checked by the TypeScript type checker (member types and call signatures, not just names) |
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 20 tools
Each tool targets a distinct aspect of TypeScript AST analysis, such as listing symbols, extracting definitions, analyzing dependencies, or detecting issues. Even related tools like call_graph and get_callers have clearly differentiated scopes, preventing misselection.
The majority of tools follow a consistent verb_noun snake_case pattern (list_functions, get_type_definition, find_usages). Minor deviations exist, such as noun-only names like call_graph, code_complexity, code_smells, and dead_code, but these remain readable and do not disrupt overall coherence.
With 20 tools, the server is slightly above the typical ideal range, but each tool addresses a distinct need within the TypeScript AST analysis domain. The count feels justified given the breadth of operations covered, from symbol enumeration to code quality checks.
The tool set provides comprehensive coverage for static AST analysis, including symbol discovery, detail extraction, relationship mapping, complexity measurement, error detection, and dead code identification. No obvious gaps exist for the server's stated purpose.