# How to integrate Recruitee MCP with Mastra AI

```json
{
  "title": "How to integrate Recruitee MCP with Mastra AI",
  "toolkit": "Recruitee",
  "toolkit_slug": "recruitee",
  "framework": "Mastra AI",
  "framework_slug": "mastra-ai",
  "url": "https://composio.dev/toolkits/recruitee/framework/mastra-ai",
  "markdown_url": "https://composio.dev/toolkits/recruitee/framework/mastra-ai.md",
  "updated_at": "2026-05-12T10:23:33.477Z"
}
```

## Introduction

This guide walks you through connecting Recruitee to Mastra AI using the Composio tool router. By the end, you'll have a working Recruitee agent that can add a new candidate named alex lee, list all currently published job offers, get detailed profile for candidate emily chen through natural language commands.
This guide will help you understand how to give your Mastra AI agent real control over a Recruitee account through Composio's Recruitee MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Recruitee with

- [OpenAI Agents SDK](https://composio.dev/toolkits/recruitee/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/recruitee/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/recruitee/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/recruitee/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/recruitee/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/recruitee/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/recruitee/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/recruitee/framework/cli)
- [Google ADK](https://composio.dev/toolkits/recruitee/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/recruitee/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/recruitee/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/recruitee/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/recruitee/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Set up your environment so Mastra, OpenAI, and Composio work together
- Create a Tool Router session in Composio that exposes Recruitee tools
- Connect Mastra's MCP client to the Composio generated MCP URL
- Fetch Recruitee tool definitions and attach them as a toolset
- Build a Mastra agent that can reason, call tools, and return structured results
- Run an interactive CLI where you can chat with your Recruitee agent

## What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.
Key features include:
- MCP Client: Built-in support for Model Context Protocol servers
- Toolsets: Organize tools into logical groups
- Step Callbacks: Monitor and debug agent execution
- OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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

The Recruitee MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Recruitee account. It provides structured and secure access to your recruitment workflow, so your agent can perform actions like managing candidates, creating notes, publishing job offers, retrieving company info, and handling tags on your behalf.
- Automated candidate management: Quickly create new candidate profiles, retrieve detailed information, or delete candidates as your hiring process evolves.
- Collaborative note-taking: Let your agent add notes to candidate profiles, ensuring every piece of feedback or interview insight is captured and accessible.
- Job offer publishing and retrieval: Effortlessly generate new job offers or fetch details on published positions from your public careers site.
- Company and job listing access: Instantly get your company ID, list all candidates, or pull a list of current published job offers for reporting and coordination.
- Tag and label management: Enable your agent to delete outdated tags, keeping your recruitment database organized and relevant.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `RECRUITEE_CREATE_CANDIDATE` | Create Candidate | Tool to create a new candidate profile. Use after gathering all candidate details. Example: "Create a new candidate named Jane Doe with email jane.doe@example.com." |
| `RECRUITEE_CREATE_NOTE` | Create Note | Creates a new note for a candidate in Recruitee. Notes can be used to record interview feedback, assessments, or any observations about the candidate. Use this when you need to add commentary or documentation to a candidate's profile. |
| `RECRUITEE_CREATE_OFFER` | Create Offer | Creates a new job offer or talent pool in Recruitee. Required fields include title, location IDs, and description. Use Get Locations action to retrieve valid location IDs before creating an offer. The offer status can be set to draft, internal, published, closed, or archived. |
| `RECRUITEE_DELETE_CANDIDATE` | Delete Candidate | Tool to delete a candidate profile. Use when you need to permanently remove a candidate from your Recruitee account. Returns no content on success. |
| `RECRUITEE_DELETE_TAG` | Delete Tag | Permanently deletes a tag from Recruitee by its ID. This action requires appropriate API permissions to delete tags. Use this when you need to remove unused or obsolete tags. Note: Deleting a tag removes it from all associated candidates and offers. |
| `RECRUITEE_GET_CANDIDATE` | Get Candidate | Tool to retrieve detailed information about a specific candidate. Use when you need the candidate's full profile before proceeding. |
| `RECRUITEE_GET_CANDIDATES` | Get Candidates | Tool to retrieve a list of all candidates in the company. Use when you need to fetch or filter candidates before proceeding. |
| `RECRUITEE_GET_COMPANY_ID` | Get Company ID | Tool to retrieve the company ID of the authenticated account. Use when you need to confirm your company identity before other operations. |
| `RECRUITEE_GET_COMPANY_OFFER_PUBLIC` | Get Company Offer Public | Tool to retrieve a specific published job offer by ID or slug from the public Careers Site API. Use after you have the offer identifier. |
| `RECRUITEE_GET_DEPARTMENTS` | Get Departments | Tool to retrieve a list of company departments. Use when you need to reference or assign offers or candidates to departments. |
| `RECRUITEE_GET_LOCATIONS` | Get Locations | Tool to retrieve a list of company locations. Use when you need to see all location options before assigning them to offers. |
| `RECRUITEE_GET_NOTES` | Get Notes | Tool to retrieve a list of notes for a specific candidate. Use after confirming the candidate exists when you need to review their notes. |
| `RECRUITEE_GET_OFFERS` | Get Offers | Tool to retrieve a list of all job offers. Use after authentication to browse or paginate your company's complete set of offers. |
| `RECRUITEE_GET_PIPELINE_STAGES` | Get Pipeline Stages | Tool to retrieve pipeline stages of a job offer. Use when you have the offer ID and need its stages to track candidate progression. Example: "Get pipeline stages for offer ID 456." |
| `RECRUITEE_GET_TAGS` | Get Tags | Retrieve all tags with optional filtering and pagination. Search by name, sort by name or usage count, and paginate through results. |
| `RECRUITEE_LIST_EEO_JOB_CATEGORIES` | List EEO Job Categories | Tool to retrieve available EEO (Equal Employment Opportunity) job categories. Use when you need to see standard EEO job classification options. |
| `RECRUITEE_LIST_INVOICES` | List Invoices | Tool to list invoices for a company. Use to retrieve billing invoice records. |
| `RECRUITEE_LIST_LOCALIZATION_SETTINGS` | List Localization Settings | Tool to retrieve localization settings including proposed time format and start day of the week. Use when you need to check regional or time display preferences. |
| `RECRUITEE_LIST_SHARE_COUNTRIES` | List Share Countries | Tool to retrieve all countries with region codes and phone codes per locale. Use when you need comprehensive country reference data including internationalization details. |
| `RECRUITEE_LIST_SHARE_EEO_ANSWERS` | List Share EEO Answers | Tool to retrieve available EEO (Equal Employment Opportunity) answers. Use when you need to see available answer options for EEO compliance questions. |
| `RECRUITEE_UPDATE_CANDIDATE` | Update Candidate | Updates an existing candidate's information in Recruitee. Use this to modify candidate details such as name, contact info, cover letter, tags, and social links. All fields except candidate_id are optional - only provide the fields you want to update. The API performs a partial update (PATCH), preserving any fields you don't specify. |
| `RECRUITEE_UPDATE_NOTE` | Update Note | Tool to update an existing note for a candidate. Use when you need to modify note text or pin status after creation. |
| `RECRUITEE_UPDATE_OFFER` | Update Offer | Updates an existing job offer or talent pool in Recruitee. Allows modification of offer details including title, description, requirements, status, locations, department assignment, work type (remote/hybrid/on-site), visibility settings, and application form field requirements. Only specified fields are updated; omitted fields remain unchanged. Requires the offer ID - use Get Offers or Get Offer actions to retrieve existing offer IDs. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Recruitee MCP server is an implementation of the Model Context Protocol that connects your AI agent to Recruitee. It provides structured and secure access so your agent can perform Recruitee operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Node.js 18 or higher
- A Composio account with an active API key
- An OpenAI API key
- Basic familiarity with TypeScript

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key.
- You need credits or a connected billing setup to use the models.
- Store the key somewhere safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings and copy your API key.
- This key lets your Mastra agent talk to Composio and reach Recruitee through MCP.

### 2. Install dependencies

Install the required packages.
What's happening:
- @composio/core is the Composio SDK for creating MCP sessions
- @mastra/core provides the Agent class
- @mastra/mcp is Mastra's MCP client
- @ai-sdk/openai is the model wrapper for OpenAI
- dotenv loads environment variables from .env
```bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates your requests to Composio
- COMPOSIO_USER_ID tells Composio which user this session belongs to
- OPENAI_API_KEY lets the Mastra agent call OpenAI models
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import libraries and validate environment

What's happening:
- dotenv/config auto loads your .env so process.env.* is available
- openai gives you a Mastra compatible model wrapper
- Agent is the Mastra agent that will call tools and produce answers
- MCPClient connects Mastra to your Composio MCP server
- Composio is used to create a Tool Router session
```typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

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

if (!openaiAPIKey) 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 as string,
});
```

### 5. Create a Tool Router session for Recruitee

What's happening:
- create spins up a short-lived MCP HTTP endpoint for this user
- The toolkits array contains "recruitee" for Recruitee access
- session.mcp.url is the MCP URL that Mastra's MCPClient will connect to
```typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["recruitee"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Recruitee MCP URL:", composioMCPUrl);
```

### 6. Configure Mastra MCP client and fetch tools

What's happening:
- MCPClient takes an id for this client and a list of MCP servers
- The headers property includes the x-api-key for authentication
- getTools fetches the tool definitions exposed by the Recruitee toolkit
```typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
```

### 7. Create the Mastra agent

What's happening:
- Agent is the core Mastra agent
- name is just an identifier for logging and debugging
- instructions guide the agent to use tools instead of only answering in natural language
- model uses openai("gpt-5") to configure the underlying LLM
```typescript
const agent = new Agent({
    name: "recruitee-mastra-agent",
    instructions: "You are an AI agent with Recruitee tools via Composio.",
    model: "openai/gpt-5",
  });
```

### 8. Set up interactive chat interface

What's happening:
- messages keeps the full conversation history in Mastra's expected format
- agent.generate runs the agent with conversation history and Recruitee toolsets
- maxSteps limits how many tool calls the agent can take in a single run
- onStepFinish is a hook that prints intermediate steps for debugging
```typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\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({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        recruitee: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

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

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

## Complete Code

```typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

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

if (!openaiAPIKey) 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 as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["recruitee"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      recruitee: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "recruitee-mastra-agent",
    instructions: "You are an AI agent with Recruitee tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

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

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { recruitee: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();
```

## Conclusion

You've built a Mastra AI agent that can interact with Recruitee through Composio's Tool Router.
You can extend this further by:
- Adding other toolkits like Gmail, Slack, or GitHub
- Building a web-based chat interface around this agent
- Using multiple MCP endpoints to enable cross-app workflows

## How to build Recruitee MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/recruitee/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/recruitee/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/recruitee/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/recruitee/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/recruitee/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/recruitee/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/recruitee/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/recruitee/framework/cli)
- [Google ADK](https://composio.dev/toolkits/recruitee/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/recruitee/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/recruitee/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/recruitee/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/recruitee/framework/crew-ai)

## Related Toolkits

- [Ashby](https://composio.dev/toolkits/ashby) - Ashby is an applicant tracking system that handles job postings, candidate management, and hiring analytics.
- [Async interview](https://composio.dev/toolkits/async_interview) - Async interview is an on-demand video interview platform for streamlined hiring. Candidates record responses on their schedule, so employers can review anytime.
- [Bamboohr](https://composio.dev/toolkits/bamboohr) - 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.
- [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date.
- [Connecteam](https://composio.dev/toolkits/connecteam) - Connecteam is a workforce management platform for deskless teams, streamlining operations, HR, and team communication. It helps businesses save time by automating scheduling, time tracking, and staff engagement tasks.
- [Lever](https://composio.dev/toolkits/lever) - Lever is an applicant tracking system that blends sourcing, CRM, and analytics for recruiting. It helps companies scale hiring with collaborative workflows and actionable insights.
- [Remote retrieval](https://composio.dev/toolkits/remote_retrieval) - Remote retrieval is a logistics automation tool for managing laptop and monitor returns. It streamlines return tracking, saving time and hassle for IT and ops teams.
- [Sap successfactors](https://composio.dev/toolkits/sap_successfactors) - Sap successfactors is a cloud-based human capital management suite for HR, payroll, recruiting, and talent management. It helps organizations centralize employee data and streamline the entire employee lifecycle.
- [Talenthr](https://composio.dev/toolkits/talenthr) - TalentHR is an intuitive, all-in-one HR tool for managing employee records, leave, and HR workflows. It streamlines HR operations so businesses can focus on people, not paperwork.
- [Workable](https://composio.dev/toolkits/workable) - Workable is an all-in-one HR software platform that streamlines hiring, employee management, and payroll. It helps teams simplify recruiting, onboarding, and staff operations in one place.
- [Workday](https://composio.dev/toolkits/workday) - Workday is a cloud-based ERP platform for HR, finance, and workforce analytics. It streamlines employee management, payroll, and business operations in a single system.
- [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.
- [Google Calendar](https://composio.dev/toolkits/googlecalendar) - Google Calendar is a time management service for scheduling meetings, events, and reminders. It streamlines personal and team organization with integrated notifications and sharing options.
- [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.
- [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management.
- [Twitter](https://composio.dev/toolkits/twitter) - Twitter is a social media platform for sharing real-time updates, conversations, and news. Stay connected, informed, and engaged with communities worldwide.
- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Composio](https://composio.dev/toolkits/composio) - Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Recruitee MCP?

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

### Can I use Tool Router MCP with Mastra AI?

Yes, you can. Mastra AI 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 Recruitee tools.

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

Yes, absolutely. You can configure which Recruitee 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 Recruitee data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
