# LiquidPlanner Classic MCP

> LiquidPlanner Classic connects project scheduling to your AI agent. It lets you build complex project plans and manage resources by understanding task dependencies and team capacity. You can create projects, track tasks, check resource loads against deadlines, and monitor predictive schedules—all through natural conversation.

## Overview
- **Category:** productivity
- **Price:** Free
- **Tags:** predictive-scheduling, resource-leveling, task-dependencies, time-tracking, capacity-planning

## Description

Listen up. This connection lets your AI agent talk directly to LiquidPlanner Classic. It’s how you get sophisticated project planning done using plain conversation, without needing to jump through a dozen menus. You're building out complex plans and managing who does what by understanding dependencies and team bandwidth. Here’s the deal: when your agent runs these tools, it tells you exactly what’s going on in LiquidPlanner.

To start, if you don't know where to look, your agent can run `list_workspaces` to show every single workspace connected to your account. If you need details about a specific environment, it uses `get_workspace` to fetch that info for you. From there, it pulls up all the projects using `list_projects`, giving you a directory of everything defined in your main workspace.

Building out work starts with creating structure. You can call `create_project` and instantly establish a new project record in the default LiquidPlanner space so you’re tracking work right away. Once that's set up, you use `create_task` to add individual tasks to an existing project or folder; remember it needs a parent ID to know where to nest it properly. When you need more tasks later, your agent uses `update_task` to change anything about an existing task—you can adjust the deadline, reassign owners, or modify estimates on the fly.

If you're trying to figure out what a task entails, your agent fetches all the details for one specific piece of work using `get_task`. That gives you everything: who’s assigned it, how much time is estimated, and what other tasks depend on its completion. If you need the full scope of an entire job—the milestones, the status updates, the big picture—it runs `get_project` using a unique project ID. You can also run `list_tasks`, which simply spits out every active task in the default workspace so you don't have to know specific project IDs just to see what’s happening.

When it comes to people, your agent has access to team data. It runs `list_members` to get a list of every person in the default workspace and pulls up their current resource allocation data for planning purposes. If you're looking at the whole picture, running `list_workspaces` shows all connected LiquidPlanner environments so your agent knows exactly where to look when retrieving data.

So, what does this mean for your day-to-day? You can tell it to build out a brand new project and populate it with tasks in minutes. You don't have to manually check who's overloaded or who's got bandwidth—the agent runs resource allocation checks against the list of members, letting you spot underutilized teams or employees swamped by deadlines. It keeps track of everything from the initial task creation all the way up to checking if a project has hit its major milestones. You get accurate status updates and full details on any piece of work right through your chat interface.

## Tools

### create_project
Creates a new project record in the default LiquidPlanner workspace so you can start tracking work immediately.

### create_task
Adds a new task to an existing project or folder, requiring a parent ID for proper nesting and context.

### get_project
Retrieves full details about one specific project using its unique ID, giving you scope, milestones, and status.

### get_task
Fetches all information for a single task, including assignments, estimates, and dependencies. This is great for deep dives.

### get_workspace
Gets details about the entire workspace or specifies a different one if you're working in multiple environments.

### list_members
Lists every team member in the default workspace, providing current resource allocation data for planning.

### list_projects
Retrieves a comprehensive list of all available projects within the configured workspace.

### list_tasks
Lists every task in the default workspace, allowing you to see what's active without knowing specific project IDs.

### list_workspaces
Shows all connected workspaces within LiquidPlanner Classic so your agent knows where to look for data.

### update_task
Changes details on an existing task, such as adjusting the deadline, reassigning owners, or changing estimates.

## Prompt Examples

**Prompt:** 
```
Show all projects and the predicted schedule for the Platform v2 project.
```

**Response:** 
```
Projects: 5. 'Platform v2' (78 tasks), 'Mobile App' (34), 'API Redesign' (22), 'Infrastructure' (15), 'Marketing Site' (12). Platform v2 schedule: Best case: Jun 12. Most likely: Jun 28. Worst case: Jul 15. Progress: 45%. On-time probability: 72%. Critical path: 'Auth Module' → 'API Gateway' → 'Load Testing'. ⚠️ 3 tasks at risk.
```

**Prompt:** 
```
Create a task and show time tracking for the team this week.
```

**Response:** 
```
Task created! 'Implement caching layer' — Best: 8h, Worst: 16h. Assigned: Sarah. Project: API Redesign. Predicted completion: May 2. Time tracking (this week): Team total: 142h. Sarah: 38h (95%), Mike: 35h (88%), Lisa: 32h (80%), James: 22h (55%), Others: 15h. Most time: 'Auth Module' (28h).
```

**Prompt:** 
```
Show workspace members and resource allocation.
```

**Response:** 
```
Workspace members: 8. Resource allocation: Sarah (95% ⚠️ overloaded, 3 projects). Mike (88%, 2 projects). Lisa (80%, 2 projects). James (55%, 1 project). Ana (70%, 2 projects). 3 others at 40-60%. Availability next week: James (40% free), Ana (30%), others fully allocated.
```

## Capabilities

