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 |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Stefan-Nitu/mcp-refactor-typescript'
If you have feedback or need assistance with the MCP directory API, please join our Discord server