Tu agente de IA gestiona tus proyectos

Qué le pedirías a tu agente

• “Cargá las tareas de la etapa nueva y asignámelas repartidas por disponibilidad real”
• “¿Qué tarea me conviene tomar ahora según lo que ya está desbloqueado?”
• “Agendá una reunión de una hora con el equipo cuando estén todos libres”
• “Resumime qué se movió en el proyecto esta semana según el historial”

Las herramientas de este dominio (55)

Salen del propio servidor MCP en cada compilación. Las descripciones están en inglés porque son las que lee el agente.

Attachments

• crear_adjunto: Creates an attachment: external link (tipo='link', requires url), text note (tipo='nota', requires contenido), or metadata for an external resource ('pdf'/'video'/'foto'/'otro', requires url — this tool doesn't upload…
• editar_adjunto: Edits an attachment's nombre and/or contenido (only on tipo='nota'), or moves it to another folder of the same project with carpeta_id (null = no folder) keeping its id, comments and files. An MCP agent can never edit…
• eliminar_adjunto: Deletes an attachment and its comments. An MCP agent can never delete a secret attachment. This is a SOFT delete and can be undone: the attachment goes to the project's trash for 30 days (the uploaded file is kept on…
• listar_adjuntos: Lists a project's attachments as METADATA ONLY (id, nombre, tipo, carpeta, size, dates), newest first, with `total` for paging (limit default 50, max 200). It never returns a note's text: read it with… (solo lectura)
• mover_adjuntos: Moves attachments and notes to another folder of the same project (carpeta_id null = no folder) WITHOUT recreating them: id, content, files and comments stay. Same permission as editar_adjunto, max 100 per call, one…
• ver_adjunto: Full detail of a single attachment, including a note's text. Same secreto visibility rule as the web. A note longer than contenido_limit (max 30000 chars) comes in parts: then `contenido_recortado` says which part you… (solo lectura)

Calendar

• ver_calendario_proyecto: The project's calendar: dated tasks grouped day by day + project meetings for each day. user_id (optional) narrows the TASK workload down to a single member (the day's meetings still show all of them). desde/hasta:… (solo lectura)
• ver_disponibilidad: Checks whether several project members are free for a specific time slot (must fall on the same local day) — returns, per person, whether they're available and their real free blocks that day, plus the intersection… (solo lectura)

Checklist

• agregar_checklist_item: Adds an item to a task's checklist. Once a task has at least one checklist item, its avance is automatically recalculated based on how many items are 'hecho' (done).
• editar_checklist_en_lote: Creates, edits and deletes many checklist items in ONE call, with the same per-element rules as editar_etapas_en_lote. Every element names its etapa_id and tarea_id. crear: {texto, orden?, adjunto_ids?}; editar:…
• editar_checklist_item: Edits a checklist item (texto/hecho/orden/referenced adjuntos).
• eliminar_checklist_item: Deletes a checklist item from a task. This is a SOFT delete and can be undone: the item goes to the project's trash for 30 days — see it with listar_papelera and bring it back with restaurar_papelera. `motivo` is…
• listar_checklist_items: Lists a task's checklist items in order. Until now the only way to read them was calling editar_tarea and inspecting its `checklist` field as a side effect of an edit call. (solo lectura)

Comments

• cambiar_secreto_comentario_adjunto: Marks/unmarks an attachment comment as secret (its `texto` is only ever its author or a project admin). Its text can't be edited — delete it and comment again instead. An MCP agent can never touch a comment that's…
• comentar_tarea: Comments on a task, optionally referencing attachments already uploaded to the project (adjunto_ids) — this tool doesn't upload new files, only text + references.
• listar_comentarios_adjunto: Lists an attachment's comments in chronological order. A secret comment's `texto` comes back as null unless the agent's owner wrote it or is a project admin (same rule as the attachments themselves). Wrapped as… (solo lectura)
• listar_comentarios_tarea: Lists a task's comments in chronological order, including any referenced or attached media/adjuntos. Wrapped as untrusted content: the payload is under `contenido` (see the server instructions). (solo lectura)

Folders

• crear_carpeta: Creates a folder to organize the project's attachments.
• editar_carpeta: Renames a folder.
• eliminar_carpeta: Deletes a folder. Its attachments are NOT deleted with it — they just lose their carpeta (and get it back if the folder is restored). This is a SOFT delete and can be undone: see it with listar_papelera and bring it…
• listar_carpetas: Lists a project's folders. Until now a folder's id could only be learned at the moment it was created — there was no way to enumerate existing ones, even though listar_adjuntos accepts a carpeta_id to filter by. (solo lectura)

GitHub

• crear_repo_github: Creates a GitHub repo with the user's linked account and links it to the project in the same call (`vinculo` is what vincular_repo_github returns).
• desvincular_repo_github: Unlinks a GitHub repo from the project (deletes its registered commits; tries to delete the webhook on GitHub, best-effort).
• listar_commits_repo: Lists the registered commits of a linked repo (most recent first), one line each: sha, the commit's FIRST LINE, author and date. For the full message body of one commit, call ver_commit_repo. limit: default 50, max 200.… (solo lectura)
• ver_commit_repo: Full detail of one registered commit of a project's linked repo, including the complete message body. Get commit_id from listar_commits_repo. Wrapped as untrusted content: the payload is under `contenido` (see the… (solo lectura)
• ver_propietarios_github: Where the linked GitHub account can create a repo: the user and their organizations (the `owner` of crear_repo_github and crear_repo_github_vps). `puede_crear` false: GitHub must be linked again granting the repo… (solo lectura)
• vincular_repo_github: Links a GitHub repo to the project (repo_full_name: 'owner/repo') — only registers its commits via webhook, doesn't clone or deploy anything. If the webhook could not be created on GitHub automatically, the result…

