Labsco
MCP SERVER

YesDev

by yesdevcn

Run YesDev project work from the client: file a requirement, break it into tasks with owners and planned dates, query the task list by status or date window, and post the day's report.

Project & Task ManagementVerified
Summary
Requirement, task and issue stay separate objects here, so a plan does not collapse into one flat to-do list.

A task can carry need_id, problem_id and project_id at once, which is what lets query_tasks answer questions like 'unfinished work on this requirement, planned to start this week, owned by these people' in a single call. The write surface is real rather than advisory — tasks, projects and requirements can all be created, updated and deleted — but update_project is deliberately narrow, taking only name, description, owner and background colour, with dates and status behind their own calls. Issues arrive rather than originate: get_my_problems reads what was assigned to the caller and update_problem edits it, with no tool that files a new one.

What it is

A YesDev project-management front end, 28 tools covering projects, requirements, tasks, assigned issues and the daily report for the account behind the connection.

What you get
  • Task work end to end: create_task, get_task_detail, update_task, remove_task, plus query_tasks filtering on status, type, owner, project, milestone flag and start, finish or planned date ranges with paging and sorting.
  • Project records: create_project, get_project_detail, get_project_list, update_project for name, description, owner and colour, and the narrower update_project_status and update_project_time.
  • A requirements layer above tasks: create_need, update_need, get_need_detail and its reduced form get_need_detail_lite, remove_need, query_needs, get_project_needs, and get_sub_needs for children of a parent requirement.
  • The identity lookups the other calls depend on: search_staff resolves a name or employee number to an employee ID, get_workgroup_list returns work group IDs, get_my_profile returns the caller's own ID.
  • The caller's own queue in three calls: get_my_task_list for open tasks, get_my_problems for issues assigned to them, get_my_project_list for the projects they are working on, with update_problem and submit_daily_report to close the loop.
Requirements

A YesDev account whose projects, requirements and tasks the tools address. Most write calls take an employee ID, a work group ID or a project ID rather than a name, which search_staff, get_workgroup_list and get_my_profile resolve first.

Setup effort

One command plus a key — npm install -g @yesdevcn/yesdev-mcp-server, then supply credentials