ts-diagnostics-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| projectPath | Yes | The absolute path to the TypeScript project root | |
| TS_DIAG_AUTO_DETECT | No | Auto-detect workspaces (true/false, default: true) | |
| TS_DIAG_DEBOUNCE_MS | No | Debounce delay in milliseconds (default: 500) | |
| TS_DIAG_INCREMENTAL | No | Enable incremental builds (true/false, default: true) | |
| TS_DIAG_MAX_CACHE_SIZE | No | Cache size in MB (default: 100) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_all_diagnosticsA | Get all TypeScript diagnostics from all watched projects. Returns errors, warnings, and suggestions with file locations. |
| get_file_diagnosticsA | Get TypeScript diagnostics for a specific file. Much faster than running tsc on the whole project. |
| get_package_diagnosticsA | Get TypeScript diagnostics for a specific package in a monorepo. Useful for filtering diagnostics by workspace. |
| has_errorsA | Quick boolean check if there are any TypeScript errors. Optionally check a specific file. Extremely fast - use this before full diagnostic queries. |
| get_diagnostic_countA | Get summary counts of errors, warnings, and suggestions. Faster than getting full diagnostics. |
| get_watch_statusA | Get status of the TypeScript watch process including watched configs, file count, and last compilation time. |
| get_cache_statsA | Get cache performance statistics including hit rate, size, and evictions. |
| clear_cacheB | Clear cached diagnostics. Optionally clear cache for a specific file only. |
| list_packagesA | List all packages in the monorepo that are being watched. Useful for discovering available package 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 9 tools
Each tool has a clearly distinct purpose: retrieving diagnostics by scope (all, file, package), counting, quick boolean check, cache management, cache stats, watch status, and package listing. No overlap.
All tool names follow a verb_noun pattern in snake_case (e.g., get_all_diagnostics, clear_cache, has_errors, list_packages), which is consistent and predictable.
Nine tools cover the key operations for a TypeScript diagnostics server without being excessive. The scope is well-balanced – enough to be useful but not overwhelming.
The tool surface covers all essential operations: retrieving diagnostics at various levels, cache management, status monitoring, and package discovery. No obvious gaps for the intended purpose.