VTrack MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@VTrack MCP Server list all projects"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
VTrack MCP Server
MCP (Model Context Protocol) server that exposes the V-Track project management API as tools for AI assistants.
Setup
1. Install dependencies
npm install2. Build
npm run build3. Configure
Set environment variables before starting:
Variable | Description | Default |
| V-Track API base URL |
|
| Bearer access token | (empty) |
Or call the configure tool at runtime to set them dynamically.
4. Run
npm start
# or for development
npm run devRelated MCP server: taiga-mcp
Connecting to Claude Desktop / Claude Code
Add to your MCP config (e.g. ~/.claude/settings.json or Claude Desktop config):
{
"mcpServers": {
"vtrack": {
"command": "node",
"args": ["D:/workspace/vtrack-mcp/dist/index.js"],
"env": {
"VTRACK_BASE_URL": "https://your-vtrack-api.example.com",
"VTRACK_ACCESS_TOKEN": "your-bearer-token"
}
}
}
}Available Tools
Meta
Tool | Description |
| Set base URL and access token at runtime |
Auth
Tool | Description |
| Login, returns accessToken + refreshToken |
| Refresh access token |
| Logout current user |
Users
Tool | Description |
| Paginated user list |
| Current user info |
| User detail by ID |
Projects
Tool | Description |
| Paginated project list |
| Project detail by ID |
| Export members as Excel |
Tasks
Tool | Description |
| Paginated task list with filters |
| Task detail by ID |
| Kanban board grouped by status |
Backlog
Tool | Description |
| Paginated backlog (feature tasks) |
| Backlog item detail |
Issues
Tool | Description |
| Paginated issues (bug tasks) |
| Issue detail by ID |
Sprints
Tool | Description |
| Paginated sprint list |
| Active sprints only |
| Sprint detail by ID |
| Lightweight sprint list for dropdowns |
Project Members
Tool | Description |
| Members of a project |
Task Comments
Tool | Description |
| Comments for a task (cursor-based) |
| Comment detail by ID |
Attachments
Tool | Description |
| Attachments for an entity |
| Attachment detail by ID |
Requests
Tool | Description |
| Paginated request list |
| Request detail by ID |
Milestones
Tool | Description |
| Paginated milestone list |
| Milestone detail by ID |
Reports
Tool | Description |
| System-wide metrics |
| System-wide alerts |
| Project-level report |
| Exportable project data |
| Project-level alerts |
Workload
Tool | Description |
| Workload per team member |
Lookup Tables
Tool | Description |
| All priorities |
| All system roles |
| All project roles |
| Task types (optionally by project) |
| Request types (optionally by project) |
| Request channels |
| All statuses (no auth required) |
Notifications
Tool | Description |
| User's notifications |
| Mark one notification as read |
| Mark all notifications as read |
Meeting Notes
Tool | Description |
| Paginated meeting notes |
| Meeting note detail by ID |
Service Monitors
Tool | Description |
| Paginated monitor list |
| Monitor detail |
| Monitor logs |
| Incident list |
| Incident detail |
| SLA statistics |
| Uptime statistics |
Misc
Tool | Description |
| API health check |
| Paginated audit logs |
Response Format
All V-Track responses follow this envelope:
{
"code": 0,
"message": "...",
"data": {},
"total": 100,
"totalPages": 10
}code: 0 = success. Errors: -2 bad request, -3 unauthorized, -4 not found.
Available Tools
54 toolsattachments_detailB
Get detailed information about a specific attachment.
Inputs: id (required).
attachments_listA
Get list of attachments for a given entity (task, project, etc.).
Inputs: entityType (required), entityId (required).
audit_logsC
Get audit logs, optionally filtered by user.
Inputs: userId, page, pageSize, filters.
backlog_detailC
Get detailed information about a specific backlog item.
Inputs: id (required).
backlog_listB
Get paginated list of backlog items (feature tasks without sprint).
Inputs: page, pageSize, filters, projectId, +8 more.
configureA
Configure the MCP server connection (base URL and access token). Call this before using other tools if environment variables are not set.
Inputs: baseUrl, accessToken.
health_checkA
Check if the V-Track API is healthy and reachable.
Inputs: no named parameters.
issues_detailB
Get detailed information about a specific issue.
Inputs: id (required).
issues_listB
Get paginated list of issues (bug tasks without sprint).
Inputs: page, pageSize, filters, projectId, +8 more.
lookup_prioritiesA
Get all available task/request priorities.
Inputs: no named parameters.
lookup_project_rolesA
Get all available project roles.
Inputs: no named parameters.
lookup_request_channelsA
Get all available request channels.
Inputs: no named parameters.
lookup_request_typesC
Get request types, optionally filtered by project.
Inputs: projectId.
lookup_rolesA
Get all available system roles.
Inputs: no named parameters.
lookup_statusesA
Get all available statuses (no auth required).
Inputs: no named parameters.
lookup_task_typesC
Get task types, optionally filtered by project.
Inputs: projectId.
meeting_notes_detailB
Get detailed information about a specific meeting note.
Inputs: id (required).
meeting_notes_listC
Get paginated list of meeting notes for a project.
Inputs: page, pageSize, filters, projectId.
milestones_detailB
Get detailed information about a specific milestone.
Inputs: id (required).
milestones_listC
Get paginated list of milestones for a project.
Inputs: page, pageSize, filters, projectId, +1 more.
notifications_listA
Get notifications for the currently authenticated user.
Inputs: no named parameters.
notifications_mark_all_readA
Mark all notifications as read for the current user.
Inputs: no named parameters.
notifications_mark_readA
Mark a specific notification as read.
Inputs: id (required).
project_members_listC
Get paginated list of members for a project.
Inputs: page, pageSize, filters, projectId.
projects_detailB
Get detailed information about a specific project.
Inputs: id (required).
projects_export_members_excelC
Export project members list as an Excel file.
Inputs: no named parameters.
projects_listC
Get paginated list of projects with optional filters.
Inputs: page, pageSize, filters, statusId, +1 more.
reports_attentionB
Get system-wide alerts and items needing attention.
Inputs: no named parameters.
reports_export_dataC
Get exportable report data for a project.
Inputs: projectId (required), startDate (required), endDate (required), sprintId.
reports_globalA
Get global system-wide metrics and KPIs.
Inputs: no named parameters.
reports_projectC
Get report metrics for a specific project.
Inputs: projectId (required), sprintId, startDate, endDate.
reports_project_attentionC
Get alerts and items needing attention for a specific project.
Inputs: projectId (required), sprintId, startDate, endDate.
requests_detailC
Get detailed information about a specific request.
Inputs: id (required).
requests_listC
Get paginated list of requests with optional filters.
Inputs: page, pageSize, filters, projectId, +7 more.
service_monitors_detailB
Get detailed information about a specific service monitor.
Inputs: id (required).
service_monitors_incident_detailB
Get detailed information about a specific incident.
Inputs: id (required).
service_monitors_incidentsC
Get paginated list of incidents.
Inputs: page, pageSize, filters.
service_monitors_listC
Get paginated list of service monitors.
Inputs: page, pageSize, filters.
service_monitors_logsC
Get paginated monitor logs.
Inputs: page, pageSize, filters.
service_monitors_sla_statsC
Get SLA statistics for a service monitor.
Inputs: monitorId (required), startDate, endDate.
service_monitors_uptime_statsC
Get uptime statistics for a service monitor.
Inputs: monitorId (required), startDate, endDate.
sprints_detailB
Get detailed information about a specific sprint.
Inputs: id (required).
sprints_listC
Get paginated list of sprints for a project.
Inputs: page, pageSize, filters, projectId.
sprints_list_activeB
Get paginated list of active sprints for a project.
Inputs: page, pageSize, filters, projectId.
sprints_list_for_filterC
Get sprint list for use in filter dropdowns (lightweight).
Inputs: projectId.
task_comments_detailA
Get detailed information about a specific task comment.
Inputs: id (required).
task_comments_listB
Get comments for a task in chat style (cursor-based pagination).
Inputs: taskId (required), limit, cursor.
tasks_detailB
Get detailed information about a specific task.
Inputs: id (required).
tasks_kanban_boardA
Get the Kanban board view of tasks grouped by status for a project/sprint.
Inputs: projectId (required), sprintId, viewAll.
tasks_listC
Get paginated list of tasks with optional filters.
Inputs: page, pageSize, filters, projectId, +5 more.
users_detailB
Get detailed information about a specific user by ID.
Inputs: id (required).
users_listB
Get paginated list of users with optional filters.
Inputs: page, pageSize, filters.
users_meA
Get information about the currently authenticated user.
Inputs: no named parameters.
workload_listC
Get workload data per team member for a project.
Inputs: projectId (required), startDate, endDate, memberName, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 54 tools
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.
All tool names follow a consistent resource_action pattern with underscores (e.g., attachments_list, projects_detail). No mixing of conventions or ambiguous verbs.
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.
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
Related MCP Connectors
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server exposing the Backtest360 engine API as tools for AI agents.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
MCP server exposing klokin time-tracking operations (employees, time entries, stores) to AI clients.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP 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.63 npm1MIT
- AlicenseAqualityCmaintenanceMCP 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.559 npmISC
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes the full Task-Tracker REST API as MCP tools, enabling AI agents to manage trackers, tasks, notes, checklists, and projects conversationally.MIT
- FlicenseCqualityDmaintenanceMCP server for the Zube.io project management API, exposing boards, cards, epics, tickets, sprints, and workspaces as tools for AI assistants.42-