Pathline Project Planner

io.github.theluckystrikePublished by GitHub account theluckystrikev1.0.0Updated Oct 26, 2026

Project planning tool for critical path calculations.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server that computes a project's critical path, duration, task start/finish times and slack from tasks and dependencies.

What you can do
  • Calculate the critical path and overall project duration from explicit task durations and dependencies
  • Get earliest and latest start and finish times for each task
  • Report task slack to see which activities have float
  • Work with up to 40 tasks and up to 160 finish-to-start dependencies
When to use it
Useful when a user wants schedule analysis of a project plan — identifying the critical path, total duration, or which tasks have slack — and can supply task durations and dependencies explicitly.
Requirements
A remote streamable HTTP endpoint; no package installation, account, API key or environment variables are declared.
Before you install
The calculation depends entirely on the durations and dependencies supplied; results are only as good as that input. No authentication is declared for the endpoint, so avoid sending confidential project data.

Installation

In SourceWeft

  1. Open Pathline Project Planner in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.theluckystrike%2Fcritical-path/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "pathline-project-planner": {
      "type": "http",
      "url": "https://critical-path.zovo.one/mcp"
    }
  }
}

Tools

1

calculate_critical_path

Calculate critical path

Use this when the user wants a critical path calculation, project duration, earliest/latest task starts and finishes, or task slack from explicit durations and dependencies. Accepts one to forty tasks, at most 160 finish-to-start dependencies, and durations with at most three decimal places. Includes parallel critical tasks and a CSV schedule. Does not schedule calendar dates, generate Gantt charts, account for resources or holidays, or infer missing task durations.

Parametersunittasksrequiredproject

Version history

1
  1. v1.0.0LatestOct 22, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.