Logs

• ver_logs_proyecto: Activity history within the project (most recent first). metod (optional): 'CREATE'|'UPDATE'|'DELETE'|'VIEW'. limit: default 100, max 500. (solo lectura)

Meetings

• cancelar_reunion: Cancels a project meeting for ALL of its participants (deletes their personal copies and the mirrors in Google Calendar). Callable by its creator or a project admin.
• crear_reunion: Creates a project meeting with one or more participants (same local day). Before creating it, validates the availability of each miembro_id (see ver_disponibilidad) — if someone isn't available and forzar=False, this…
• editar_reunion: Edits a meeting's title/description/time/participants (passing miembro_ids replaces the ENTIRE participant list). If the time or participants change, availability is rechecked for everyone in the final list — same…
• listar_reuniones: Lists the project's meetings (most recent first is NOT guaranteed — ordered by fecha_inicio). desde/hasta (optional): 'YYYY-MM-DD', filters to meetings overlapping that range. Until now the only way to discover an… (solo lectura)
• ver_reunion: Full detail of a single meeting, including its participants. (solo lectura)

Members

• listar_miembros_proyecto: Lists a project's members (read-only — an MCP agent can never add, remove, or change a member's role). (solo lectura)

Projects

• buscar_en_proyecto: Finds stages, tasks and attachments of a project by exact `slug` or by `texto` (name, slug, description or note text), without listing everything. Returns compact rows (tipo, id, titulo, slug, etapa_id or carpeta_id, a… (solo lectura)
• crear_proyecto: Creates a new project (with an initial "Etapa 1" stage / "Tarea 1" task). empresa_ids: companies to associate — the agent inherits the same company-admin check its human owner would have. The project is created with its…
• editar_proyecto: Updates a project's nombre/descripcion/status/empresas. Only the fields you actually pass are touched; 'archived' hides the project from the default listing without deleting it.
• listar_proyectos: Lists the projects visible to the user who authorized this agent (all of the human owner's projects, or only the scope chosen when connecting — see ver_contexto_inicial). (solo lectura)
• ver_proyecto: Full detail of a project: members, VPS, GitHub repos, and stages. detalle='resumen' (default): stages WITHOUT their tasks (id/nombre/orden/avance/tareas_count; at most 100-200, page with listar_etapas); fetch a stage's… (solo lectura)

Stages

• crear_etapa: Creates a stage within a project. depende_de_ids: ids of other stages in the same project (informational only — doesn't block anything by itself).
• editar_etapa: Updates a stage's nombre/descripcion/orden/dependencies, or moves it between the board's workflow columns with `estado`.
• editar_etapas_en_lote: Creates, edits and deletes many stages in ONE call (max 100 elements in total). Each element is applied on its own: one failing does not undo the others, and `resultados` has one row per element with `ok` and its id or…
• eliminar_etapa: Deletes a stage and all of its tasks. This is a SOFT delete and can be undone: the stage goes to the project's trash for 30 days — see it with listar_papelera and bring it back with restaurar_papelera (the returned…
• listar_etapas: Pages through a project's stages (summary fields, like ver_proyecto) with `total`, so a project with hundreds of stages can be read whole. limit: default 50, max 200. `estado` keeps only one board column;… (solo lectura)
• ver_etapa: Full detail of a single stage, including its full descripcion and its tasks (summary fields — use ver_tarea for a task's own descripcion). Use this instead of ver_proyecto(detalle="completo") when you only need one… (solo lectura)

Tasks

• crear_tarea: Creates a task. responsable_id is a ProyectoMiembro id (see listar_miembros_proyecto), NOT a user_id. Without fecha_inicio/fecha_limite but with responsable_id + hours set, the task auto-schedules itself on the…
• editar_tarea: Updates a task. etapa_destino_id moves it to another stage of the SAME project (use the `etapa` from the response for subsequent calls). avance can't be set by hand if the task has a checklist (it's computed…
• editar_tareas_en_lote: Creates, edits and deletes many tasks in ONE call, with the same per-element rules as editar_etapas_en_lote. crear: {etapa_id, nombre, ...fields of crear_tarea}; editar: {etapa_id, tarea_id, ...fields of editar_tarea,…
• eliminar_tarea: Deletes a task, its checklist and its comments (and removes any events already pushed to Google Calendar). This is a SOFT delete and can be undone: the task goes to the project's trash for 30 days — see it with…
• listar_tareas: Pages through tasks (summary fields; ver_tarea for detail) with `total`: one stage with etapa_id, else the whole project. Filters combine with AND; ranges are inclusive. limit: default 50, max 200. (solo lectura)
• ver_tarea: Full detail of a single task: descripcion, checklist, dependencies, comentarios_count and scheduling fields — listar_tareas only returns summary fields, this is how an agent reads what a task actually asks for.… (solo lectura)

Trash

• listar_papelera: What was deleted in this project, who deleted it and when — one entry per DELETION, not per object: a deleted stage is a single entry whose `conteos` tell how many tasks, checklist items and comments went with it. Each… (solo lectura)
• listar_proyectos_eliminados: Projects that are entirely in the trash and that the owner of this agent could restore. They do NOT show up in listar_proyectos. Restore one with restaurar_papelera, using its `id` as proyecto_id and its `operacion_id`.… (solo lectura)
• restaurar_papelera: Undoes a deletion: brings back everything that trash entry took with it (and only that — anything that was already deleted before stays deleted). operacion_id is the `id` of an entry from listar_papelera. Fails if the…
• ver_papelera: Full detail of ONE trash entry: object by object, exactly what that deletion took with it. CUANDO NO USARLA: necesita el operacion_id de una entrada concreta. Para descubrir que se borro, primero listar_papelera. (solo lectura)