Lever with LlamaIndex

How to integrate Lever MCP with LlamaIndex

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

Introduction Also integrate Lever with TL;DR What is LlamaIndex What is the Lever MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Composio SDK Step-by-step Guide Complete Code Conclusion How to build Lever MCP Agent with another framework Explore Other Toolkits FAQ

Connect Lever without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

Introduction

This guide walks you through connecting Lever to LlamaIndex using the Composio tool router. By the end, you'll have a working Lever agent that can list all open job postings, get candidate details by email, schedule interview for specific candidate through natural language commands.

This guide will help you understand how to give your LlamaIndex agent real control over a Lever account through Composio's Lever MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Lever with

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI CrewAI

TL;DR

Here's what you'll learn:

Set your OpenAI and Composio API keys
Install LlamaIndex and Composio packages
Create a Composio Tool Router session for Lever
Connect LlamaIndex to the Lever MCP server
Build a Lever-powered agent using LlamaIndex
Interact with Lever through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

ReAct Agent: Reasoning and acting pattern for tool-using agents
MCP Tools: Native support for Model Context Protocol
Context Management: Maintain conversation context across interactions
Async Support: Built for async/await patterns

What is the Lever MCP server, and what's possible with it?

The Lever MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Lever account. It provides structured and secure access to your recruiting pipeline, so your agent can perform actions like managing candidates, scheduling interviews, updating job postings, tracking offers, and analyzing hiring metrics on your behalf.

End-to-end candidate management: Let your agent add, update, or move candidates through different stages of your hiring process seamlessly.
Automated interview scheduling: Have the agent create, modify, or cancel interviews and coordinate with both candidates and interviewers to streamline the process.
Job posting and requisition updates: Direct your agent to create new job postings, update existing requisitions, or close filled roles instantly.
Offer and feedback tracking: Enable your agent to manage offer letters, track acceptance rates, and collect structured feedback from interviewers.
Recruiting analytics and reporting: Ask the agent to generate reports on pipeline activity, source effectiveness, and diversity metrics—helping you make data-driven hiring decisions.

Supported Tools & Triggers

Tools

Add Opportunity LinksTool to add links to a contact associated with an opportunity.

Add Opportunity SourcesTool to add sources to an opportunity.

Add Opportunity TagsTool to add tags to an opportunity.

Create Form SubmissionTool to create a completed profile form submission for a candidate's opportunity profile.

Create Form TemplateTool to create a profile form template for an account.

Create InterviewTool to create an interview on an externally-managed panel in Lever.

Create NoteTool to create a note on an opportunity profile or add a threaded comment to an existing note.

Create OpportunityTool to create a new candidate opportunity in Lever.

Create PanelTool to create a new interview panel for an opportunity.

Create RequisitionTool to create a new requisition in Lever for tracking hiring needs.

Create Requisition FieldTool to create a custom requisition field schema for use across requisitions.

Create Requisition Field OptionTool to add new options to a dropdown requisition field without replacing existing options.

Upload FileTool to upload a file temporarily to Lever for use with posting applications.

Create UserTool to create a new user in the Lever system.

Deactivate UserTool to deactivate a user in the Lever system.

Delete Form TemplateTool to delete a profile form template from account.

Delete InterviewTool to delete an interview from an opportunity panel.

Delete NoteTool to delete a note on an opportunity.

Delete PanelTool to delete a panel from an opportunity.

Delete RequisitionTool to delete or archive a requisition from Lever account.

Delete Requisition FieldTool to delete a requisition field from the account.

Delete Requisition Field OptionTool to remove specific options from a dropdown requisition field.

Download FileTool to download a file associated with an opportunity.

Get File MetadataTool to retrieve metadata for a single file on an opportunity.

Get FormTool to retrieve a specific profile form for an opportunity.

Get Form TemplateTool to retrieve a single form template by unique identifier.

Get InterviewTool to retrieve a single interview for an opportunity.

Get NoteTool to retrieve a single note for an opportunity.

Get OpportunityTool to retrieve detailed information about a single opportunity.

Get PanelTool to retrieve a single interview panel for an opportunity.

Get RequisitionTool to retrieve detailed information about a single requisition by ID.

Get Requisition FieldTool to retrieve detailed information about a single custom requisition field by ID.

