Click on "Deploy 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., "@amulen-mcp show me my overdue tasks in AMULEN"
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.
Servidor MCP para AMULEN, la plataforma de gestión de proyectos, tableros y tareas de 3HTP. Permite que asistentes como Claude consulten y actualicen tu trabajo en AMULEN con tus mismos permisos.
Autenticación con token personal (sin contraseña).
Una llamada por herramienta. Los errores (403, 404, 422…) se devuelven con un mensaje claro.
Comentarios y descripciones en Markdown, que AMULEN muestra con formato.
Adjuntos de evidencia: archivos locales o textos generados por el agente.
En AMULEN → Mi Perfil → Tokens de API → Crear token. Copia el valor (amu_…):
se muestra una sola vez. Puedes revocarlo desde el mismo lugar.
Necesitas uv.
AMULEN_BASE_URL es la dirección de AMULEN que usas en el navegador.
Claude Code
claude mcp add amulen -s user \
-e AMULEN_BASE_URL=https://amulen.3htp.cloud \
-e AMULEN_TOKEN=amu_xxx \
-- uvx amulen-mcp@1.2.0Claude Desktop y otros clientes (mcpServers en JSON)
{
"mcpServers": {
"amulen": {
"command": "uvx",
"args": ["amulen-mcp@1.2.0"],
"env": {
"AMULEN_BASE_URL": "https://amulen.3htp.cloud",
"AMULEN_TOKEN": "amu_xxx"
}
}
}
}Fijar la versión (@1.2.0) evita que una actualización te llegue sin aviso. Para actualizar,
cambia el número de versión.
Abre una sesión nueva y pregunta: "¿Tengo tareas en AMULEN?"
Related MCP server: Dot Taskboard MCP Server
Herramienta | Qué hace |
| Usuario del token |
| Tus tareas en todos los proyectos (filtros: estado, proyecto, texto, vencidas) |
| Proyectos accesibles / detalle con tableros |
| Métricas: por estado, vencidas, horas, por usuario, bolsas de horas |
| Miembros con su id (para asignar tareas) |
| Crear / editar proyecto |
| Tableros |
| Tareas de un tablero / detalle con checklist, comentarios y adjuntos |
| Crear / editar (mover de estado, registrar horas reales) |
| Comentar una tarea (Markdown) |
| Checklist |
| Adjuntar evidencia: archivo local ( |
| Ver y descargar adjuntos (a |
No borra tareas, tableros ni proyectos, ni administra usuarios o permisos.
El servidor corre en tu máquina y solo habla con la AMULEN_BASE_URL que configures.
El token actúa con tus permisos. AMULEN registra en la auditoría cada cambio hecho con él.
Si un token se filtra, revócalo en Mi Perfil. Si encuentras una vulnerabilidad, repórtala en privado a los mantenedores (no en un issue público).
Mensaje | Causa |
| Token mal copiado, revocado o expirado |
|
|
| No tienes permisos sobre ese proyecto o tablero |
| El firewall de la red bloqueó la petición antes de llegar a AMULEN |
uv sync
uv run pytestLas versiones se publican en PyPI al crear un tag vX.Y.Z (GitHub Actions, Trusted Publishing).
MIT. Ver LICENSE.
Add one or more checklist items to a task. items: [{"titulo": "...", "descripcion": "..."}] (descripcion optional).
Inputs: items (required), task_slug (required), board_slug (required), project_slug (required).
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).
Inputs: contenido (required), task_slug (required), board_slug (required), project_slug (required), +1 more.
Create a board in a project. bolsa_horas + horas_totales turn it into an hour-budget board.
Inputs: nombre (required), project_slug (required), bolsa_horas, horas_totales.
Create a project. The creator becomes its admin.
Inputs: nombre (required), descripcion.
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).
Inputs: titulo (required), board_slug (required), project_slug (required), estado, +7 more.
Delete a checklist item from a task.
Inputs: item_id (required), task_slug (required), board_slug (required), project_slug (required).
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.
Inputs: task_slug (required), board_slug (required), project_slug (required), attachment_id (required), +1 more.
Get a board with task counts per state and its hour budget (bolsa de horas: total, spent, scheduled, available).
Inputs: board_slug (required), project_slug (required).
Get a project with the boards I can see in it.
Inputs: project_slug (required).
Get a task with description (HTML and plain text), assignees, checklist (with item ids) and comments.
Inputs: task_slug (required), board_slug (required), project_slug (required).
List a task's attachments (id, file name, content type, size).
Inputs: task_slug (required), board_slug (required), project_slug (required).
List the boards of a project that I can see, with their columns (valid states) and whether I can edit them.
Inputs: project_slug (required).
List active project members with their user id and role. Use the ids for task assignment (user_ids).
Inputs: project_slug (required).
List the projects I can access (optionally filtered by name with q).
Inputs: q, limit, offset.
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.
Inputs: board_slug (required), project_slug (required), q, mias, +6 more.
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.
Inputs: q, limit, estado, offset, +2 more.
Project metrics: tasks by state, overdue tasks, hours (projected/real), tasks per user, and per-board hour budgets.
Inputs: project_slug (required).
Update a checklist item (mark completed/uncompleted, rename). Get item ids from amulen_get_task.
Inputs: item_id (required), task_slug (required), board_slug (required), project_slug (required), +3 more.
Rename a project or change its description (project admins only). Note: renaming changes the slug.
Inputs: project_slug (required), nombre, descripcion.
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.
Inputs: task_slug (required), board_slug (required), project_slug (required), estado, +9 more.
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).
Inputs: task_slug (required), board_slug (required), project_slug (required), nombre, +2 more.
Show the AMULEN user behind the configured token (name, email, roles, tenant).
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Manage Timequip projects, tasks, comments, members, and dashboards through MCP.
Read and write Mission Control state via MCP — projects, tasks, subtasks, templates, status updates.
Read and edit your Tasks boards: create and update tasks, comment, and track time.
Read teams, spaces, lists and tasks; create, update and comment on tasks and track time.
