How to integrate Workable MCP with Mastra AI

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Workable logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Workable to Mastra AI using the Composio tool router. By the end, you'll have a working Workable agent that can list all candidates for open roles, show scheduled interviews for this week, fetch all current job postings through natural language commands.

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

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

Also integrate Workable with

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 Workable tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Workable 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 Workable 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 Workable MCP server, and what's possible with it?

The Workable MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Workable account. It provides structured and secure access to your hiring and HR data, so your agent can perform actions like listing jobs, managing candidates, retrieving background check info, and organizing departments on your behalf.

  • Comprehensive candidate management: Instantly retrieve and aggregate candidate data across all jobs, making it easy for your agent to analyze talent pipelines, track applicants, and surface top candidates.
  • Job and account insights: Let your agent list all open roles, access job details, and pull account-wide information to keep your hiring team up-to-date and organized.
  • Automated event and interview scheduling: Fetch all scheduled events, interviews, and meetings so your agent can help coordinate calendars and ensure everyone’s on the same page.
  • Background check integration: Retrieve available background check providers and packages, enabling your agent to streamline compliance and onboarding workflows.
  • Team and department organization: List or delete departments, fetch member rosters, and manage legal entities—helping your agent automate org chart updates and keep your HR records tidy.

Supported Tools & Triggers

Tools
Create EmployeeTool to create an employee in your Workable account.
Delete DepartmentTool to delete a department.
Delete SubscriptionTool to unsubscribe from an event by deleting a webhook subscription.
Get AccountTool to return the specified account.
Get AccountsRetrieves all Workable accounts (organizations) accessible to the authenticated user.
Get Background Check PackagesTool to retrieve a list of available background check packages from a specified provider.
Get Background Check ProvidersRetrieves a list of background check providers integrated with your Workable account.
Get CandidatesRetrieve a list of candidates across all jobs in the organization.
Get EmployeeTool to retrieve detailed information for a specific employee by ID.
Get EventsRetrieve a collection of scheduled events (calls, interviews, meetings) from the Workable account.
Get JobsRetrieves a paginated list of jobs from your Workable account.
Get Legal EntitiesTool to retrieve a collection of your account legal entities.
Get MembersRetrieve a paginated list of Workable account members with their roles and permissions.
Get recruitersRetrieves external recruiters from your Workable account.
Get RequisitionsTool to retrieve a collection of requisitions in the account.
Get StagesTool to retrieve a collection of your recruitment pipeline stages.
Get SubscriptionsRetrieves all webhook subscriptions configured in your Workable account.
List Custom AttributesTool to retrieve all custom attributes configured in the Workable account.
List DepartmentsTool to retrieve all departments from your Workable account.
List Disqualification ReasonsTool to retrieve a collection of account's disqualification reasons.
List Employee FieldsTool to retrieve a collection of your account's employee field definitions.
List EmployeesTool to retrieve a collection of account employees.
List Permission SetsTool to retrieve a collection of your account permission sets.
List Public JobsTool to return a collection of public jobs for an account.
List Public LocationsTool to retrieve a collection of locations where a Workable account has public job postings.
List Time Off BalancesRetrieves all time off balances for an employee across all time off categories.
List Time Off CategoriesTool to retrieve all time off categories configured for your account.
List Work SchedulesTool to retrieve a collection of work schedules configured in your Workable account.
Update Background Check StatusUpdates the status and results of an existing background check in a candidate's timeline.
Merge DepartmentTool to merge a department into another.
Create DepartmentTool to create a department in your account.
Enable MemberEnable (restore) a deactivated Workable account member to active status.
Invite MemberTool to invite a member to your Workable account.
Update DepartmentTool to update an existing department in your account.
Update MemberUpdates a Workable account member's details including roles, name, headline, email, and collaboration rules.
Update EmployeeTool to update an existing employee in Workable.
Upload Employee DocumentsTool to upload a list of documents for a specific employee.

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:

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

Step-by-step Guide

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

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Workable through MCP.

Install dependencies

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

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

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

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

Import libraries and validate environment

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,
});
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

Create a Tool Router session for Workable

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

  const composioMCPUrl = session.mcp.url;
  console.log("Workable MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "workable" for Workable access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

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);
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 Workable toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "workable-mastra-agent",
    instructions: "You are an AI agent with Workable tools via Composio.",
    model: "openai/gpt-5",
  });
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

Set up interactive chat interface

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: {
        workable: 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);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Workable 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

Complete Code

Here's the complete code to get you started with Workable and Mastra AI:

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: ["workable"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "workable-mastra-agent",
    instructions: "You are an AI agent with Workable 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: { workable: 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 Workable 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 Workable MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Workable MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Workable MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Workable MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Workable MCP with Claude Cowork

Codex logo

Codex

Use Workable MCP with Codex

OpenClaw logo

OpenClaw

Use Workable MCP with OpenClaw

Hermes logo

Hermes

Use Workable MCP with Hermes

CLI logo

CLI

Use Workable MCP with CLI

Google ADK logo

Google ADK

Use Workable MCP with Google ADK

LangChain logo

LangChain

Use Workable MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Workable MCP with Vercel AI SDK

LlamaIndex logo

LlamaIndex

Use Workable MCP with LlamaIndex

CrewAI logo

CrewAI

Use Workable MCP with CrewAI

FAQ

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

With a standalone Workable MCP server, the agents and LLMs can only access a fixed set of Workable tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Workable 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 Workable tools.

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

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

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 freeGet a demo↗