Bring Predictive Scheduling
to VS Code Copilot
Learn how to connect LiquidPlanner Classic to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings LiquidPlanner Classic data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
LiquidPlanner Classic in VS Code Copilot
LiquidPlanner Classic and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect LiquidPlanner Classic to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.