How to Use the LiquidPlanner Classic MCP in Mastra AI

Q: How do I add the LiquidPlanner Classic MCP Server to my Mastra AI agent?

You initialize the MCPClient with the Vinkius URL and then spread the returned tools into your agent configuration. The setup takes under five minutes and gives your agent instant access to your workspaces.

Q: Can Mastra AI workflows pause for human approval before modifying LiquidPlanner Classic?

Yes, you can configure the requireToolApproval option in Mastra AI. This forces the workflow to halt before executing updatetask, letting a manager review the scheduling impact first.

Q: Can I query multiple workspaces using this setup?

The listworkspaces tool allows your agent to discover all accessible environments. You can then target specific workspaces by passing their IDs to getworkspace.

Build automated workflows that update LiquidPlanner Classic schedules and task dependencies using Mastra AI agents.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect LiquidPlanner Classic MCP to Mastra AI

Create your Vinkius account to connect LiquidPlanner Classic to Mastra AI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup LiquidPlanner Classic with Mastra AI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Handle complex scheduling loops with Mastra AI

`update_task` lets your Mastra AI workflows modify active task parameters when external triggers occur. If a developer closes a ticket in your repository, the agent automatically marks the corresponding task as complete in your workspace. Mastra's built-in workflow engine retries failed calls automatically using exponential backoff. This ensures your LiquidPlanner Classic timelines stay accurate even during temporary network hiccups.

Build multi-step project generation pipelines

`create_project` initiates new project folders inside your default workspace based on incoming client requests. The agent reads incoming templates, generates the project, and then populates it with tasks. Using conditional branching, the workflow checks if specific resources are free before assigning tasks. The agent evaluates team availability to prevent over-allocation before writing the data.

Keep team resources aligned automatically

`list_members` pulls the current list of active workspace participants to verify availability. Your agent compares this list against external calendars to spot scheduling conflicts. By exposing this MCP Server to Mastra AI, you build self-healing schedules. The agent reassigns tasks using `update_task` whenever a team member's availability changes.

Setup guide

Set up LiquidPlanner Classic MCP in Mastra AI

Prerequisites

Node.js 18+ and a TypeScript project
@mastra/mcp + @mastra/core packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run npm install @mastra/mcp @mastra/core plus your preferred model provider (e.g. @ai-sdk/openai).
2

Configure the MCPClient
Create an MCPClient with your Vinkius endpoint as a URL object. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Discover and inject tools
Call mcpClient.listTools() and spread the result into your agent's tools object. All LiquidPlanner Classic tools become native Mastra tools.
4

Run with any model
Swap openai("gpt-4o") for any AI SDK-compatible provider. Call agent.generate() and the agent routes tool calls through MCP automatically.

agent.ts

import { MCPClient } from "@mastra/mcp";
import { Agent } from "@mastra/core/agent";
import { openai } from "@ai-sdk/openai";

const mcpClient = new MCPClient({
  id: "liquidplanner-classic-mcp-client",
  servers: {
    "liquidplanner-classic-mcp": {
      url: new URL(
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
      ),
    },
  },
});

const agent = new Agent({
  name: "LiquidPlanner Classic Agent",
  model: openai("gpt-4o"),
  instructions: "You have access to LiquidPlanner Classic tools.",
  tools: {
    ...(await mcpClient.listTools()),
  },
});

const result = await agent.generate(
  "List recent LiquidPlanner Classic transactions"
);
console.log(result.text);

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by LiquidPlanner Classic. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect LiquidPlanner Classic now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about LiquidPlanner Classic MCP in Mastra AI

You initialize the `MCPClient` with the Vinkius URL and then spread the returned tools into your agent configuration. The setup takes under five minutes and gives your agent instant access to your workspaces.

Yes, you can configure the `requireToolApproval` option in Mastra AI. This forces the workflow to halt before executing `update_task`, letting a manager review the scheduling impact first.

The framework handles API limits through its native retry mechanisms. If an `update_task` call triggers a rate limit, the workflow pauses and tries again without losing the update payload.

The `list_workspaces` tool allows your agent to discover all accessible environments. You can then target specific workspaces by passing their IDs to `get_workspace`.

Your project schedules, task dependencies, and workspace member IDs are processed strictly in memory. Vinkius secures this MCP connection using zero-trust network policies, meaning no persistent logs of your project details are ever kept.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript