wt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_productC | Resolve o produto e resume name, projects, presets e tasks. |
| list_tasksC | Lista tasks do estado (empty/ready/broken) com projetos e branches. |
| list_projectsB | Lista projetos configurados no config.yml. |
| create_taskB | Cria uma task vazia (pasta + workspace + estado), sem worktrees git. |
| create_with_presetC | Cria task e adiciona os projetos do preset (branch default = nome da task). |
| add_projectB | Adiciona um projeto (pelo nome da config) a uma task existente. |
| removeC | Remove um projeto da task ou a task inteira. Exige confirm=true (ou dry_run). |
| statusB | Retorna git status (linhas) de cada projeto da task. |
| syncC | Fetch + rebase/merge na base registrada de cada projeto da task. |
| doctorC | Diagnostica inconsistências; com fix=true tenta corrigir (exige confirm). |
| pruneA | Remove pastas órfãs e worktrees git fantasma. Exige confirm=true (ou dry_run). |
| workspace_pathA | Retorna o path do .code-workspace da task (não abre o editor). |
| open_workspaceC | Abre o .code-workspace no Cursor/VS Code. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools have clear, distinct purposes: listing, creating, syncing, removing, and diagnosing. Minor overlap exists between create_task and create_with_preset, and between remove and add_project, but descriptions clarify the differences.
Names mix styles: some are verb_noun (list_tasks, create_task), while others are bare verbs (sync, remove, status, prune) or noun-ish (workspace_path, open_workspace). This inconsistency makes it less predictable, though still readable.
With 13 tools, the server is well-scoped for managing development tasks and projects. Each tool addresses a distinct need without being overwhelming.
The tool surface covers core lifecycle operations: create, list, resolve, add, remove, sync, status, and maintenance. Minor gaps exist (e.g., no explicit update/rename task), but the set is sufficient for the domain.