upsprint-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UPSPRINT_EMAIL | No | Email of the Upsprints user. Required for read tools. | |
| UPSPRINT_API_URL | No | Base URL of the Upsprints API (e.g., http://localhost:9002). Required for read tools. | |
| UPSPRINT_PASSWORD | No | Password of the Upsprints user. Required for read tools. | |
| UPSPRINT_COMPANY_ID | No | Optional company ID to auto-select on login. | |
| UPSPRINT_WEBHOOK_URL | No | Webhook endpoint URL. Default: https://api.upsprints.com.br/webhooks/upsprint | https://api.upsprints.com.br/webhooks/upsprint |
| UPSPRINT_WEBHOOK_TOKEN | No | Token from Webhooks > Tokens (e.g., ups_...). Required for write tools. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_taskB | Cria uma nova task em um projeto via webhook (action createTask). Suporta campos personalizados de formulário via metadata. |
| update_taskA | Atualiza campos de uma task existente sem movê-la (action updateTask). Pelo menos um campo em "updates" é obrigatório. Útil para anexar o SDD gerado na descrição. |
| move_taskB | Move uma task para outra coluna do board (action moveTask). A coluna atual é detectada automaticamente. |
| move_task_and_updateB | Move uma task para outra coluna e atualiza campos na mesma operação (action moveTaskAndUpdate). |
| assign_taskC | Atribui uma task a um usuário específico (action assignTask). |
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 5 tools
Each tool targets a distinct operation (create, update, move, combine move+update, assign), but move_task and move_task_and_update could cause minor confusion for agents deciding between separate calls or a combined operation.
All tool names follow a strict verb_noun pattern using snake_case (create_task, update_task, move_task, etc.), making the naming highly predictable and consistent.
With 5 tools covering core task actions, the count is well-scoped for a focused task management server, neither too sparse nor excessive.
The set covers create, update, move, and assign operations, but lacks delete and any retrieval/list functionality, which may leave agents unable to fully manage the task lifecycle.