Bring Predictive Scheduling
to Claude Desktop
Learn how to connect LiquidPlanner Classic to Claude Desktop and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the LiquidPlanner Classic MCP Server?
Connect your LiquidPlanner Classic workspace to any AI agent and manage project planning through natural conversation.
What you can do
- Task Management — Create, update, and assign tasks with priority and estimates
- Project Tracking — Browse projects, milestones, and deliverables
- Timeline Monitoring — Track predictive schedules and deadline forecasts
- Workspace Browsing — Navigate workspace structure and team members
- Time Tracking — Access logged time and effort data
How it works
1. Subscribe to this server
2. Enter your LiquidPlanner email, password, and Workspace ID
3. Start managing projects from Claude, Cursor, or any MCP-compatible client
Who is this for?
- PMs — manage predictive project schedules
- Teams — track tasks and time entries
- Executives — monitor deadline forecasts and resource allocation
Built-in capabilities (10)
Create a new project in the default workspace
Requires parent_id if it should be nested under a project or folder. Create a new task in the default workspace
Get details of a specific project
Get details of a specific task
Uses the default configured workspace if no ID is provided. Get details of a specific workspace or the default workspace
List members in the default workspace
List projects in the default workspace
List tasks in the default workspace
List workspaces from LiquidPlanner Classic
Update an existing task in the default workspace
Why Claude Desktop?
Claude Desktop is the definitive way to connect LiquidPlanner Classic to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
LiquidPlanner Classic in Claude Desktop
LiquidPlanner Classic and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect LiquidPlanner Classic to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for LiquidPlanner Classic in Claude Desktop
The LiquidPlanner Classic MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
LiquidPlanner Classic for Claude Desktop
Every tool call from Claude Desktop to the LiquidPlanner Classic MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.