# How to integrate Workable MCP with OpenAI Agents SDK

```json
{
  "title": "How to integrate Workable MCP with OpenAI Agents SDK",
  "toolkit": "Workable",
  "toolkit_slug": "workable",
  "framework": "OpenAI Agents SDK",
  "framework_slug": "open-ai-agents-sdk",
  "url": "https://composio.dev/toolkits/workable/framework/open-ai-agents-sdk",
  "markdown_url": "https://composio.dev/toolkits/workable/framework/open-ai-agents-sdk.md",
  "updated_at": "2026-05-12T10:30:32.564Z"
}
```

## Introduction

This guide walks you through connecting Workable to the OpenAI Agents SDK 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 OpenAI Agents SDK 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

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

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Install the necessary dependencies
- Initialize Composio and create a Tool Router session for Workable
- Configure an AI agent that can use Workable as a tool
- Run a live chat session where you can ask the agent to perform Workable operations

## What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.
Key features include:
- Hosted MCP Tools: Connect to external services through hosted MCP endpoints
- SQLite Sessions: Persist conversation history across interactions
- Simple API: Clean interface with Agent, Runner, and tool configuration
- Streaming Support: Real-time response streaming for interactive applications

## 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

| Tool slug | Name | Description |
|---|---|---|
| `WORKABLE_CREATE_EMPLOYEE` | Create Employee | Tool to create an employee in your Workable account. Use when adding a new hire to employee management system. Employee can be created in draft state (unpublished) or published state (active). Requires w_employees scope. |
| `WORKABLE_DELETE_DEPARTMENT` | Delete Department | Tool to delete a department. Use when removing an obsolete or restructured department after confirming dependent resources. |
| `WORKABLE_DELETE_SUBSCRIPTION` | Delete Subscription | Tool to unsubscribe from an event by deleting a webhook subscription. Use when you need to stop receiving notifications for a specific event. |
| `WORKABLE_GET_ACCOUNT` | Get Account | Tool to return the specified account. Use when you need account metadata by subdomain after listing available accounts. |
| `WORKABLE_GET_ACCOUNTS` | Get Accounts | Retrieves all Workable accounts (organizations) accessible to the authenticated user. Returns account details including ID, name, subdomain, description, summary, and website URL. Use this action to discover which Workable accounts you have access to, or to obtain account identifiers needed for other API operations. Requires 'r_jobs' scope. |
| `WORKABLE_GET_BACKGROUND_CHECK_PACKAGES` | Get Background Check Packages | Tool to retrieve a list of available background check packages from a specified provider. Use after identifying the provider to view available package options. |
| `WORKABLE_GET_BACKGROUND_CHECK_PROVIDERS` | Get Background Check Providers | Retrieves a list of background check providers integrated with your Workable account. Returns provider details including id, name, integration type, connection status, and logo URL. If no providers are configured, returns an empty list. |
| `WORKABLE_GET_CANDIDATES` | Get Candidates | Retrieve a list of candidates across all jobs in the organization. Returns candidate details including name, email, job, stage, and status. Use this to: list all candidates, filter by specific job/stage/email, or find candidates created/updated after a certain date. Supports pagination via the 'limit' parameter (max 100 per page). For complete candidate details, use the individual candidate endpoint. |
| `WORKABLE_GET_EMPLOYEE` | Get Employee | Tool to retrieve detailed information for a specific employee by ID. Use when you need complete employee data including personal details, contact info, employment history, and more. Requires r_employees scope and may need member_id parameter for account-level tokens. |
| `WORKABLE_GET_EVENTS` | Get Events | Retrieve a collection of scheduled events (calls, interviews, meetings) from the Workable account. Supports filtering by event type, date range, candidate, job, or team member. Use pagination parameters (limit, since_id, max_id) for large result sets. By default, cancelled events are excluded unless explicitly included. |
| `WORKABLE_GET_JOBS` | Get Jobs | Retrieves a paginated list of jobs from your Workable account. Returns job details including title, state, department, location, and salary information. Use this to search for jobs by state (draft/published/closed/archived), filter by creation/update dates, or fetch additional fields like descriptions and requirements. |
| `WORKABLE_GET_LEGAL_ENTITIES` | Get Legal Entities | Tool to retrieve a collection of your account legal entities. Use after confirming valid authentication and enabling Employee Management. |
| `WORKABLE_GET_MEMBERS` | Get Members | Retrieve a paginated list of Workable account members with their roles and permissions. This action fetches team members from your Workable account, including admins, standard users, reviewers, and inactive members. You can filter by role, email, name, or status, and paginate through results. Use this to list collaborators, verify member access levels, or find specific team members by email or name. |
| `WORKABLE_GET_RECRUITERS` | Get recruiters | Retrieves external recruiters from your Workable account. Returns all external recruiters by default, or filter by job shortcode to get recruiters collaborating on a specific job. Requires r_jobs scope. |
| `WORKABLE_GET_REQUISITIONS` | Get Requisitions | Tool to retrieve a collection of requisitions in the account. Use after authentication succeeds. |
| `WORKABLE_GET_STAGES` | Get Stages | Tool to retrieve a collection of your recruitment pipeline stages. Use when you need to list all available stages before managing candidates or pipelines. |
| `WORKABLE_GET_SUBSCRIPTIONS` | Get Subscriptions | Retrieves all webhook subscriptions configured in your Workable account. Use this tool to: - List all active webhook subscriptions that receive event notifications - Verify which events your webhooks are listening to - Check the target URLs and filters configured for each subscription - Audit your webhook configuration Requires 'r_candidates' or 'r_employees' scope. No parameters needed. |
| `WORKABLE_LIST_CUSTOM_ATTRIBUTES` | List Custom Attributes | Tool to retrieve all custom attributes configured in the Workable account. Returns attribute configuration including ID, type, enabled status, labels, and hints. Use this action to discover available custom attributes before creating or updating candidates, jobs, or other entities that support custom fields. Requires 'r_jobs' scope. |
| `WORKABLE_LIST_DEPARTMENTS` | List Departments | Tool to retrieve all departments from your Workable account. Use when you need to view the organizational structure or get department identifiers. Requires r_account scope. |
| `WORKABLE_LIST_DISQUALIFICATION_REASONS` | List Disqualification Reasons | Tool to retrieve a collection of account's disqualification reasons. Use when you need to list all available disqualification reasons before disqualifying candidates. |
| `WORKABLE_LIST_EMPLOYEE_FIELDS` | List Employee Fields | Tool to retrieve a collection of your account's employee field definitions. Use when you need to understand available employee data fields before creating or updating employee records. |
| `WORKABLE_LIST_EMPLOYEES` | List Employees | Tool to retrieve a collection of account employees. Use when you need to list, search, or filter employees by name, email, or organizational structure. Supports pagination via limit and offset parameters. Required scope: r_employees. |
| `WORKABLE_LIST_PERMISSION_SETS` | List Permission Sets | Tool to retrieve a collection of your account permission sets. Use when you need to list available permission sets before assigning permissions to members. Requires r_account scope. |
| `WORKABLE_LIST_PUBLIC_JOBS` | List Public Jobs | Tool to return a collection of public jobs for an account. Use when you need to fetch publicly available job listings by subdomain. No authentication required for this endpoint. |
| `WORKABLE_LIST_PUBLIC_LOCATIONS` | List Public Locations | Tool to retrieve a collection of locations where a Workable account has public job postings. Use when you need to discover which geographic locations have available positions for a specific account. No authentication required. |
| `WORKABLE_LIST_TIMEOFF_BALANCES` | List Time Off Balances | Retrieves all time off balances for an employee across all time off categories. Returns detailed balance information including available units, used units, carry-over amounts, and tracking units (days/hours). Use this to check remaining vacation days, sick leave, or other time off allowances for an employee. When using account-level token, employee_id must be provided; employee-level tokens automatically use the authenticated employee's balances. |
| `WORKABLE_LIST_TIMEOFF_CATEGORIES` | List Time Off Categories | Tool to retrieve all time off categories configured for your account. Use when you need to view available time off types before managing employee time off requests. |
| `WORKABLE_LIST_WORK_SCHEDULES` | List Work Schedules | Tool to retrieve a collection of work schedules configured in your Workable account. Use when you need to list all available work schedules, including their weekly hours, work days, and configurations. |
| `WORKABLE_POST_BACKGROUND_CHECK` | Update Background Check Status | Updates the status and results of an existing background check in a candidate's timeline. This tool is designed for background check providers to push status updates (pending, consented, completed, declined, expired) and results back to Workable after initiating a background check. Use this action when: - A candidate has consented to or declined a background check request - Background check results are complete and need to be injected into the candidate's timeline - The status of an ongoing background check has changed - Attaching final reports and structured results to a completed check Prerequisites: Requires a valid background_check_id from an existing background check request that was previously created through Workable's background check provider integration. Note: Uses PUT request to /checks/{background_check_id} endpoint (despite the 'Post' naming). |
| `WORKABLE_POST_DEPARTMENT_MERGE` | Merge Department | Tool to merge a department into another. Use after confirming both department IDs and optional force flag. |
| `WORKABLE_POST_DEPARTMENTS` | Create Department | Tool to create a department in your account. Use when you need to add a new department for organizing teams under your Workable account. |
| `WORKABLE_POST_MEMBER_ENABLE` | Enable Member | Enable (restore) a deactivated Workable account member to active status. This action reactivates a previously deactivated member, restoring their access to the Workable account. The operation is idempotent - enabling an already active member will succeed without error. Requires the 'w_members' scope. Returns HTTP 204 No Content on success. |
| `WORKABLE_POST_MEMBERS_INVITE` | Invite Member | Tool to invite a member to your Workable account. Use when sending an invitation email. |
| `WORKABLE_PUT_DEPARTMENTS` | Update Department | Tool to update an existing department in your account. Use when renaming a department or changing its parent after confirming its ID. |
| `WORKABLE_PUT_MEMBERS` | Update Member | Updates a Workable account member's details including roles, name, headline, email, and collaboration rules. Requires member ID and roles array. Use this to modify existing member information such as changing permissions, updating contact details, or adjusting collaboration settings. |
| `WORKABLE_UPDATE_EMPLOYEE` | Update Employee | Tool to update an existing employee in Workable. Use when you need to modify employee details such as job title, contact information, department, or other employee attributes. Requires employee ID and member ID. |
| `WORKABLE_UPLOAD_EMPLOYEE_DOCUMENTS` | Upload Employee Documents | Tool to upload a list of documents for a specific employee. Use when you need to attach documents (contracts, forms, etc.) to an employee's record. Required scope: w_employees. |

## Supported Triggers

None listed.

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

The Workable MCP server is an implementation of the Model Context Protocol that connects your AI agent to Workable. It provides structured and secure access so your agent can perform Workable 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:
- Composio API Key and OpenAI API Key
- Primary know-how of OpenAI Agents SDK
- A live Workable project
- Some knowledge of Python or 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'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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings and copy your API key.

### 2. Install dependencies

Install the Composio SDK and the OpenAI Agents SDK.
```python
pip install composio_openai_agents openai-agents python-dotenv
```

```typescript
npm install @composio/openai-agents @openai/agents dotenv
```

### 3. Set up environment variables

Create a .env file and add your OpenAI and Composio API keys.
```bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com
```

### 4. Import dependencies

What's happening:
- You're importing all necessary libraries.
- The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Workable.
```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
```

### 5. Set up the Composio instance

No description provided.
```python
load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
```

```typescript
dotenv.config();

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

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
```

### 6. Create a Tool Router session

What is happening:
- You give the Tool Router the user id and the toolkits you want available. Here, it is only workable.
- The router checks the user's Workable connection and prepares the MCP endpoint.
- The returned session.mcp.url is the MCP URL that your agent will use to access Workable.
- This approach keeps things lightweight and lets the agent request Workable tools only when needed during the conversation.
```python
# Create a Workable Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["workable"]
)

mcp_url = session.mcp.url
```

```typescript
// Create Tool Router session for Workable
const session = await composio.create(userId as string, {
  toolkits: ['workable'],
});
const mcpUrl = session.mcp.url;
```

### 7. Configure the agent

No description provided.
```python
# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Workable. "
        "Help users perform Workable operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
```

```typescript
// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Workable. Help users perform Workable operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
```

### 8. Start chat loop and handle conversation

No description provided.
```python
print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

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

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

rl.on('line', async (userInput) => {
  const text = userInput.trim();

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

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

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

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

## Complete Code

```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["workable"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Workable. "
        "Help users perform Workable operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

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

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['workable'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Workable. Help users perform Workable operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

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

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

  rl.on('line', async (userInput) => {
    const text = userInput.trim();

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

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

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\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

This was a starter code for integrating Workable MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Workable.
Key features:
- Hosted MCP tool integration through Composio's Tool Router
- SQLite session persistence for conversation history
- Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

## How to build Workable MCP Agent with another framework

- [Claude Agent SDK](https://composio.dev/toolkits/workable/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/workable/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/workable/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/workable/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/workable/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/workable/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/workable/framework/cli)
- [Google ADK](https://composio.dev/toolkits/workable/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/workable/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/workable/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/workable/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/workable/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/workable/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.
- [Recruitee](https://composio.dev/toolkits/recruitee) - Recruitee is collaborative hiring software that centralizes recruitment tasks for teams. It streamlines sourcing, interviewing, and hiring so you can fill roles faster.
- [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.
- [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 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 OpenAI Agents SDK?

Yes, you can. OpenAI Agents SDK 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.

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