Get StageTool to retrieve detailed information about a single stage by its UUID.

Get UserTool to retrieve detailed information about a single user by their UUID.

List Opportunity FilesTool to list all files on an opportunity.

List FormsTool to list all profile forms for an opportunity.

List Form TemplatesTool to list all active form templates.

List InterviewsTool to list all interviews for an opportunity.

List NotesTool to list notes on an opportunity profile.

List OffersTool to list offers for an opportunity.

List OpportunitiesTool to list all opportunities in the hiring pipeline.

List PanelsTool to list all interview panels for an opportunity.

List PostingsTool to list all job postings including published, internal, closed, draft, pending, and rejected postings.

List ReferralsTool to list all referrals for an opportunity.

List Requisition FieldsTool to list all requisition field schemas in your Lever account with optional filtering.

List RequisitionsTool to list all requisitions with filtering and pagination.

List Opportunity ResumesTool to list all resumes for an opportunity.

List SourcesTool to list all recruitment sources in your Lever account.

List StagesTool to retrieve all pipeline stages in your Lever account.

List TagsTool to list all tags in your Lever account.

List UsersTool to retrieve all active users in your Lever account with optional filters.

Reactivate UserTool to reactivate a previously deactivated user in the Lever system.

Remove Contact Links by OpportunityTool to remove links from a contact associated with an opportunity.

Remove Opportunity SourcesTool to remove sources from an opportunity.

Remove Opportunity TagsTool to remove tags from an opportunity.

Update Form TemplateTool to update an existing profile form template.

Update InterviewTool to update an interview on an externally-managed panel.

Update NoteTool to update a note on an opportunity profile.

Update PanelTool to update an externally-managed panel for an opportunity.

Update RequisitionTool to update an existing requisition in Lever.

Update Requisition FieldTool to update an existing requisition field in Lever.

Update Requisition Field OptionTool to update existing options in a dropdown requisition field without replacing the entire field object.

Update UserTool to update an existing user in the Lever system.

Upload File to OpportunityTool to upload a file permanently to an opportunity.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before you begin, make sure you have:

Python 3.8/Node 16 or higher installed
A Composio account with the API key
An OpenAI API key
A Lever account and project
Basic familiarity with async Python/Typescript

Getting API Keys for OpenAI, Composio, and Lever

OpenAI API key (OPENAI_API_KEY)

Go to the OpenAI dashboard
Create an API key if you don't have one
Assign it to OPENAI_API_KEY in .env

Composio API key and user ID

Log into the Composio dashboard
Copy your API key from Settings
- Use this as COMPOSIO_API_KEY
Pick a stable user identifier (email or ID)
- Use this as COMPOSIO_USER_ID

Installing dependencies

pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv

Create a new Python project and install the necessary dependencies:

composio-llamaindex: Composio's LlamaIndex integration
llama-index: Core LlamaIndex framework
llama-index-llms-openai: OpenAI LLM integration
llama-index-tools-mcp: MCP client for LlamaIndex
python-dotenv: Environment variable management

Set environment variables

bash

OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

Authenticate with OpenAI's GPT-5 model
Connect to Composio's Tool Router
Identify your Composio user session for Lever access

Import modules

import asyncio
import os
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

Create a new file called lever_llamaindex_agent.py and import the required modules:

Key imports:

asyncio: For async/await support
Composio: Main client for Composio services
LlamaIndexProvider: Adapts Composio tools for LlamaIndex
ReActAgent: LlamaIndex's reasoning and action agent
BasicMCPClient: Connects to MCP endpoints
McpToolSpec: Converts MCP tools to LlamaIndex format

Load environment variables and initialize Composio

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set in the environment")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment")

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

