Skip to main content
Glama
Stefan-Nitu

mcp-refactor-typescript

by Stefan-Nitu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-refactor-typescript

No user-submitted related servers found.

    Related Servers

    • ts-mcp-server

      AndyLiner13
      A
      license
      A
      quality
      D
      maintenance
      A lightweight MCP server that provides 40 tools for TypeScript/JavaScript refactoring and code intelligence, directly mapping to TypeScript's tsserver protocol commands for accurate structural changes and workspace analysis.
      40
      20 npm
      3
      MIT

    • Refactor MCP

      egn88
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for automated refactoring of Java and TypeScript/JavaScript codebases.
      16
      4
      -

    • weavatrix-refactor-js

      Weavatrix
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides evidence-backed, transactional code refactoring for JavaScript/TypeScript and other languages via MCP, enabling semantic renames, signature changes, edits, and safe bulk operations with preview, atomic apply, and rollback.
      25 npm
      MIT

    • ts-refactor-mcp

      schicks
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI agents to move TypeScript files and directories while automatically updating all affected imports using a persistent tsserver instance. This ensures atomic, error-free refactoring that maintains project integrity without manual intervention or wasted tokens.
      2
      12 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources