A
licenseB
qualityD
maintenanceMCP server that exposes the V-Track project management API as tools for AI assistants, enabling interaction with projects, tasks, issues, sprints, and more.
54
11 npm
MIT
WeTrack Enterprise MCP Server
by subbuyalla
Related Servers
Alternatives to WeTrack Enterprise MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with JetBrains YouTrack for issue, project, and user management through natural language.1-
- AlicenseNot gradedqualityDmaintenanceEnables 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.ISC
- FlicenseNot gradedqualityDmaintenanceEnables LLM agents to manage projects, track issues, log work, and integrate with Git. Provides 23 MCP tools for full project management capabilities.15-
- AlicenseNot gradedqualityAmaintenanceConnects a workspace and project management platform to Claude, Cursor, VS Code, Windsurf, and other MCP clients, letting users list workspaces, create and manage projects and tasks, and build, train, and prompt AI agents. Also generates MCP tools from any OpenAPI spec.3,386 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables 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.15 npm52-
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
ActivitySlowing
ResponsivenessNo issues