Lever with Vercel AI SDK

How to integrate Lever MCP with Vercel AI SDK v6

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 Vercel AI SDK 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 Vercel AI SDK v6 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 Vercel AI SDK 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 Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

How to set up and configure a Vercel AI SDK agent with Lever integration
Using Composio's Tool Router to dynamically load and access Lever tools
Creating an MCP client connection using HTTP transport
Building an interactive CLI chat interface with conversation history management
Handling tool calls and results within the Vercel AI SDK framework

What is Vercel AI SDK?

The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state.

Key features include:

streamText: Core function for streaming responses with real-time tool support
MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp
Step Counting: Control multi-step tool execution with stopWhen: stepCountIs()
OpenAI Provider: Native integration with OpenAI models

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:

Node.js and npm installed
A Composio account with API key
An OpenAI API key

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
Keep the API key safe.

Composio API Key

Log in to the Composio dashboard.
Navigate to your API settings and generate a new API key.
Store this key securely as you'll need it for authentication.

Install required dependencies

bash

npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv

First, install the necessary packages for your project.

What you're installing:

@ai-sdk/openai: Vercel AI SDK's OpenAI provider
@ai-sdk/mcp: MCP client for Vercel AI SDK
@composio/core: Composio SDK for tool integration
ai: Core Vercel AI SDK
dotenv: Environment variable management

Set up environment variables

bash

OPENAI_API_KEY=your_openai_api_key_here
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here

Create a .env file in your project root.

What's needed:

OPENAI_API_KEY: Your OpenAI API key for GPT model access
COMPOSIO_API_KEY: Your Composio API key for tool access
COMPOSIO_USER_ID: A unique identifier for the user session

Import required modules and validate environment

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey,
});

What's happening:

We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio
The dotenv/config import automatically loads environment variables
The MCP client import enables connection to Composio's tool server

Create Tool Router session and initialize MCP client

typescript

async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["lever"],
  });

  const mcpUrl = session.mcp.url;

What's happening:

We're creating a Tool Router session that gives your agent access to Lever tools
The create method takes the user ID and specifies which toolkits should be available
The returned mcp object contains the URL and authentication headers needed to connect to the MCP server
This session provides access to all Lever-related tools through the MCP protocol

Connect to MCP server and retrieve tools

typescript

const mcpClient = await createMCPClient({
  transport: {
    type: "http",
    url: mcpUrl,
    headers: session.mcp.headers, // Authentication headers for the Composio MCP server
  },
});

const tools = await mcpClient.tools();

What's happening:

We're creating an MCP client that connects to our Composio Tool Router session via HTTP
The mcp.url provides the endpoint, and mcp.headers contains authentication credentials
The type: "http" is important - Composio requires HTTP transport
tools() retrieves all available Lever tools that the agent can use

Initialize conversation and CLI interface

typescript

let messages: ModelMessage[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log(
  "Ask any questions related to lever, like summarize my last 5 emails, send an email, etc... :)))\n",
);

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

What's happening:

We initialize an empty messages array to maintain conversation history
A readline interface is created to accept user input from the command line
Instructions are displayed to guide the user on how to interact with the agent

Handle user input and stream responses with real-time tool feedback

typescript

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({ role: "user", content: trimmedInput });
  console.log("\nAgent is thinking...\n");

  try {
    const stream = streamText({
      model: openai("gpt-5"),
      messages,
      tools,
      toolChoice: "auto",
      stopWhen: stepCountIs(10),
      onStepFinish: (step) => {
        for (const toolCall of step.toolCalls) {
          console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

What's happening:

We use streamText instead of generateText to stream responses in real-time
toolChoice: "auto" allows the model to decide when to use Lever tools
stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations
onStepFinish callback displays which tools are being used in real-time
We iterate through the text stream to create a typewriter effect as the agent responds
The complete response is added to conversation history to maintain context
Errors are caught and displayed with helpful retry suggestions

Complete Code

Here's the complete code to get you started with Lever and Vercel AI SDK:

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey,
});

async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["lever"],
  });

  const mcpUrl = session.mcp.url;

  const mcpClient = await createMCPClient({
    transport: {
      type: "http",
      url: mcpUrl,
      headers: session.mcp.headers, // Authentication headers for the Composio MCP server
    },
  });

  const tools = await mcpClient.tools();

  let messages: ModelMessage[] = [];

  console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
  console.log(
    "Ask any questions related to lever, like summarize my last 5 emails, send an email, etc... :)))\n",
  );

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
      console.log("\nGoodbye!");
      rl.close();
      process.exit(0);
    }

    if (!trimmedInput) {
      rl.prompt();
      return;
    }

    messages.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    try {
      const stream = streamText({
        model: openai("gpt-5"),
        messages,
        tools,
        toolChoice: "auto",
        stopWhen: stepCountIs(10),
        onStepFinish: (step) => {
          for (const toolCall of step.toolCalls) {
            console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

Conclusion

You've successfully built a Lever agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback.

Key features of this implementation:

Real-time streaming responses for a better user experience with typewriter effect
Live tool execution feedback showing which tools are being used as the agent works
Dynamic tool loading through Composio's Tool Router with secure authentication
Multi-step tool execution with configurable step limits (up to 10 steps)
Comprehensive error handling for robust agent execution
Conversation history maintenance for context-aware responses

You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

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

Mastra AI

Use Lever MCP with Mastra AI

LlamaIndex

Use Lever MCP with LlamaIndex

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 Vercel AI SDK v6?

Yes, you can. Vercel AI SDK v6 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 Vercel AI SDK v6

Table of Contents

Connect Lever without Auth hassles

Introduction

Also integrate Lever with

TL;DR

What is Vercel AI SDK?

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 and Composio

Install required dependencies

Set up environment variables

Import required modules and validate environment

Create Tool Router session and initialize MCP client

Connect to MCP server and retrieve tools

Initialize conversation and CLI interface

Handle user input and stream responses with real-time tool feedback

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

Mastra AI

LlamaIndex

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 Vercel AI SDK v6?

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