Skip to main content
Glama
Athenaxlee

llm-migrate

by Athenaxlee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to llm-migrate

No user-submitted related servers found.

    Related Servers

    • FreshStack MCP

      Jayesh01323
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to inspect project dependency versions, resolve version constraints, and audit Python code for deprecated or incompatible APIs using authoritative evidence and local AST analysis.
      3
      19 npm
      MIT

    • ropey

      andrewesweet
      A
      license
      A
      quality
      D
      maintenance
      Enables coding agents to perform safe, project-wide Python refactoring (rename, move, extract, inline, change signature, organize imports, etc.) with a dry-run safety contract and LSP-coordinate addressing.
      15
      MIT

    • assurance-memory

      yshaaban
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to perform read-only source investigation via a local SQLite index, offering status, search, backlog, context, impact, and drift tools for TypeScript, JavaScript, and Java codebases.
      -

    • astra-mcp

      nimelkot
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to index local Python repositories and retrieve code intelligence through semantic search, caller lookups, hybrid context expansion, and visualization.
      5
      MIT
    • NSTOK AI Software Factory MCP Server by nstok-id

      NSTOK AI Software Factory MCPofficial

      nstok-id
      F
      license
      C
      quality
      C
      maintenance
      Enables reasoning agents to turn PRDs into production-ready applications by discovering and reusing existing features, UI components, database models, and templates, then planning, scaffolding, validating, and preparing Git changes for review.
      29
      -
    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

    C2.8/5.0

    Scored across 35 tools

    Disambiguation3/5

    Most tools are separated by clear object nouns (model, prompt, invocation, file, blocker, evaluation), but the generate/plan/report/finalize/start cluster is easy to confuse and requires careful reading of descriptions. The analyze/prepare/validate pairs also rely on subtle wording rather than instantly obvious boundaries.

    Naming Consistency5/5

    All 35 tools follow the same verb_noun snake_case convention with no camelCase or mixed naming styles. Compound targets are consistent and readable, such as prepare_prompt_migration vs prepare_invocation_migration and get_blocker_resolutions vs get_research_prompts.

    Tool Count2/5

    35 tools is well above the 25+ threshold and makes the flat tool surface heavy for agents to navigate. The breadth is defensible for a migration platform, but as a single MCP server it would benefit from consolidation, grouping, or namespacing.

    Completeness5/5

    The lifecycle is unusually complete: scan application, resolve models, analyze prompts/invocations, generate plans, start runs, handle blockers, submit adaptations, evaluate, review evidence, build consensus, and finalize. There are no obvious dead ends, and finalize_migration plus the blocker tools explicitly handle remaining gaps and next steps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources