Gotask MCP

A Model Context Protocol (MCP) server designed for Taskfile/go-task, supporting the running of development tasks through AI agents.

Developer tools Education and learning tools #Task runner #Development tool #AI integration .Python

rating : 2.5 points

downloads : 6.7K

update time : 2025-04-28

Open Site

What is gotask-mcp?

gotask-mcp is a server based on the Model Context Protocol (MCP), designed to automate development tasks such as code inspection and automated fixes through Taskfile. It allows you to easily integrate these tasks into your development environment.

How to use gotask-mcp?

First, ensure that the necessary dependencies (such as uv and Taskfile) are installed. Then, start the server and integrate it into your development tools, such as Cursor IDE.

Applicable scenarios

Suitable for projects that require frequent running of development tasks, such as code quality inspection, automated build, testing, and deployment.

Main features

List all tasks

Get a list of all tasks defined in the Taskfile of the current project.

Run a specified task

Run a specific task based on the task name.

Advantages

Simplify task management and improve development efficiency.

Support multiple task types to meet different needs.

Easy to integrate into existing development tools.

Limitations

Require installation of additional dependencies (such as uv and Taskfile).

Some features may not be very friendly to beginners.

How to use

Install dependencies

Ensure that uv and Taskfile are installed. You can use the following commands to install them: - For Homebrew users: `brew install uv` and `brew install go-task` - For other methods, please refer to the official documentation.

Start the server

Use the following command to start the gotask-mcp server: `uv run --with mcp --directory /path/to/gotask-mcp mcp run /path/to/gotask-mcp/src/server.py`

Configure Cursor IDE

Add the MCP server in Cursor settings and import the example rule file.

Usage examples

List all tasks

Get all tasks defined in the Taskfile of the current project.

Run a specific task

Run the task named 'lint'.

Frequently Asked Questions

How to install uv and Taskfile?

What should I do if I encounter an error?

Can I use gotask-mcp in other IDEs?

Related resources

Taskfile official documentation

Learn about the detailed usage of Taskfile.

UV installation guide

Learn how to install the UV tool.

Cursor IDE official website

Learn more about Cursor IDE.

🚀 Gotask-mcp

A Model Context Protocol (MCP) server designed for Taskfile/go-task.

🚀 Quick Start

Prerequisites

This project and the mcp CLI tool rely on the dependency management tool uv being installed. You can install it via, for example, brew install uv (for Homebrew users). Refer here for other installation methods.

You also need to install Taskfile. For Homebrew users, brew install go-task is a viable option. Refer here for other installation methods.

Quick Start Guide (for Cursor IDE)

Ensure you have installed the prerequisites.
Clone this repository.
Make sure there is a suitable Taskfile.yml file in your working project (you can take inspiration from the example in this project).
In Cursor Settings > MCP Server, start a server using the following command:

uv run --with mcp --directory /path/to/gotask-mcp mcp run /path/to/gotask-mcp/src/server.py

It is recommended to copy the context rules in .cursor/rules/tool-use-rule.mdc to your working project (or write similar rules). The Cursor Agent needs some instructions to use the tools correctly.

📚 Documentation

Task runners (such as Taskfile) are a way to define and run commands for simple or complex tasks, which are usually required to be executed regularly.

Such tasks can be an important part of the development cycle, such as automatic fixes and QA checks. Therefore, it would be very useful if a code agent powered by generative AI could run these tasks at the appropriate time. The way to achieve this is through an MCP server that provides tools for running such tasks.

This server is designed to run in an isolated environment and allows clients (such as the Cursor IDE Agent) to pass context information about the working project.

A tool for getting a list of available tasks.
A tool for running a task with a specified name.

The Cursor Agent needs to pass the working directory path as input to these tools so that they can read the project's Taskfile.yml file.

(Note: At the time of writing, the integration of MCP resources with the Cursor IDE is not ideal - the first tool should ideally be implemented as a resource rather than a tool.)