# @taskinger/mcp

> MCP server for Taskinger: read and write the tasks and notes of one workbook from Claude, Cursor or any MCP client.

Latest version **0.4.1** (published 2026-09-24) · MIT license · 0 weekly downloads

## Install

```sh
npm install @taskinger/mcp
pnpm add @taskinger/mcp
yarn add @taskinger/mcp
bun add @taskinger/mcp
```

Provides the command `taskinger-mcp`.

## Health

**Score 60/100 (C)** — status: active.

Positive: esm support; no vulnerabilities; recently updated; high maintenance score.

Warnings: low downloads; no types; pre 1.0.

## Facts

| | |
|---|---|
| Version | 0.4.1 |
| Published | 2026-09-24 |
| First published | 2026-09-23 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | ESM |
| Node | >=18 |
| Dependencies | 2 |
| Unpacked size | 14.5 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | Taskinger |
| Maintainers | vmetal |
| Keywords | mcp, model-context-protocol, taskinger, tasks, notes, claude, cursor |

## Links

- npm: https://www.npmjs.com/package/@taskinger/mcp
- Repository: https://github.com/MegaVmetal/Taskinger.app
- Homepage: https://taskinger.app
- Issues: https://github.com/MegaVmetal/Taskinger.app/issues
- npm.io page: https://npm.io/package/@taskinger/mcp

## Dependencies (2)

- [zod](https://npm.io/package/zod.md) ^3.24.0
- [@modelcontextprotocol/sdk](https://npm.io/package/@modelcontextprotocol/sdk.md) ^1.12.0

## Recent versions

- 0.4.1 (latest) — 2026-09-24
- 0.4.0 — 2026-09-24
- 0.3.0 — 2026-09-23
- 0.2.0 — 2026-09-23
- 0.1.0 — 2026-09-23

## README

# @taskinger/mcp

An MCP server for [Taskinger](https://taskinger.app): work in one workbook —
its tasks and its notes — from Claude Desktop, Claude Code, Cursor or any
other MCP client.

Tasks say what to do. Notes are where an assistant writes down what it
learned, so the next session does not work it out again.

## Setup

Mint a key in the app: **Workbook settings → External API** (Team plan). Give
it the write scope if the assistant should create and edit things rather than
only read them.

Claude Code:

```bash
claude mcp add taskinger -e TASKINGER_API_KEY=zad_… -e TASKINGER_WORKBOOK=… -- npx -y @taskinger/mcp
```

Claude Desktop (`claude_desktop_config.json`) or Cursor (`mcp.json`):

```json
{
  "mcpServers": {
    "taskinger": {
      "command": "npx",
      "args": ["-y", "@taskinger/mcp"],
      "env": {
        "TASKINGER_API_KEY": "zad_…",
        "TASKINGER_WORKBOOK": "the workbook id, as in https://taskinger.app/w/<id>"
      }
    }
  }
}
```

| Variable | |
|---|---|
| `TASKINGER_API_KEY` | `zad_<keyId>.<secret>`, from Workbook settings → External API |
| `TASKINGER_WORKBOOK` | the workbook id from its address |
| `TASKINGER_API_BASE` | optional; defaults to `https://taskinger.app/api` |

## Tools

**Tasks** — `list_tasks`, `get_task`, `create_task`, `update_task`,
`complete_task`.

**Notes** — `list_notes`, `get_note`, `create_note`, `update_note`. A note is
written prose; a list is ticked off. A list's lines are edited by name (add,
tick by line id, remove by line id), so an edit here never overwrites a line
somebody changed in the app meanwhile.

**Lookups** — `get_workbook` (including the house rules on task intake),
`list_members`, `list_projects`, `list_labels`.

## Scope

One workbook per server process, named by the environment, so an assistant
only ever sees and touches what the key was minted for — a key cannot reach
another workbook. A read-only key gives a read-only assistant. Everything the
server writes goes through the same API the app's own integrations use, so it
lands in the activity log, pushes and webhooks like any other change, and the
workbook's house rules are enforced.

Full API reference: [taskinger.app/openapi.yaml](https://taskinger.app/openapi.yaml).

## License

MIT

---
_Source: https://npm.io/package/@taskinger/mcp · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._