mcp-refactor-typescript
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| file_operationsA | Rename/move TypeScript files - auto-updates ALL imports (<1s, 47 refs across 12 files). vs Edit/Bash: They break imports. This catches dynamic imports, mocks, re-exports. Use when: Renaming/moving TS/JS files. Always use this, not mv/Edit. |
| code_qualityA | Fix ALL TypeScript errors + organize imports + remove unused (<1s, 20+ issues). vs Manual: Compiler-verified, preserves side-effects, finds hidden issues. Use when: After refactoring or before commits. Use proactively. |
| refactoringA | Rename symbols, extract functions, or move symbols to files (auto-updates imports). vs Edit: Updates ALL refs (imports, JSDoc, dynamic imports). Impossible by hand. Use when: Renaming, extracting, or moving symbols between files. Always use this. |
| workspaceA | Find references (type-aware) | Cleanup | Move+organize+fix | Restart tsserver. vs grep: Finds dynamic imports, JSDoc, type-only imports grep misses. ⚠️ Can DELETE. Use when: Before renaming/refactoring. Use find_references first to see impact. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| operations-catalog | Detailed documentation for all refactoring operations with examples |
TDQS
Scored across 4 tools
Tools have mostly distinct purposes: code_quality for fixing errors/organizing, file_operations for file moves, refactoring for symbol renaming/extraction, workspace for finding references and cleanup. Some overlap exists (e.g., workspace cleanup may overlap with code_quality), but descriptions clarify when to use each.
All names use lowercase snake_case, but the pattern is inconsistent: code_quality (noun_quality) vs file_operations (noun_operations) vs refactoring (gerund) vs workspace (single noun). No verb_noun pattern, making it less predictable for agents.
With 4 tools, the surface is well-scoped for a TypeScript refactoring server. Each tool covers a key area (code quality, file operations, symbol refactoring, workspace queries) without unnecessary bloat.
Core refactoring workflows are covered: error fixing, file renaming, symbol manipulation, and referencing. Minor gaps like formatting or running typechecker are absent, but the set is sufficient for common refactoring tasks.