amulen-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMULEN_TOKEN | Yes | Token personal de API de AMULEN (empieza por 'amu_'), creado en Mi Perfil → Tokens de API. | |
| AMULEN_BASE_URL | Yes | La dirección de AMULEN que usas en el navegador (por ejemplo, https://amulen.3htp.cloud). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
AMULEN: gestión de proyectos, tableros y tareas (tarjetas). Jerarquía: proyecto (project_slug) → tablero (board_slug) → tarea (task_slug). Para 'mis tareas' usa amulen_my_tasks (una sola llamada). Los slugs que devuelven las herramientas se usan tal cual en las siguientes llamadas. Para asignar usuarios, obtén sus ids con amulen_list_members. Comentarios y descripciones se escriben en Markdown (negritas, listas, tablas, código): AMULEN los muestra con formato. Al leer, usa los campos *_markdown.
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 |
|---|---|
| amulen_whoamiA | Show the AMULEN user behind the configured token (name, email, roles, tenant). |
| amulen_my_tasksA | List tasks assigned to me across all projects and boards, in a single call. estado: states to include (TO DO, DOING, DONE, PENDING, BACKLOG, or ALL). Default: TO DO + DOING. project_slug: limit to one project. q: text search in title/description. vencidas: only tasks whose due date (fecha_fin) already passed. Sorted by due date (soonest first). Use meta.next_offset to paginate. |
| amulen_list_projectsB | List the projects I can access (optionally filtered by name with q). |
| amulen_get_projectB | Get a project with the boards I can see in it. |
| amulen_project_dashboardB | Project metrics: tasks by state, overdue tasks, hours (projected/real), tasks per user, and per-board hour budgets. |
| amulen_list_membersB | List active project members with their user id and role. Use the ids for task assignment (user_ids). |
| amulen_create_projectB | Create a project. The creator becomes its admin. |
| amulen_update_projectA | Rename a project or change its description (project admins only). Note: renaming changes the slug. |
| amulen_list_boardsA | List the boards of a project that I can see, with their columns (valid states) and whether I can edit them. |
| amulen_get_boardB | Get a board with task counts per state and its hour budget (bolsa de horas: total, spent, scheduled, available). |
| amulen_create_boardB | Create a board in a project. bolsa_horas + horas_totales turn it into an hour-budget board. |
| amulen_list_tasksC | List tasks in a board. estado: states to include. mias: only tasks assigned to me. asignado_a: user id. fecha_desde / fecha_hasta: due-date range, format YYYY-MM-DD. q: text search. |
| amulen_get_taskB | Get a task with description (HTML and plain text), assignees, checklist (with item ids) and comments. |
| amulen_create_taskA | Create a task. descripcion is Markdown by default (formato: markdown | html | texto). Dates YYYY-MM-DD. estado defaults to the board's first column. user_ids must be active project members (see amulen_list_members). |
| amulen_update_taskB | Update a task; only the fields you pass change. descripcion is Markdown by default. Use it to move a task (estado) or log real hours (horas_reales). user_ids replaces the whole assignee list. |
| amulen_add_commentB | Add a comment to a task. Write it in Markdown (bold, lists, tables, code blocks, links): AMULEN renders it formatted. formato: markdown (default) | html | texto (no formatting). |
| amulen_add_checklist_itemsC | Add one or more checklist items to a task. items: [{"titulo": "...", "descripcion": "..."}] (descripcion optional). |
| amulen_update_checklist_itemB | Update a checklist item (mark completed/uncompleted, rename). Get item ids from amulen_get_task. |
| amulen_delete_checklist_itemC | Delete a checklist item from a task. |
| amulen_list_attachmentsB | List a task's attachments (id, file name, content type, size). |
| amulen_upload_attachmentA | Attach evidence to a task (max 25 MB). Either file_path: a local file (screenshot, PDF, log, zip...) on this machine; nombre optionally renames it. Or nombre + contenido_texto: a text document you write (e.g. "evidencia.md" with a summary of the work done). |
| amulen_download_attachmentB | Download a task attachment to a local folder (default: ~/Downloads/amulen/<task_slug>/). Returns the saved path so you can open or analyze the file. Never overwrites existing files. |
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 22 tools
Tools are mostly separated cleanly by resource and action across projects, boards, tasks, attachments, checklists, comments, and identity. The main overlap is between amulen_my_tasks and amulen_list_tasks (which also supports 'mias' and 'asignado_a'), but the descriptions clarify cross-project vs board-scoped usage.
Nearly all tools follow a consistent amulen_ prefix plus verb_noun pattern (get_, list_, create_, update_, add_, delete_, upload_, download_). A few exceptions such as amulen_whoami, amulen_my_tasks, and amulen_project_dashboard break strict verb_noun form but remain readable and predictable.
At 22 tools the server is on the high end, but the domain spans projects, boards, tasks, comments, checklists, attachments, and identity, so most tools are justified. It is slightly heavy rather than excessive for the stated scope.
Core read/create/update workflows are covered, including attachment and checklist lifecycle operations. However, there are no delete operations for tasks, projects, or boards, and no member add/remove or comment edit/delete, which are notable gaps for full project management.