Summary

Close the task in the editor where you finished the work.

The gap it closes is small and daily: the moment a fix is done, the bug can be resolved with its resolution and build recorded — without switching to ZenTao, finding the item and filling in the form.

What it is

A ZenTao integration built for editor use rather than a generic database wrapper: it wraps the ZenTao API at the level of the workflow, handling authentication for you and persisting the connection so you configure it once.

What you get

Your task list and your bug list, fetched for the logged-in user
Finishing a task by its ID
Resolving a bug with the resolution, the build it was resolved in, and a comment
Configuration persistence — the ZenTao URL, username, password and API version are saved so later calls need only the task at hand
TypeScript types across the ZenTao API surface, and authentication managed automatically rather than per call

Requirements

A ZenTao instance and an account on it. The README's global install line names `@bigtian/mcp-zentao`, which npm does not have. The first invocation takes a `config` object carrying the URL, username, password and API version, which is then written to `.zentao/config.json` in your home directory — pass `config` again to update it. Docker Compose is supported, reading `ZENTAO_URL`, `ZENTAO_USERNAME`, `ZENTAO_PASSWORD` and `ZENTAO_API_VERSION` from a `.env` and serving on port 3000, which is what the Cursor entry points at. The config file holds your password in the clear, so set its permissions accordingly; deleting it and reconfiguring is the documented reset.