How to Use the LiquidPlanner Classic MCP in CrewAI

Q: How do I pass the LiquidPlanner Classic MCP Server tools to a CrewAI agent?

You add the Vinkius server URL directly to the agent's mcps array configuration. CrewAI automatically discovers tools like listtasks and makes them available to the specified agent.

Q: Can a CrewAI agent create nested tasks in LiquidPlanner Classic?

Yes, an agent can use createtask and supply the correct parentid parameter. This allows the crew to build complex, nested task structures under existing projects.

Q: Can I restrict which MCP tools my agents can access?

Yes, you can use the MCPServerHTTP class with a tool filter to limit access. For example, you can allow agents to run listtasks while blocking them from using createproject.

Deploy a crew of autonomous CrewAI agents to manage LiquidPlanner Classic schedules, assign tasks, and balance workloads.

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 CrewAI

Create your Vinkius account to connect LiquidPlanner Classic to CrewAI 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 CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate multi-agent project planning

`create_project` allows your planning agent to establish new initiatives in your default workspace. While that agent sets up the project container, a second agent uses `create_task` to populate the backlog. CrewAI coordinates these actions sequentially, ensuring tasks are only created after the project container exists. This multi-agent collaboration prevents broken dependencies and keeps your workspaces clean.

Automate resource allocation with CrewAI

`list_members` retrieves the active team list, which your resource allocation agent analyzes to find available people. A separate coordinator agent then assigns tasks based on individual capacity. This division of labor keeps your project schedules realistic. The agents communicate through shared memory to ensure no single developer gets double-booked.

Monitor and adjust task dependencies

`list_tasks` feeds the current task list to a monitoring agent that watches for overdue items. When a delay is found, the agent calculates the downstream impact on other tasks. The moderator agent then uses `update_task` to shift dates and resolve conflicts. Your entire scheduling pipeline runs autonomously without requiring constant manual oversight.

Setup guide

Set up LiquidPlanner Classic MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke LiquidPlanner Classic tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="LiquidPlanner Classic Analyst",
    goal="Access and analyze LiquidPlanner Classic data via MCP.",
    backstory="Expert analyst with direct LiquidPlanner Classic access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent LiquidPlanner Classic transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="LiquidPlanner Classic Analyst",
        goal="Access and analyze LiquidPlanner Classic data via MCP.",
        backstory="Expert analyst with direct LiquidPlanner Classic access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent LiquidPlanner Classic transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 CrewAI

You add the Vinkius server URL directly to the agent's `mcps` array configuration. CrewAI automatically discovers tools like `list_tasks` and makes them available to the specified agent.

Yes, an agent can use `create_task` and supply the correct `parent_id` parameter. This allows the crew to build complex, nested task structures under existing projects.

CrewAI manages agent actions through sequential execution or explicit task definitions. This prevents two agents from calling `update_task` on the same item simultaneously.

Yes, you can use the `MCPServerHTTP` class with a tool filter to limit access. For example, you can allow agents to run `list_tasks` while blocking them from using `create_project`.

Your project schedules, task dependencies, and workspace member IDs are transmitted over encrypted TLS connections. Vinkius processes these MCP requests in sandbox environments that never persist your workspace data.

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