Task Delay Days

Task Delay Days MCP Connector for Claude

A+

Calculate project schedule variances and task delays.

4 tools Official Updated Oct 1, 2026 Official Vinkius Partner

This MCP server provides precision tools for measuring the temporal gap between planned and actual task completion. Use get_task_delay to find specific task variances, get_batch_delay_summary for high-level project health overviews, check_schedule_compliance to validate delays against tolerance thresholds, and get_project_delay_trend to analyze how delays accumulate monthly.

schedulingdelay-calculationproject-healthvariance-analysistimeline

4 tools expose this connector's capabilities to your AI agent.

check_schedule_compliance

Determines if a specific task or a set of tasks meets a predefined tolerance threshold for delays

get_batch_delay_summary

Aggregates delay data across multiple tasks to provide a high-level overview of project health

get_project_delay_trend

Analyzes how delays are accumulating over time by grouping task delays by their planned completion months

get_task_delay

Calculates the specific number of days a single task is delayed or early

See how to talk to your AI agent using Task Delay Days.

How many days was the task delayed if it was planned for 2024-05-01 and finished on 2024-05-05?

The task was delayed by 4 days.

Is a task compliant if it was planned for 2024-06-10, finished on 2024-06-12, and my tolerance is 3 days?

Yes, the task is compliant as the 2-day delay is within the 3-day tolerance.

What is the total delay for these tasks: [{ 'plannedDate': '2024-01-01', 'actualDate': '2024-01-05' }, { 'plannedDate': '2024-01-10', 'actualDate': '2024-01-08' }]?

The total delay is 2 days.

You can use the `get_task_delay` tool by providing the planned completion date and the actual completion date in ISO 8601 format.

Related Connectors