Create a Tool Router session and build the agent function

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["lever"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")

    description = "An agent that uses Composio Tool Router MCP tools to perform Lever actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Lever actions.
    """
    return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True)

What's happening here:

We create a Composio client using your API key and configure it with the LlamaIndex provider
We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, lever)
The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
LlamaIndex will connect to this endpoint to dynamically discover and use the available Lever tools.
The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.

Create an interactive chat loop

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

What's happening here:

We're creating a direct terminal interface to chat with your Lever database
The LLM's responses are streamed to the CLI for faster interaction.
The agent uses context to maintain conversation history
You can type 'quit' or 'exit' to stop the chat loop gracefully
Agent responses and any errors are displayed in a clear, readable format

Define the main entry point

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

What's happening here:

We're orchestrating the entire application flow
The agent gets built with proper error handling
Then we kick off the interactive chat loop so you can start talking to Lever

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Lever, then start asking questions.

Complete Code

Here's the complete code to get you started with Lever and LlamaIndex:

import asyncio
import os
import signal
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["lever"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")
    description = "An agent that uses Composio Tool Router MCP tools to perform Lever actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Lever actions.
    """
    return ReActAgent(
        tools=tools,
        llm=llm,
        description=description,
        system_prompt=system_prompt,
        verbose=True,
    );

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

Conclusion

You've successfully connected Lever to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:

Tool Router dynamically exposes Lever tools through an MCP endpoint
LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
The agent becomes more capable without increasing prompt size
Async Python provides clean, efficient execution of agent workflows

You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.

How to build Lever MCP Agent with another framework

OpenAI Agents SDK

Use Lever MCP with OpenAI Agents SDK

Claude Agent SDK

Use Lever MCP with Claude Agent SDK

Claude Code

Use Lever MCP with Claude Code

Claude Cowork

Use Lever MCP with Claude Cowork

Codex

Use Lever MCP with Codex

OpenClaw

Use Lever MCP with OpenClaw

Hermes

Use Lever MCP with Hermes

CLI

Use Lever MCP with CLI

Google ADK

Use Lever MCP with Google ADK

LangChain

Use Lever MCP with LangChain

Vercel AI SDK

Use Lever MCP with Vercel AI SDK

Mastra AI

Use Lever MCP with Mastra AI

CrewAI

Use Lever MCP with CrewAI

Explore Other Toolkits

Ashby

Api Key

Ashby is an applicant tracking system that handles job postings, candidate management, and hiring analytics.

Async interview

Api Key

Async interview is an on-demand video interview platform for streamlined hiring. Candidates record responses on their schedule, so employers can review anytime.

Bamboohr

Oauth2Api Key

BambooHR is a cloud-based HR management platform for small and mid-sized businesses. It streamlines employee data, HR workflows, and reporting in one easy interface.

TOOLKIT MARKETPLACE

FAQ

What are the differences in Tool Router MCP and Lever MCP?

With a standalone Lever MCP server, the agents and LLMs can only access a fixed set of Lever tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Lever and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with LlamaIndex?

Yes, you can. LlamaIndex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Lever tools.

Can I manage the permissions and scopes for Lever while using Tool Router?

Yes, absolutely. You can configure which Lever scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Lever data and credentials are handled as safely as possible.

Used by agents from

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for free Get a demo↗

Harsha GaddipatiCo-founder, Slashy

Karan skipped his own birthday party to fix our critical issue. It was 10 pm and he diverted his Waymo to help us instead. This really sets the bar, shows you the commitment you need to have when users rely on your software.

Abhi AryaCo-founder, Opennote

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

We chose Composio over Pipedream because it delivered depth where it mattered. It supported niche tools and tricky edge cases that other platforms simply ignored. Giving us confidence to scale without compromising.

Ryan YuFounder, Extra Thursday

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down in the complexities of managing agent auth would have been a death sentence for Extra Thursday.

Tomisin JenrolaFounder & CEO, SwarmZero

Before partnering with Composio, adding tool integrations was a slow, resource-intensive process. Each integration could take weeks or months of engineering time, and maintaining them meant constantly keeping up with API changes.

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

How to integrate Lever MCP with LlamaIndex

Table of Contents

Connect Lever without Auth hassles

Introduction

Also integrate Lever with

TL;DR

What is LlamaIndex?

What is the Lever MCP server, and what's possible with it?

Supported Tools & Triggers

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI, Composio, and Lever

Installing dependencies

Set environment variables

Import modules

Load environment variables and initialize Composio

Create a Tool Router session and build the agent function

Create an interactive chat loop

Define the main entry point

Run the agent

Complete Code

Conclusion

How to build Lever MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

CrewAI

Explore Other Toolkits

Ashby

Async interview

Bamboohr

FAQ

What are the differences in Tool Router MCP and Lever MCP?

Can I use Tool Router MCP with LlamaIndex?

Can I manage the permissions and scopes for Lever while using Tool Router?

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability