How to integrate Workable MCP with LangChain

This guide walks you through connecting Workable to LangChain 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 LangChain 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.

Get started for free Get a demo

Workable

Oauth2Api Key

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.

37 Tools

Managed auth

Connect Workable without auth hassles

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

Try for free

Introduction

This guide will help you understand how to give your LangChain 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

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

TL;DR

Here's what you'll learn:

Get and set up your OpenAI and Composio API keys
Connect your Workable project to Composio
Create a Tool Router MCP session for Workable
Initialize an MCP client and retrieve Workable tools
Build a LangChain agent that can interact with Workable
Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

Agent Framework: Build agents that can use tools and make decisions
MCP Integration: Connect to external services through Model Context Protocol adapters
Memory Management: Maintain conversation history across interactions
Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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.

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

Step by step10 STEPS

Prerequisites

Before starting this tutorial, make sure you have:

Python 3.10 or higher installed on your system
A Composio account with an API key
An OpenAI API key
Basic familiarity with Python and async programming

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 dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

@composio/langchain provides Composio integration for LangChain
@langchain/mcp-adapters enables MCP client connections
@langchain/core is the core agent framework
dotenv/config loads environment variables

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_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's API
COMPOSIO_USER_ID identifies the user for session management
OPENAI_API_KEY enables access to OpenAI's language models

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();

What's happening:

We're importing LangChain's MCP adapter and Composio SDK
The dotenv/config import loads environment variables from your .env file
This setup prepares the foundation for connecting LangChain with Workable functionality through MCP

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

What's happening:

We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
Creating a Composio instance that will manage our connection to Workable tools
Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['workable']
    }
);

const url = session.mcp.url;

What's happening:

We're creating a Tool Router session that gives your agent access to Workable tools
The create method takes the user ID and specifies which toolkits should be available
The returned session.mcp.url is the MCP server URL that your agent will use
This approach allows the agent to dynamically load and use Workable tools as needed

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "workable-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });

What's happening:

We're creating a MultiServerMCPClient that connects to our Workable MCP server via HTTP
The client is configured with a name and the URL from our Tool Router session
getTools() retrieves all available Workable tools that the agent can use
We're creating a LangChain agent using the GPT-5 model

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Workable related question or task to the agent.\n");

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

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

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

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

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

What's happening:

We initialize an empty conversationHistory list to maintain context across interactions
A readline interface is used to continuously accept user input from the command line
When a user types a message, it's added to the conversation history and sent to the agent
The agent processes the request using the invoke() method with the full conversation history
Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully

Run the application

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

What's happening:

We call the main() function to start the application

Complete Code

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

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['workable']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "workable-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Workable related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    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;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

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

Conclusion

You've successfully built a LangChain agent that can interact with Workable through Composio's Tool Router.

Key features of this implementation:

Dynamic tool loading through Composio's Tool Router
Conversation history maintenance for context-aware responses
Async Python provides clean, efficient execution of agent workflows

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

TOOLS

Supported Tools

Every Workable action and event your agent gets out of the box.

Create Employee

Tool to create an employee in your Workable account.

Delete Department

Tool to delete a department.

Delete Subscription

Tool to unsubscribe from an event by deleting a webhook subscription.

Get Account

Tool to return the specified account.

Get Accounts

Retrieves all Workable accounts (organizations) accessible to the authenticated user.

Get Background Check Packages

Tool to retrieve a list of available background check packages from a specified provider.

Get Background Check Providers

Retrieves a list of background check providers integrated with your Workable account.

Get Candidates

Retrieve a list of candidates across all jobs in the organization.

Get Employee

Tool to retrieve detailed information for a specific employee by ID.

Get Events

Retrieve a collection of scheduled events (calls, interviews, meetings) from the Workable account.

Get Jobs

Retrieves a paginated list of jobs from your Workable account.

Get Legal Entities

Tool to retrieve a collection of your account legal entities.

Get Members

Retrieve a paginated list of Workable account members with their roles and permissions.

Get recruiters

Retrieves external recruiters from your Workable account.

Get Requisitions

Tool to retrieve a collection of requisitions in the account.

Get Stages

Tool to retrieve a collection of your recruitment pipeline stages.

Get Subscriptions

Retrieves all webhook subscriptions configured in your Workable account.

List Custom Attributes

Tool to retrieve all custom attributes configured in the Workable account.

List Departments

Tool to retrieve all departments from your Workable account.

List Disqualification Reasons

Tool to retrieve a collection of account's disqualification reasons.

List Employee Fields

Tool to retrieve a collection of your account's employee field definitions.

List Employees

Tool to retrieve a collection of account employees.

List Permission Sets

Tool to retrieve a collection of your account permission sets.

List Public Jobs

Tool to return a collection of public jobs for an account.

List Public Locations

Tool to retrieve a collection of locations where a Workable account has public job postings.

List Time Off Balances

Retrieves all time off balances for an employee across all time off categories.

List Time Off Categories

Tool to retrieve all time off categories configured for your account.

List Work Schedules

Tool to retrieve a collection of work schedules configured in your Workable account.

Update Background Check Status

Updates the status and results of an existing background check in a candidate's timeline.

Merge Department

Tool to merge a department into another.

Create Department

Tool to create a department in your account.

Enable Member

Enable (restore) a deactivated Workable account member to active status.

Invite Member

Tool to invite a member to your Workable account.

Update Department

Tool to update an existing department in your account.

Update Member

Updates a Workable account member's details including roles, name, headline, email, and collaboration rules.

Update Employee

Tool to update an existing employee in Workable.

Upload Employee Documents

Tool to upload a list of documents for a specific employee.

FRAMEWORKS

How to build Workable MCP Agent with another framework

OpenAI Agents SDK

Use Workable MCP with OpenAI Agents SDK

Claude Agent SDK

Use Workable MCP with Claude Agent SDK

Claude Code

Use Workable MCP with Claude Code

Claude Cowork

Use Workable MCP with Claude Cowork

Codex

Use Workable MCP with Codex

OpenClaw

Use Workable MCP with OpenClaw

Hermes

Use Workable MCP with Hermes

CLI

Use Workable MCP with CLI

Google ADK

Use Workable MCP with Google ADK

Vercel AI SDK

Use Workable MCP with Vercel AI SDK

Mastra AI

Use Workable MCP with Mastra AI

LlamaIndex

Use Workable MCP with LlamaIndex

CrewAI

Use Workable MCP with CrewAI

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

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.

Breathe HR

Api Key

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.

FAQ

Frequently asked questions

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.

Yes, you can. LangChain 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.

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.

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.

Start with Workable.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Workable tool your agent needs.Free to start.

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

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

Harsha Gaddipati

Co-founder, Slashy

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's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

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

Nirman Dave

CEO, Zams

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

Ryan Yu

Founder, Extra Thursday

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

Tomisin Jenrola

Founder & CEO, SwarmZero

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.

Jerome Leclanche

Co-Founder, Ingram Technologies

How to integrate Workable MCP with LangChain

Connect Workable without auth hassles

Introduction

Also integrate Workable with

TL;DR

What is LangChain?

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

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 dependencies

Set up environment variables

Import dependencies

Initialize Composio client

Create a Tool Router session

Configure the agent with the MCP URL

Set up interactive chat interface

Run the application

Complete Code

Conclusion

Supported Tools

How to build Workable MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Explore Other Toolkits

Ashby

Async interview

Bamboohr

Breathe HR

Frequently asked questions

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

Can I use Tool Router MCP with LangChain?+

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

How safe is my data with Composio Tool Router?+

Start with Workable.It takes 30 seconds.

Teams ship real agents on Composio