plan_project_timeline — Zovo Project Timeline MCP Tool
plan_project_timeline
(plan project timeline) is one of 2 tools on the
Zovo Project Timeline
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call plan_project_timeline from your client
- Claude Code Zovo Project Timeline plan_project_timeline run in your project directory
- Claude Desktop Zovo Project Timeline plan_project_timeline ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Zovo Project Timeline plan_project_timeline ~/.cursor/mcp.json
- VS Code Zovo Project Timeline plan_project_timeline .vscode/mcp.json
- Zed Zovo Project Timeline plan_project_timeline ~/.config/zed/settings.json
- Windsurf Zovo Project Timeline plan_project_timeline ~/.codeium/windsurf/mcp_config.json
- Cline Zovo Project Timeline plan_project_timeline ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Zovo Project Timeline plan_project_timeline ~/.gemini/settings.json
- Grok Zovo Project Timeline plan_project_timeline .mcp.json (in your project root)
- ChatGPT Zovo Project Timeline plan_project_timeline Settings → Connectors → Advanced → Developer mode
- Claude.ai Zovo Project Timeline plan_project_timeline Settings → Connectors → Add custom connector
- LangChain Zovo Project Timeline plan_project_timeline pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http gantt-timeline https://gantt-timeline.zovo.one/mcpOther tools on this server
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.