gotask-mcp

What is gotask-mcp?

gotask-mcp is a Model Context Protocol (MCP) server that integrates with Taskfile (go-task), a task runner. It enables AI coding agents to retrieve a list of available tasks and execute them, making regular development workflows like autofixes and QA checks accessible to LLM-driven tools.

How to use gotask-mcp?

Install the prerequisites uv and Taskfile (e.g., via Homebrew). Clone the repository and ensure a Taskfile.yml exists in your working project. In Cursor IDE settings > MCP Servers, start a server with the command:
uv run --with mcp --directory /path/to/gotask-mcp mcp run /path/to/gotask-mcp/src/server.py
Optionally copy the included .cursor/rules/tool-use-rule.mdc into your project to guide the agent.

Key features of gotask-mcp

• Retrieve a list of available tasks from the project’s Taskfile.yml
• Run a named task with the working directory passed by the client
• Designed for isolated execution with contextual project information
• Tested with Cursor IDE Agent
• Minimal tool interface: two tools (list tasks, run task)

Use cases of gotask-mcp

• An AI agent automatically runs linting or formatting tasks before creating a commit
• A coding agent executes test or build tasks after making changes to verify correctness
• Developers delegate repetitive QA steps (e.g., type checking, dependency updates) to their AI assistant
• CI-like workflows are triggered locally by the agent without manual intervention

FAQ from gotask-mcp

What prerequisites are needed to run gotask-mcp?

You need uv (e.g., brew install uv) and Taskfile (e.g., brew install go-task) installed on your system.

Where are the tasks defined that gotask-mcp runs?

Tasks are defined in a Taskfile.yml file located in the working project directory. The server reads that file using the working directory path provided by the client.

How does gotask-mcp know which project to work with?

The client (e.g., Cursor IDE Agent) passes the working directory path as an input to the tools, allowing the server to locate and read the correct Taskfile.yml.

What is a known limitation when using gotask-mcp with Cursor IDE?

At the time of writing, MCP resources do not work well with Cursor IDE. Therefore the list-tasks feature is implemented as a tool rather than a resource.

What transport does gotask-mcp use?

The server is started via the mcp CLI using mcp run, which by default uses stdio transport for communication with the client.