Skip to main content

The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench • Explore Tool Discovery →

Live 29 Actions

Leapsome MCP Server
for AI Agents

Connect your AI agent to StackOne's Leapsome MCP server and give it 29 MCP tools out of the box. Auth, tool execution, and security all managed.

Start Free Book Demo Read Docs →
Leapsome logo
Leapsome MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

29 Agent Actions

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

MCP Actions → Build Actions →

Authentication

Agent Tool Authentication

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

Agent Auth →

Security

Agent Protection

Every Leapsome 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 Leapsome call.

Tools Discovery →

What is the Leapsome MCP Server?

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

All Leapsome MCP Tools

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

Review Cycles

  • List Review Cycles

    List review cycles

  • List Review Cycles

    List review cycles

Users

  • Create User

    Create User

  • Get Users

    Get Users

  • Get User

    Get User

  • Update User

    Update User

Groups

  • Create Group

    Create Group

  • Get Group

    Get Group

  • Update Group

    Update Group

Other (20)

  • Create Praise

    Create praise

  • Create Instant Feedback

    Create instant feedback

  • Create Private Note

    Create private note

  • List Employees

    List employees

  • List Access Roles

    List access roles

  • List Goals

    List goals

  • List Goal Tags

    List goal tags

  • List Goal Comments

    List goal comments

  • Get Goal Details

    Get goal details

  • List Review Cycle Participants

    List review cycle participants

  • List Feedback

    List feedback

  • List Document Categories

    List document categories

  • List Timesheets

    List timesheets

  • List Payroll Cycles

    List payroll cycles

  • List Payroll Cycle Participants

    List payroll cycle participants

  • List Work Locations

    List work locations

  • List Absences

    List absences

  • Update Employee Access Roles

    Update employee access roles

  • Update Key Result

    Update key result

  • Update Initiative

    Update initiative

Leapsome AI Agent Use Cases

Connect your AI agent to Leapsome and help your team scale the HR operations they run by hand today.

Employee Onboarding

Use StackOne to connect your AI agent to your HRIS, identity management, and LMS to automate employee onboarding.

View
WorkdayBambooHRPersonioHiBobGustoRipplingOkta360Learning
HR Policy Q&A Chatbot

Use StackOne to connect your AI agent to your HRIS, knowledge base, and messaging tools to automate HR policy Q&A.

View
WorkdayBambooHRPersonioHiBobGustoRipplingSharePointConfluence
Employee Offboarding

Use StackOne to connect your AI agent to your HRIS, identity management, and ITSM to automate employee offboarding and deprovisioning.

View
WorkdayBambooHRPersonioOktaServiceNowRipplingGustoJira
More HRIS & HCM use cases

Set Up Your Leapsome MCP Server in Minutes

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

MCP Clients

Claude Desktop setup guide
Claude Code setup guide
Cursor setup guide
Goose setup guide

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>"
      ]
    }
  }
}

Check More HRIS / HCM MCP Servers

UKG Ready

139+ actions

Workday (Rest and Soap)

128+ actions

Factorial

127+ actions

HiBob

123+ actions

Oracle Fusion HCM

120+ actions

Humaans

117+ actions

SAP SuccessFactors

111+ actions

All HRIS / HCM MCP Servers →

Platform Resources

MCP Code Mode: Keeping Tool Responses Out of Agent Context

Anthropic's code_execution processes data already in context. Custom MCP code mode keeps raw tool responses in a sandbox. 14K tokens vs 500.

11 min

Comparing BM25, TF-IDF, and Hybrid Search for MCP Tool Discovery

Benchmarking BM25, TF-IDF, and hybrid search for MCP tool discovery across 916 tools. The 80/20 TF-IDF/BM25 hybrid hits 21% Top-1 accuracy in under 1ms.

10 min

Indirect Prompt Injection Defense for MCP Tools: A Technical Guide

MCP tools that read emails, CRM records, and tickets are indirect prompt injection vectors. Here's how we built a two-tier defense that scans tool results in ~11ms.

12 min

MCP vs A2A: Architecture, Security, and When to Use Each

MCP vs A2A: what each protocol standardizes, how they differ, their shared security risks including indirect prompt injection, and when to use one, both, or a hybrid architecture.

12 min

MCP vs API: What 200+ Connector Builds Taught Us

MCP wraps APIs, it doesn't replace them. After building 200+ connectors that serve both, here's when each approach wins.

14 min read

Leapsome MCP Server FAQ

Does StackOne have a Leapsome MCP server?
Yes. StackOne offers a hosted Leapsome MCP server with 29 pre-built actions, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
Leapsome MCP server vs direct API integration — what's the difference?
A Leapsome MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Leapsome. A Leapsome 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 Leapsome at runtime. StackOne provides both.
How does Leapsome authentication work for AI agents?
Leapsome 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 Leapsome account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Leapsome MCP tools vulnerable to prompt injection?
Yes — Leapsome 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 Leapsome agent and how do I avoid it?
Context bloat happens when Leapsome tool schemas and API responses eat your Leapsome agent's memory, preventing it from reasoning effectively. A single Leapsome 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 Leapsome agent can access?
Yes — you can limit which actions your Leapsome 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 Leapsome MCP server?
Yes — you can create custom agent actions for your Leapsome MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Leapsome's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Leapsome MCP server?
Skip a Leapsome MCP server if your integration is purely software-to-software — direct Leapsome 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 Leapsome actions at runtime.
What AI frameworks and AI clients does the StackOne Leapsome MCP server support?
The StackOne Leapsome 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.

Start Free Book Demo