ProjectManager

Returns tasks that are overdue (past planned finish date and not 100% complete). Optionally filter by assignee name.

get_overdue_tasks

Retrieves detailed information for a single project by ID, including schedule dates, progress, status, description, a URL to open the project in ProjectManager, and a consolidated list of all project and task file attachments (name, type, date, a full download URL, and task ID when attached to a task). Share file URLs so the user can click them. Do not download or fetch file contents yourself. Share the project URL when the user should open the project in PM. Use get_projects first to resolve a project ID from a name. Project ID is the project code (e.g. H2), not a GUID. File download URLs require the same authenticated session as this MCP connection.

get_project

Retrieves the list of members on a project, including their resource ID, name, and permission level. Use get_resources to resolve member names to IDs when creating tasks. Call get_projects first to resolve the project ID (project code, e.g. H2).

get_project_members

Returns pre-calculated project metrics for insights: EVM (BAC, PV, EV, AC, CPI, SPI), burndown series, cost variance rows, cost/hours summary, and progress s-curve points. Call this before generating EVM, burndown, cost, or progress insight charts — use these values in tables and charts; do not recalculate.

get_project_metrics

Returns summary information about a project including name, dates, budget, task counts, and schedule health.

get_project_summary

Returns a list of project tasks with key schedule and progress fields. Use filters to narrow results.

get_project_tasks

Retrieves projects where the currently authenticated user is the assigned manager. Internally resolves the current user's identity; no user ID needs to be provided. Use this when the user wants to see the projects they are responsible for managing, rather than all projects they have access to. For all accessible projects, use get_projects.

get_my_projects

Returns workload summary showing how many open tasks each assignee has on a project.

get_resource_workload

Retrieves the list of available resources (team members) in the workspace, including their ID, name, and email address. Use this before calling create_project to resolve member IDs, or before calling create_task to resolve assignee IDs. If a user refers to a team member by name, call this tool first to look up their resource ID. If a name matches more than one resource, present the options and ask the user to confirm before proceeding.

get_resources

Retrieves full details for a single task by its ID, including name, description, status, assignee, due date, priority, theme, parent project ID, planned and actual dates, costs, effort, WBS, a URL to open the task in ProjectManager, and any file attachments. File attachments are returned as an array containing the name, type, creation date, and a full download URL for each file. Share those file URLs so the user can click them. Do not download or fetch file contents yourself. Share the task URL when the user should open the task in PM. Use this when you already know the task ID. To search for tasks across a project or date range, use get_tasks instead. The project_id returned by this tool can be passed to get_task_statuses when updating a task's status. Planned and actual effort values are returned in minutes but should be displayed in hours and minutes (eg 1hr 30mins not 90mins). plannedCost and actualCost represent material costs only, the total cost of a task is material cost plus resource cost. Create and modify dates are UTC timestamps. Agile users rarely populate the cost and effort fields.

get_task

Retrieves the links from a task (as predecessor) to its successor tasks. Returns, per link, the successor task's ID, link type, and lag. Use this before update_link or delete_link to see a task's existing dependencies.

get_links

Retrieves the list of available task statuses for a given project. Accepts a project ID. Returns each status's ID and name. Use this before calling update_task_status to obtain a valid task_status_id. Statuses are user-defined per project and cannot be assumed. If you only have a task ID, call get_task first to retrieve its project_id, then pass that here.

get_task_statuses

Removes one or more resources from a task's assignees. Requires a task_id and a list of resource IDs. Call get_task first to see who is currently assigned via its assigneeIds field. Removing a resource that is not currently assigned has no effect for that resource. Use add_task_assignees to assign resources instead.

remove_task_assignees

Sets or changes the parent of an existing task, making it a sub-task of the specified parent. Requires a task_id and a parent_task_id. Use this to reorganise task hierarchy after tasks have already been created. To set a parent at creation time, use the parent_task_id parameter on create_task instead; that is more efficient when building a task list from scratch. Both the task and the parent task must belong to the same project.

set_task_parent

Updates one or more fields on an existing project. Accepts the project name, description, target completion date, manager, budget, and free-text status update. Use get_projects first to resolve the project ID. Use get_resources to resolve the manager ID. targetDate is the project's target planned completion date, budget is the proposed project budget, and statusUpdate is free-text progress information (it does not change the project's workflow status). Only supplied fields are updated; omitted fields remain unchanged.

update_project

Updates one or more fields on an existing task by its ID. Accepts the task name, description, percent complete, planned dates, duration, effort, material cost, colour theme, and milestone toggle. percentComplete must be between 0 and 100; plannedDuration and plannedEffort are measured in minutes; and plannedCost represents material cost only, not total cost. Use only a defined theme enum value. Only supplied fields are updated; omitted fields remain unchanged.

update_task

Updates the link type and lag of an existing link between a predecessor task (task_id) and its successor (successor_task_id). Both link_type and lag are required and fully replace the existing values. The link must already exist - use create_link to create one, or get_links to see a task's existing links.

update_link

Updates the priority of a task by its ID. Accepts a task_id and a priority value. Use this when the user wants to raise or lower the urgency of a task. Priority values are fixed and do not vary per project; no lookup step is required.

update_task_priority

Updates the status of a task by its ID. Requires a task_id and a task_status_id. Valid status IDs for a project can be retrieved using get_task_statuses. Always call that tool first to obtain the correct ID, as statuses are user-defined and vary per project. Do not guess or invent status IDs. If the user's intent maps to more than one plausible status, present the options and ask the user to confirm before proceeding.

update_task_status