viot-tasktisk
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@viot-tasktiskshow my dashboard"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
viot-tasktisk
MCP server for qlda-viot task tracking. Exposes 4 high-level skills to Claude — no raw API fiddling needed.
Tool | What it does |
| My tasks grouped by urgency + weekly priorities (one call overview) |
| Set status / due / priority on a task or item |
| Full item detail with all child tasks |
| Create a task under an item |
Install
Requires Node.js ≥ 20.
macOS / Linux
Run the installer. It asks a few questions upfront — global vs. user install, then your QLDA credentials — so the rest (npm install + setup wizard) runs unattended:
curl -fsSL https://raw.githubusercontent.com/Iot-Viet-Solution/viot-tasktisk/main/install.sh | bashUpfront prompts:
Global or User install
QLDA API URL (default
http://localhost:3100)Username
Password (hidden input)
Config is saved to ~/.config/viot-tasktisk/config.json (mode 0600).
The wizard prints the exact snippet to paste into Claude Desktop when done.
Install options explained
Global | User | |
Who can use it | Everyone on the machine | Current user only |
Needs sudo | Sometimes (depends on npm setup) | Never |
Install prefix | system npm global |
|
PATH change needed | No | Yes (installer offers to do it) |
Windows
npm install -g https://github.com/Iot-Viet-Solution/viot-tasktisk/releases/latest/download/viot-tasktisk-1.0.1.tgz
viot-tasktisk setupManual install (without the script)
# Global
npm install -g https://github.com/Iot-Viet-Solution/viot-tasktisk/releases/latest/download/viot-tasktisk-1.0.1.tgz
viot-tasktisk setup
# User-local
npm install -g --prefix ~/.npm-global https://github.com/Iot-Viet-Solution/viot-tasktisk/releases/latest/download/viot-tasktisk-1.0.1.tgz
export PATH="$HOME/.npm-global/bin:$PATH" # add to ~/.zshrc or ~/.bashrc
viot-tasktisk setupRelated MCP server: mcp-todo
Claude integration
viot-tasktisk setup offers to auto-configure both Claude products at the end of the wizard.
To re-run just the config step (without re-entering credentials):
viot-tasktisk configureThis registers viot-tasks as a stdio MCP server for each product:
Product | How it's configured | Config location |
Claude Desktop (macOS) | JSON |
|
Claude Desktop (Windows) | JSON |
|
Claude Desktop (Linux) | JSON |
|
Claude Code (CLI) |
|
|
VS Code | JSON | platform user |
Antigravity CLI (Google) | JSON |
|
Codex CLI (OpenAI) | TOML |
|
Claude Code is the one exception: its CLI doesn't read MCP servers from ~/.claude/settings.json
(despite that file existing and looking plausible) — the only supported way to register one is
the claude mcp subcommand, which stores it in ~/.claude.json. configure shells out to
claude mcp remove (ignoring "not found") then claude mcp add, so re-running it updates the
command instead of erroring on a duplicate. This requires the claude CLI to be on PATH.
Restart Claude Desktop / reload Claude Code after configuring.
User-local install: every target here launches the server as its own subprocess rather than through your interactive shell, so none of them see a PATH change that only lives in
~/.bashrc/~/.zshrc.configuretherefore always uses the full binary path (~/.npm-global/bin/viot-tasktisk) for a user-local install, for every target — not just Claude Desktop.
Usage
From Claude
Once configured (see above), just ask in plain language — Claude picks the right tool:
"What's on my dashboard today?"
"Mark task 482 as Done"
"Show me item 120 with all its tasks"
"Add a task to item 120: write API tests, due 2026-07-10, priority Cao"
Direct CLI (no Claude needed)
Every tool is also a standalone terminal command — handy for scripts or a quick check:
viot-tasktisk dashboard # your tasks + weekly priorities
viot-tasktisk my-tasks # alias for dashboard
viot-tasktisk get-item <item_id> # full item detail + child tasks
viot-tasktisk add-task <item_id> <title> [options]
--due YYYY-MM-DD # due date
--priority TB|Cao|Thấp # priority
--assignee <user_id> # assign to user
--descr <text> # description
viot-tasktisk update-task <task_id> <status> # Plan · Todo · Doing · Done · Close · "Need help"
viot-tasktisk update-item <item_id> <status> # Todo · Doing · Review · Done · Cancelled
viot-tasktisk --help # full command referenceExamples:
viot-tasktisk get-item 120
viot-tasktisk add-task 120 "Write API tests" --due 2026-07-10 --priority Cao
viot-tasktisk update-task 482 DoneTroubleshooting
Symptom | Fix |
| User-local install only: open a new terminal, or run |
| Credentials haven't been saved yet — run |
| Wrong username/password, or the QLDA API URL is unreachable — re-run |
Tools don't show up in Claude Desktop / Claude Code | Config was written but the client hasn't reloaded — fully restart Claude Desktop, or start a new Claude Code session (MCP servers are only loaded at session start). |
| Almost always a stale short command name ( |
| The |
Override via env vars
Env vars take priority over the config file — useful for CI or Docker:
QLDA_URL=http://your-server:3100 \
QLDA_USERNAME=thanh \
QLDA_PASSWORD=secret \
viot-tasktiskUpdate
viot-tasktisk updatePulls the latest version from GitHub and reinstalls using the same prefix (global or user-local) that was used when you first installed. Prints a reminder to restart Claude Desktop.
Re-configure
viot-tasktisk setupDevelopment
git clone https://github.com/Iot-Viet-Solution/viot-tasktisk
cd viot-tasktisk
npm install
npm run dev # run directly with tsx (no build needed)
npm run build # rebuild dist/index.js
npm run typecheck # type check onlyThe prebuilt dist/index.js is committed so the GitHub install needs no build step.
When you change source, run npm run build and commit dist/index.js.
Seed accounts (for testing against local qlda-viot)
Username | Role | Password |
| admin |
|
| tuvan |
|
| dev |
|
| qa |
|
Default URL: http://localhost:3100
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Iot-Viet-Solution/viot-tasktisk'
If you have feedback or need assistance with the MCP directory API, please join our Discord server