yesdev

YesDev MCP Server is an automation tool that integrates with the YesDev project management platform to help developers log daily work hours, manage tasks, and automatically generate daily reports. It exposes a suite of MCP tools that can create and update tasks, projects, and needs, fetch user and project data, submit daily reports, and query or modify various YesDev resources. You can trigger these tools from Cursor, VSCode, or any supported MCP client, enabling AI-assisted task creation and time tracking without manual UI interactions. The server centralizes access via your YesDev access token and exposes an extensive set of APIs for routine project management activities.

Available capabilities include: getting your profile and staff/project lists, creating and updating tasks, needs, and projects, querying tasks and needs, submitting daily reports, and retrieving project details. You can compose natural-language prompts that instruct the MCP to, for example, create a new project for today, generate a set of requirements or tasks from a feature spec, and log corresponding work hours to YesDev. The toolset is designed to streamline daily standups, sprint planning inputs, and progress reporting by programmatically mirroring human actions in YesDev.

Prerequisites:

• Node.js >= 18.0.0
• npm or yarn

1. Clone the repository:

git clone https://github.com/yesdevcn/yesdev-mcp-server.git
cd yesdev-mcp-server

2. Install dependencies:

npm install

3. Create and configure environment file:

cp .env.example .env

4. Set your YesDev access token in the environment file:

# .env
YESDEV_ACCESS_TOKEN=your-yesdev-access-token

5. Run in development mode:

npm run dev

6. Build and run for production:

npm run build
npm start

Expected startup output will show registered MCP tools and that the YesDev MCP Server has started.

Tips and notes:

• Ensure YESDEV_ACCESS_TOKEN is valid; tokens are obtained from YesDev's platform under account settings.
• The MCP server registers a comprehensive set of tools (e.g., get_my_profile, create_task, update_task, create_project, submit_daily_report, get_project_list, etc.). You can reference the in-repo tool list and corresponding API docs in YesDev for parameter details.
• If you customize the local path to the server binary, ensure the path in the mcp_config matches your environment (use which yesdev-mcp-server to locate).
• When troubleshooting, verify environment variable loading (use a small test script or print process.env to confirm YESDEV_ACCESS_TOKEN is visible to the server).
• For Cursor integration, ensure the Cursor JSON config uses the appropriate command and environment as shown in the example.
• If you update dependencies or tokens, rebuild the project to ensure the dist/index.js reflects changes.