calculate_critical_path — Pathline Project Planner MCP Tool
calculate_critical_path
(calculate critical path) is one of 1 tool on the
Pathline Project Planner
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call calculate_critical_path from your client
- Claude Code Pathline Project Planner calculate_critical_path run in your project directory
- Claude Desktop Pathline Project Planner calculate_critical_path ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Pathline Project Planner calculate_critical_path ~/.cursor/mcp.json
- VS Code Pathline Project Planner calculate_critical_path .vscode/mcp.json
- Zed Pathline Project Planner calculate_critical_path ~/.config/zed/settings.json
- Windsurf Pathline Project Planner calculate_critical_path ~/.codeium/windsurf/mcp_config.json
- Cline Pathline Project Planner calculate_critical_path ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Pathline Project Planner calculate_critical_path ~/.gemini/settings.json
- Grok Pathline Project Planner calculate_critical_path .mcp.json (in your project root)
- ChatGPT Pathline Project Planner calculate_critical_path Settings → Connectors → Advanced → Developer mode
- Claude.ai Pathline Project Planner calculate_critical_path Settings → Connectors → Add custom connector
- LangChain Pathline Project Planner calculate_critical_path pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http critical-path https://critical-path.zovo.one/mcp
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.