How to integrate Workday MCP with OpenAI Agents SDK

Framework Integration Gradient
Workday Logo
open-ai-agents-sdk Logo
divider

Introduction

This guide walks you through connecting Workday to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Workday agent that can request vacation days for next week, check my current absence balance, find all open job postings i manage, summarize feedback from recent interviews through natural language commands.

This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Workday account through Composio's Workday MCP server.

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

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 Workday
  • Configure an AI agent that can use Workday as a tool
  • Run a live chat session where you can ask the agent to perform Workday operations

What is open-ai-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 Workday MCP server, and what's possible with it?

The Workday MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Workday account. It provides structured and secure access to your HR, payroll, and recruiting data, so your agent can perform actions like managing time off, retrieving employee details, tracking job postings, and analyzing interview feedback on your behalf.

  • Automated time off management: Easily create new time off requests or check absence balances for yourself or others, making leave management effortless.
  • Employee data and profile retrieval: Have your agent fetch profile details for the current user or any specified worker to simplify onboarding and HR processes.
  • Comprehensive job posting insights: Instantly retrieve information about job postings, including descriptions and screening questionnaires, to aid recruiters and hiring managers.
  • Interview feedback analysis: Let your agent pull and summarize interview feedback entries to streamline debriefs and improve hiring decisions.
  • Access to holiday and leave events: Quickly get holiday schedules and leave status values for better workforce planning and scheduling.

Supported Tools & Triggers

Tools
Create Time Off RequestCreates a time off request for the specified worker id and initiates the business process.
Get Absence BalanceRetrieves the specified balance of all absence plan and leave of absence types.
Get Balance DetailsRetrieves the specified balance of all absence plan and leave of absence types.
Get Current UserRetrieves the current authenticated worker's profile information from workday.
Get Holiday EventsReturns the holiday events for the specified workers and time period.
Get Interview FeedbackRetrieves feedback entries for a specific interview to prepare debrief notes with highlights and lowlights.
Get Job PostingRetrieves detailed information about a specific job posting including job description.
Get Job Posting QuestionnaireRetrieves screening questions and questionnaires associated with a specific job posting.
Get Leave Status ValuesRetrieves instances that can be used as values for other endpoint parameters in this service.
Get My Job PostingsFinds all job postings assigned to a specific recruiter by analyzing interviews and job requisitions.
Get ProspectRetrieves a single prospect instance for talent matching and best-fit analysis.
Get Prospect EducationsRetrieves the education of a prospect for talent matching and best-fit analysis.
Get Prospect ExperiencesRetrieves the work experience of a prospect for talent matching and best-fit analysis.
Get Prospect Resume AttachmentsRetrieves resume attachments for a specific prospect to help prepare for upcoming interviews.
Get Prospect SkillsRetrieves the skills of a prospect for talent matching and best-fit analysis.
Get Time Off Status ValuesRetrieves instances that can be used as values for other endpoint parameters in this service.
Get Worker Eligible Absence TypesRetrieves a collection of eligible absence types for the specified worker.
Get Worker Leaves of AbsenceRetrieves the leaves of absence for the specified worker using the working absencemanagement v1 api.
Get Worker Time Off DetailsRetrieves a collection of time off details for the specified worker.
Get Worker Valid Time Off DatesRetrieves the valid time off dates for the specified worker id for the given dates.
List Absence BalancesRetrieves the balance of all absence plan and leave of absence type for the specified worker id.
List BalancesRetrieves the balance of all absence plan and leave of absence type for the specified worker id.
List InterviewsRetrieves a list of interviews with job requisition and recruiter assignment details.
List Job PostingsRetrieves a list of job postings from workday recruiting system with filtering options.
List WorkersRetrieves a collection of workers and current staffing information.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router 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 Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router 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:
  • Composio API Key and OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Workday project
  • Some knowledge of Python or Typescript

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

Install dependencies

pip install composio_openai_agents openai-agents python-dotenv

Install the Composio SDK and the OpenAI Agents SDK.

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

Import dependencies

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
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 Workday.

Set up the Composio instance

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())
What's happening:
  • load_dotenv() loads your .env file so OPENAI_API_KEY and COMPOSIO_API_KEY are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.

Create a Tool Router session

# Create a Workday Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["workday"]
)

mcp_url = session.mcp.url

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only workday.
  • The router checks the user's Workday connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Workday.
  • This approach keeps things lightweight and lets the agent request Workday tools only when needed during the conversation.

Configure the agent

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Workday. "
        "Help users perform Workday 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",
            }
        )
    ],
)
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Workday and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a HostedMCPTool that connects to the MCP server URL we created earlier.
  • The headers dict includes the Composio API key for secure authentication with the MCP server.
  • require_approval: 'never' means the agent can execute Workday operations without asking for permission each time, making interactions smoother.

Start chat loop and handle conversation

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())
What's happening:
  • The program prints a session URL that you visit to authorize Workday.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using Runner.run().
  • The responses are printed to the console, and conversations are saved locally using SQLite.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Workday and open-ai-agents-sdk:

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=["workday"]
)
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 Workday. "
        "Help users perform Workday 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())

Conclusion

This was a starter code for integrating Workday MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Workday.

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 Workday MCP Agent with another framework

FAQ

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

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

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

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

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
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.