Skip to main content

Announcing StackOne Defender: leading open-source prompt injection guard for your agent Read More

Planday MCP Server
for AI Agents

Production-ready Planday MCP server with 69 extensible actions — plus built-in authentication, security, and optimized execution.

Planday logo
Planday MCP Server
Built by StackOne StackOne

Coverage

69 Agent Actions

Create, read, update, and delete across Planday — and extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your Planday MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every Planday tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Planday call.

Tools Discovery →

What is the Planday MCP Server?

A Planday MCP server lets AI agents read and write Planday data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's Planday MCP server ships with 69 pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, and optimized agent context. Connect it from MCP clients like Claude Desktop, Cursor, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All Planday MCP Tools and Actions

Every action from Planday's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.

Employees

  • Create Employee

    Create a new employee account based on provided parameters

  • Update Employee

    Update an existing employee's information

Absence Adjustments

  • Create Absence Adjustment

    Create an adjustment to change a balance of an accrued absence account

  • List Absence Adjustments

    Returns adjustments of a specific accrued absence account

Account Types

  • List Account Types

    Get all available account types filtered by id, absence type and deleted state

  • Delete Account Type

    Remove account type

Accrued Account Types

  • Create Accrued Account Type

    Create new account type definition of absence type Accrued

  • Get Accrued Account Type

    Get account types with absence type - Accrued

  • Update Accrued Account Type

    Update account type definition of absence type Accrued

Departments

  • Create Department

    Create a new department

  • List Departments

    Get a list of departments

  • Update Department

    Update details of a department

  • Delete Department

    Delete a department

Employee Groups

  • Create Employee Group

    Create a new employee group

  • List Employee Groups

    Get a list of employee groups

  • Update Employee Group

    Update details of an employee group

  • Delete Employee Group

    Delete an employee group

Skills

  • Create Skill

    Create a new skill on the portal

  • List Skills

    Get a list of skills on the portal

  • Update Skill

    Update the name, description and time limited status of a skill

  • Delete Skill

    Delete a skill by providing the skill id

Shifts

  • Create Shift

    Create a shift

  • Update Shift

    Update a shift

  • Delete Shift

    Delete an existing shift

Shift Types

  • Create Shift Type

    Create a new shift type

  • List Shift Types

    Returns paginated list of available shift types

  • Update Shift Type

    Update an existing shift type

Positions

  • Create Position

    Create a position

  • Update Position

    Update a position

  • Delete Position

    Delete position by provided id

Other (39)

  • Create Or Update Employee Period Salary

    Create or update a Period Salary with a given employee id

  • Create Or Update Revenue

    Create a new revenue record for a revenue unit on a given day or update an existing one

  • List Of Employees

    Get a list of active employee profiles

  • Get Employee By ID

    Get details of an employee's profile

  • Get Employee Field Definition

    Get a list of fields available when creating or updating an employee account

  • List Supervisors

    Retrieve a list of employees marked as supervisors

  • List Absence Accounts

    Returns all accounts filtered by account id, employee id, account type and status

  • List Absence Types

    Get available absence types

  • Get Absence Records

    Returns absence records matching given criteria

  • List Absence Requests

    Get all absence requests, filter by employee and/or absence request status

  • Get Account Balance

    Gets account balance for a specific account

  • Get Department By ID

    Get details of a department

  • Get Employee Group By ID

    Get details of an employee group

  • List Employee Types

    Get a list of available employee types

  • List Available Shifts

    Returns paginated list of available shifts matching given criteria

  • Get Shift By ID

    Returns shift by shift id

  • List Available Positions

    Returns paginated list of available positions

  • Get Position By ID

    Returns position by provided id

  • Get Employee Pay Rates In Employee Group

    Return pay rates for an employee in a specified employee group

  • Get Employee Pay Rates For All Groups

    Return pay rates of a given employee for all assigned employee groups

  • Get Employee Salary Allocation

    Return salary allocation for a given employee id

  • Get Employee Period Salary

    Return a Period Salary with a given employee id

  • List Salary Types

    Return available salary types

  • Get Payroll Data

    Returns the payroll data matching given criteria including departments, time period, and shift status

  • Get Revenue Records

    Get all revenue records matching the request criteria

  • List Employee Shifts For Today

    Returns a list of all of today's Employee Shifts

  • List Punch Clock Records

    Returns a list of all available Punch Clock records as specified in your parameters

  • Update Employee Group Pay Rates

    Update employees pay rates in a given employee group

  • Delete Revenue

    Delete revenue for a given date and revenue unit

  • Deactivate Employee

    Deactivate an employee account

  • Reactivate Employee

    Reactivate a previously deactivated employee account

  • Invite Employee

    Invite an employee by sending an invitation email

  • Change Employee Username

    Update an employee's username

  • Decline Absence Record

    Decline a specific absence record

  • Submit Absence Request

    Submit an absence request on behalf of an employee

  • Approve Absence Request

    Approve a specific absence request

  • Deny Absence Request

    Deny an absence request

  • Approve Shift

    Approve a shift that is ready for payroll processing

  • Assign Shift To Employee

    Assign a shift to a specific employee or set it to Open

Set Up Your Planday MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to Planday in under 10 lines of code.

MCP Clients

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

More HRIS / HCM MCP Servers

UKG Ready

140+ actions

Factorial

127+ actions

HiBob

123+ actions

Oracle Fusion HCM

120+ actions

Humaans

117+ actions

BambooHR

100+ actions

Planday MCP Server FAQ

Planday MCP server vs direct API integration — what's the difference?
A Planday MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Planday. A Planday MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling Planday at runtime. StackOne provides both.
How does Planday authentication work for AI agents?
Planday authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Planday account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Planday MCP tools vulnerable to prompt injection?
Yes — Planday MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a Planday agent and how do I avoid it?
Context bloat happens when Planday tool schemas and API responses eat your Planday agent's memory, preventing it from reasoning effectively. A single Planday query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my Planday agent can access?
Yes — you can limit which actions your Planday agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Planday MCP server?
Yes — you can create custom agent actions for your Planday MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Planday's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Planday MCP server?
Skip a Planday MCP server if your integration is purely software-to-software — direct Planday API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Planday actions at runtime.
What AI frameworks and AI clients does the StackOne Planday MCP server support?
The StackOne Planday MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.