How to Use the LiftedWork MCP in CrewAI

Q: How do I connect the LiftedWork server to a CrewAI agent?

Pass the Vinkius HTTP endpoint directly into the mcps parameter when defining your agent. The framework automatically discovers the tools and connects the MCP Server.

Q: How do I limit which LiftedWork tools a CrewAI agent can access?

Use the MCPServerHTTP class from the crewai.mcp module. Apply a toolfilter to expose only the specific MCP tools, like listtimeentries, that a given agent needs.

Run autonomous recruiting teams that manage LiftedWork projects and tasks using CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect LiftedWork MCP to CrewAI

Create your Vinkius account to connect LiftedWork 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 LiftedWork with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-agent coordination for candidate tracking

The `list_tasks` tool exposes the current work queue for your active job seekers. CrewAI coordinates specialized agents, like a researcher who gathers resume data and a coordinator who updates the team on progress. Agents share memory of past interactions, preventing redundant database calls. A coordinator agent can check the task list, while a separate writer agent drafts emails based on those tasks without losing context.

Autonomous project creation and assignment

The `create_project` and `create_task` tools allow autonomous crews to build out complete hiring pipelines. When a new client signs on, your CrewAI manager agent assigns setup duties to subordinate agents who execute these tools sequentially. Your crew handles the handover between agents automatically. One agent pulls client data, and the next agent immediately uses that information to construct the project container.

Filter tools for your CrewAI MCP Server

The `list_time_entries` and `list_clients` tools provide access to sensitive agency operations. This MCP Server integration allows you to filter which tools are exposed to specific agents in your crew. You can restrict your research agent to read-only tools like `list_clients`, while reserving write tools like `create_project` for your manager agent. Doing so keeps your autonomous operations secure and controlled.

Setup guide

Set up LiftedWork 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 LiftedWork tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent LiftedWork 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="LiftedWork Analyst",
        goal="Access and analyze LiftedWork data via MCP.",
        backstory="Expert analyst with direct LiftedWork access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent LiftedWork 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 LiftedWork. 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 LiftedWork 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 LiftedWork MCP in CrewAI

Pass the Vinkius HTTP endpoint directly into the `mcps` parameter when defining your agent. The framework automatically discovers the tools and connects the MCP Server.

Yes. CrewAI agents share access to the configured tools. One agent can read data using `list_tasks` while another creates entries using `create_task` during the same execution loop.

Use the `MCPServerHTTP` class from the `crewai.mcp` module. Apply a `tool_filter` to expose only the specific MCP tools, like `list_time_entries`, that a given agent needs.

Yes. The MCP Server supports both stdio and HTTP transports, letting you run your autonomous crew locally or deploy it to a cloud environment without changing your tool code.

The server processes all client directories and time tracking logs within a zero-trust sandbox. No data is stored on the Vinkius platform, ensuring that candidate hours and business relationships remain completely private.

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