### Generate New Projects
Calls the `create_project` tool to establish a new project record in the default LiquidPlanner workspace.

### Create and Update Tasks
Uses `create_task` or `update_task` to add tasks, set priorities, and modify existing task details within a parent project.

### Retrieve Project Details
Runs the `get_project` tool to fetch all specific data points for a single project ID.

### Check Resource Availability
The agent can run `list_members` and resource allocation checks, identifying overloaded employees or underutilized teams.

### List Project Structures
Uses `list_projects` to provide a full directory of all projects currently defined in the workspace.

### Find Specific Tasks
Retrieves task details using `get_task`, ensuring you have precise information on scope and deadlines.

## Use Cases

### Project Kickoff: Determining Scope
A new initiative needs to start. Instead of creating it in the UI, you tell your agent: 'Start a project for X and list all required team members.' The agent first runs `create_project`, then uses `list_members` to check resource availability before confirming the scope.

### Resource Crunch: Rebalancing Workload
The QA team is swamped. You ask your agent to 'Show me who has capacity next week.' The agent runs `list_members`, spots Sarah at 95%, and recommends moving a low-priority task from her current workload, requiring the use of `update_task`.

### Post-mortem: Understanding Delays
The 'Platform v2' project slipped. You ask your agent to analyze the project schedule using `get_project`. It provides a deep dive, pointing directly to the critical path and identifying exactly which task dependencies caused the delay.

### Discovery: Mapping All Work
You need an inventory of everything. You ask your agent to 'Show me all active projects and their major tasks.' The agent runs `list_projects` then loops through them, calling `list_tasks` for each project ID to give you a complete task breakdown.

## Benefits

- See exactly who's overloaded. Instead of guessing, run `list_members` to check real-time resource allocation against project needs. It tells you which team members are at 95% capacity, flagging potential bottlenecks before they happen.
- Never miss a deadline forecast again. Use the agent to query `get_project` and immediately get predictive schedules (best case, most likely, worst case) for any project in seconds, without opening the UI.
- Maintain clean scope documentation. When you need to adjust something, use `update_task`. You don't have to manually navigate deep into a task's details just to change an estimate or owner; tell your agent to do it.
- Get a full project picture instantly. If you only know the name but not the IDs, run `list_projects` first. Then, use `get_project` with the ID to pull all milestones and deliverables into one clean response.
- Track work scope across teams. The agent lets you list tasks (`list_tasks`) or projects (`list_projects`), giving you a bird's-eye view of what everyone is working on without manually filtering dashboards.

## How It Works

The bottom line is: your agent acts as a universal interface. It takes natural conversation and converts it into specific project management actions.

1. Subscribe to the server, then enter your LiquidPlanner email, password, and Workspace ID.
2. Your AI client sends a request (e.g., 'What is the predicted deadline for Project X?').
3. The agent translates this into tool calls (`get_project` + `list_tasks`), pulls the data, and gives you an answer in plain English.

## Frequently Asked Questions

**How do I check if a team member is overloaded using list_members?**
The agent analyzes resource allocation when you request `list_members`. It provides percentages and flags specific members who are over capacity (e.g., 95% utilization), so you know exactly where the bottleneck is.

**Can I create a new project using create_project?**
Yes, running `create_project` establishes a brand-new container in your default workspace. This lets you immediately start defining tasks and setting up initial milestones for the new initiative.

**What is the difference between list_tasks and get_task?**
`list_tasks` gives you an index—a directory of every task in the workspace. `get_task`, however, requires a specific Task ID to retrieve all associated details, including full dependency lists and owner information.

**How do I update a project's deadline?**
You use the `update_task` tool. You must provide the task's unique ID, then instruct your agent to change the specific field—like updating the estimated completion date or reassigning the owner.

**Do I need get_workspace before working on projects?**
It’s smart to use `get_workspace` first. This confirms which workspace your agent is currently operating in, preventing accidental data writes or reads in the wrong project environment.

**When I use the `create_task` tool, what happens if I want to nest it under a specific project or folder?**
You must provide the parent ID. This ID links the new task directly to an existing container (like a project or folder), ensuring it inherits correct dependencies and organizational structure.

**If I use `get_task` and the ID is incorrect, how does the system handle the error?**
The API sends back a clear error code indicating that no task was found. Your AI client can catch this specific response and prompt you to verify the task ID or list existing tasks using `list_tasks`.

**If I need an overview of all tasks across the entire workspace, should I use `list_projects` first?**
No. Just running `list_tasks` pulls a master inventory of every active task in the default workspace, regardless of which project it belongs to.

**Can I manage tasks with predictive scheduling?**
Yes. Create tasks with best/worst case estimates. LiquidPlanner calculates predictive schedules and deadline probabilities automatically.

**Does LiquidPlanner Classic require three credentials?**
Yes. Requires **Email**, **Password**, and **Workspace ID**. Uses **HTTP Basic Auth** (email:password) against `app.liquidplanner.com/api/workspaces/{id}`.

**Can I track time entries?**
Yes. Access logged time entries per task and team member with effort hours and date ranges.