create_need
Creates a new YesDev requirement.
LABSCO 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
Follow the published steps — npm install -g @yesdevcn/yesdev-mcp-server
USE CASES
01
Turning an agreed requirement into work someone owns
File the requirement against the project, then create the tasks under it with an owner and planned dates, and check what the project already carries before adding more.
02
Answering what you are on the hook for today
Read your open tasks, the issues waiting on you and the projects you are in, then post the day's report without opening the tracker.
03
Resolving a colleague to an ID before anything can be assigned
Most write calls take an employee or work group ID rather than a name, so the lookup comes first.
04
Pulling the exact slice of tasks a status meeting needs
Filter the task list by owner, status, milestone flag and date window, or take one project's list whole, then open the tasks worth discussing.
28 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_project
Creates a new YesDev project.
create_task
Creates a new YesDev task.
get_my_problems
Returns the issues assigned to the caller and still waiting on them.
get_my_profile
Returns the caller's own profile, including their employee ID.
get_my_project_list
Returns the in-progress projects the caller takes part in.
get_my_task_list
Returns the caller's unfinished tasks.
get_need_detail
Returns the full detail of the requirement with the given ID.
get_need_detail_lite
Returns a reduced view of the requirement with the given ID.
get_project_detail
Returns the detail of the project with the given ID.
get_project_list
Returns the full project list, with filtering, search and sorting.
get_project_needs
Returns every requirement belonging to the given project.
get_project_task_list
Returns the task list for one project.
get_sub_needs
Returns the child requirements of the given parent requirement.
get_task_detail
Returns the full detail of one task.
get_workgroup_list
Returns every work group together with its ID.
query_needs
Queries the requirement list on multiple conditions.
query_tasks
Queries the task list on multiple conditions, with filtering, search and sorting.
remove_need
Deletes the requirement with the given ID.
remove_task
Deletes the given task.
search_staff
Searches staff by name or employee number and returns the matching employee IDs.
submit_daily_report
Submits or updates the current day's report.
update_need
Updates the given fields of the requirement with the given ID.
update_problem
Updates an issue's fields, such as status, owner, attribution, type and remarks.
update_project
Updates a project in place, limited to its name, description, owner and background colour.
update_project_status
Updates the status of the project with the given ID.
update_project_time
Updates the planned start and end time of the project with the given ID.
update_task
Updates a task's fields; partial updates are supported.
BEFORE YOU INSTALL
What to know first
Tools you get
28 tools when we connected.
Requires
- Node.js >= 18.0.0
- YESDEV_ACCESS_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Moderate Standing cost
Rated by the size of the 28 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g @yesdevcn/yesdev-mcp-serverFind where npm installed it: which yesdev-mcp-server
Put the path it prints into args in the block below, and your YesDev access token — from https://www.yesdev.cn/platform/account/accountInfo after a free sign-up — into YESDEV_ACCESS_TOKEN.
MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"yesdev-mcp-server": {
"command": "node",
"args": [
"<YOUR_PATH_TO_BIN_YESDEV_MCP_SERVER>"
],
"env": {
"YESDEV_ACCESS_TOKEN": "<YOUR_YESDEV_ACCESS_TOKEN>"
}
}
}
}
