Skip to main content
Glama
subbuyalla

WeTrack Enterprise MCP Server

by subbuyalla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to WeTrack Enterprise MCP Server

No user-submitted related servers found.

    Related Servers

    • Yandex Tracker MCP Server

      zolkinka
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Yandex.Tracker task management system through MCP protocol. Supports creating and managing issues, searching tasks, handling comments, managing projects and queues, and generating analytics reports.
      -

    • YouTrack MCP Server

      devstroop
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with JetBrains YouTrack 2025.2 for managing issues, sprints, dependencies, time tracking, and knowledge base content. Supports CRUD operations, bulk commands, analytics with Gantt charts and critical path analysis, and covers ~80% of the YouTrack REST API.
      11 npm
      52
      -

    • mock-jira

      techindicium
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to interact with a mock JIRA-shaped issue tracker through MCP tools for managing projects, issues, and users.
      -
    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

    B3.1/5.0

    Scored across 110 tools

    Disambiguation2/5

    Multiple reporting/dashboard tools (wetrack_get_reports, wetrack_get_dashboard, wetrack_get_project_reports, wetrack_get_project_overview, wetrack_get_project_stats) have heavily overlapping purposes and outputs, making misselection likely. The client vs organisation tools are also ambiguous since both describe similar organisation entities with nearly identical fields.

    Naming Consistency4/5

    Most tools follow a consistent wetrack_verb_noun snake_case pattern, which makes the set readable and predictable. There are minor deviations such as add_ vs create_ verbs, sign_in vs the signin_url naming, and the similar list_organisations/list_clients pair, but the overall convention remains strong.

    Tool Count1/5

    At 110 tools, the surface is far beyond a manageable MCP tool set and creates a severe agent selection burden. Even though the domain is broad, many tools are niche admin, reporting, and system-trigger utilities that should be consolidated or exposed through fewer composite tools.

    Completeness4/5

    The tool surface is broad and covers most core lifecycle operations for projects, tickets, sprints, users, configurations, files, notifications, and reports. Notable gaps include no ticket deletion, no user deactivation/deletion, and no client/organisation removal, but these are workable gaps rather than fundamental dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources