ts-refactor-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
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 |
|---|---|
| moveFileA | Move a TypeScript file and update all imports automatically. Applies edits atomically. |
| warmupB | Pre-load a TypeScript project to speed up subsequent operations |
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 2 tools
The two tools have clearly distinct purposes: moveFile handles file relocation with import updates, while warmup optimizes performance by pre-loading projects. There is no ambiguity or overlap.
Both tool names use camelCase and are concise. Although moveFile follows a verb_noun pattern and warmup is a single word, they are consistent in style and easily distinguishable.
With 2 tools, the count is slightly below the typical 3-15 range, but for a focused refactoring server offering essential file-moving and caching capabilities, it is reasonable and well-scoped.
While the tools are well-implemented, the server lacks common refactoring operations like symbol renaming, extraction, or type transformations, leaving significant gaps for a refactoring toolset.