Skip to main content
Glama
harrynguyen14

VTrack MCP Server

by harrynguyen14
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to VTrack MCP Server

No user-submitted related servers found.

    Related Servers

    • yandex-tracker-mcp

      brekhov-ilya
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Yandex Tracker API, enabling AI assistants to search, read, create, and edit issues, as well as manage comments, attachments, and links in Yandex Tracker.
      20 npm
      1
      MIT

    • openproject-mcp-and-skills

      chien334
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server enabling AI agents to interact with OpenProject API v3 for project management, including creating and managing work packages, projects, comments, time entries, boards, and user dashboards.
      28 npm
      MIT

    • taiga-mcp

      juanleon8581
      A
      license
      A
      quality
      B
      maintenance
      MCP server for the Taiga project management API. Enables AI assistants to manage projects, issues, user stories, tasks, epics, sprints, and wiki pages via natural language commands.
      55
      7 npm
      ISC

    • zube-mcp

      reenrik
      F
      license
      C
      quality
      D
      maintenance
      MCP server for the Zube.io project management API, exposing boards, cards, epics, tickets, sprints, and workspaces as tools for AI assistants.
      42
      -
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3/5.0

    Scored across 54 tools

    Disambiguation4/5

    Most tools target distinct resources or actions due to descriptive names, but there is minor overlap between backlog_list, issues_list, and tasks_list (all task-like concepts) and among sprints-related tools. Descriptions help differentiate them.

    Naming Consistency5/5

    All tool names follow a consistent resource_action pattern with underscores (e.g., attachments_list, projects_detail). No mixing of conventions or ambiguous verbs.

    Tool Count3/5

    54 tools is high for a typical MCP server, but the domain (project management) is broad and each tool targets a specific aspect (CRUD per resource). The count is justifiable but borderline excessive.

    Completeness2/5

    The surface heavily favors read operations (list, detail) with no create/update/delete tools except notifications_mark_read. This leaves significant gaps for an agent needing to modify resources, limiting workflow completeness.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources