Bring Staffing
to LlamaIndex
Learn how to connect LiftedWork to LlamaIndex and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the LiftedWork MCP Server?
Connect your LiftedWork account to any AI agent and manage staffing through natural conversation.
What you can do
- Candidate Management — Browse candidates, inspect profiles, and track status
- Placement Tracking — Monitor active placements and contract details
- Job Listings — List open positions and their requirements
How it works
1. Subscribe to this server
2. Enter your LiftedWork API Key
3. Start managing staffing from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Recruiters — manage candidate pipelines and placements
- HR Teams — track open positions and applications
- Staffing Agencies — monitor active placements
Built-in capabilities (6)
Create a new project
Pass task data as a JSON string. Create a new task
List all clients
List all projects
List all agency tasks
List all time tracking entries
Why LlamaIndex?
LlamaIndex agents combine LiftedWork tool responses with indexed documents for comprehensive, grounded answers. Connect 6 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine LiftedWork tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain LiftedWork tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query LiftedWork, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what LiftedWork tools were called, what data was returned, and how it influenced the final answer
LiftedWork in LlamaIndex
LiftedWork and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect LiftedWork to LlamaIndex 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 LiftedWork in LlamaIndex
The LiftedWork 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 6 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LlamaIndex 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
LiftedWork for LlamaIndex
Every tool call from LlamaIndex to the LiftedWork 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 candidates and track placements?
Yes. Browse candidate profiles, track their status through the pipeline, and monitor active placements with contract details.
Can I browse open positions?
Yes. List all open job listings with requirements, location, and application counts.
What API does LiftedWork use?
Bearer authentication against api.liftedwork.com/v1.
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query LiftedWork tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp
