Skip to main content
Glama
bepuljang

umtri-mcp

by bepuljang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to umtri-mcp

No user-submitted related servers found.

    Related Servers

    • AgentsBestFriend

      TheRealFloatDev
      F
      license
      Not graded
      quality
      D
      maintenance
      Give your AI coding agents superpowers — a local MCP server for fast, token-efficient code navigation, search & analysis.
      -

    • TIMPS

      TIMPSs
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that gives AI coding agents persistent memory across sessions, storing architecture decisions, past bugs, and codebase conventions locally.
      1 npm
      MIT

    • project-memory-mcp

      kaaustubh
      A
      license
      A
      quality
      A
      maintenance
      Local MCP server giving AI coding agents (Claude Code, Cursor, VS Code/JetBrains Copilot) a shared, persistent memory of your projects and every bug/issue faced during development. Stateless, plain-file storage (AGENTS.md + issues.jsonl) — no database.
      16
      37 npm
      1
      MIT

    • repo-context-mcp

      nduc99911
      A
      license
      A
      quality
      B
      maintenance
      MCP server that helps AI coding agents understand a repository by providing lightweight tree/map, code search, and token-budgeted context packing tools without dumping the entire monorepo into the prompt.
      3
      52 npm
      105
      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

    A4.1/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. The only potentially confusable pair is create_edge vs create_api, but their descriptions explicitly distinguish structural dependency from runtime flow, so an agent can reliably select the right one.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores (list_bugs, get_graph, create_node, update_api, delete_bug, etc.). The few non-CRUD verbs (reopen, commit, record) still fit the same pattern, so there are no naming clashes.

    Tool Count3/5

    22 tools is on the heavy side (16–25 feels heavy), but the domain is broad: projects, nodes, edges, apis, bugs, seasons, events, and transplant operations. Every tool has a defined role, yet the overall surface could be trimmed by merging some specialized tools.

    Completeness3/5

    Nodes, apis, and bugs have full create/update/delete coverage, and edges have create/delete but no update. Projects only have create and list, missing update/delete. Season creation is intentionally human-only, which is documented. Agents can work around missing update_edge by delete+create, but there are notable lifecycle gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources