Connectors · Accounting & finance
Leapsome MCP server for AI agents.
actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Leapsome and the rest of your systems. It gives your agent 25 Leapsome actions (19 reads and 6 writes) and holds the Leapsome credential itself, so the agent never does. It paces Leapsome's limits and records every call.
100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.
claude mcp add --transport http actionlake https://connect.actionlake.com/mcpdo { action: "leapsome.employees.list", intent: "check which Leapsome account is connected"}# List employees · read · 1 upstream call- 25actionsin one signed file
- 19readlook, never change
- 6writecreate and update
- 0wait for a yesdestructive, confirmed first
Set up
Connect Leapsome in three steps.
- 01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp - 02
Connect Leapsome.
Session login. actionlake opens the session and renews it when it expires. actionlake stores what you paste write-only, sealed under your tenant's key.
api_secretLeapsome API secret
account { op: "connections.requirements", service: "leapsome" } # free: exactly what to paste, and what is found for you - 03
Make the first call. Check before a write.
Ask in plain words; Claude picks the action. Before anything changes,
checkvalidates the call and prices it, for free.do { action: "leapsome.employees.list" }# list employees · read · 1 upstream callcheck { action: "leapsome.praise.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent
Leapsome at a glance
- Sign-in
- Session login. actionlake opens the session and renews it when it expires.
- You provide
api_secret- Limits we pace to
- 20 calls a second, per connection
- API covered
- Leapsome Content API v1 (OpenAPI 3.0.1, 1.0.1)
api.leapsome.com/v1 - Built from
- Leapsome's documentation, read 23 October 2026api.leapsome.comapi.leapsome.com
- Service file
- Version 1.0.0, signed (Ed25519)
- Cached reads
- 19 of 19 reads, for up to 5 minutes; a write clears what it affects
- Shared entities
- 2, so ask can line Leapsome up with your other systems
- Data
- Processed and stored in Sydney, Australia. No US region yet
Capabilities
What an AI agent can do in Leapsome.
25 actions in 22 areas. Every one carries its effect, so a key can allow the reads and hold the rest.
- 19readlook, never change
- 6writecreate and update
- 0destructivewait for a confirmation
Goals
22 read · 0 write · 0 destructive
List goals · Get goal details
Review participants
22 read · 0 write · 0 destructive
List review cycle participants · Get results for a specific reviewee
Reviews
22 read · 0 write · 0 destructive
List review cycles · List review cycles
Absences
11 read · 0 write · 0 destructive
List absences
Access roles
11 read · 0 write · 0 destructive
List access roles
API info
11 read · 0 write · 0 destructive
API info
Document categories
11 read · 0 write · 0 destructive
List document categories
Employee access roles
10 read · 1 write · 0 destructive
Update employee access roles
14 more areas · 14 actions
- Employees 1
- Employments 1
- Feedback 1
- Goal comments 1
- Goal tags 1
- Initiatives 1
- Instant feedback 1
- Key results 1
- Payroll cycle participants 1
- Payroll cycles 1
- Praise 1
- Private notes 1
- Timesheets 1
- Work locations 1
Top actions
The Leapsome API, shaped for agents.
The ids your agent types, what each does, and the one name it shares with other systems. 5 of Leapsome's 5 action names are shared with at least one other connector, so an agent learns them once.
| Action | What it does | Effect | Same name in |
|---|---|---|---|
leapsome.employees.listList employees | List employees. | read | hr.employee.list61 connectors |
leapsome.work_locations.listList work locations | List work locations. | read | hr.location.list32 connectors |
leapsome.access_roles.listList access roles | List access roles. | read | identity.role.list184 connectors |
leapsome.payroll_cycles.listList payroll cycles | List payroll cycles. | read | hr.pay_run.list14 connectors |
leapsome.timesheets.listList timesheets | List timesheets. | read | work.timesheet.list20 connectors |
leapsome.goals.listList goals | List goals. | read | this connector |
leapsome.reviews.listList review cycles | List review cycles. | read | this connector |
leapsome.absences.listList absences | List absences. | read | this connector |
leapsome.feedback.listList feedback | List feedback. | read | this connector |
leapsome.praise.createCreate praise | Create praise. | write | this connector |
leapsome.private_notes.createCreate private note | Create private note. | write | this connector |
leapsome.instant_feedback.createCreate instant feedback | Create instant feedback. | write | this connector |
Try it
Prompts to paste into Claude.
Each one names the Leapsome actions it will call, so you know what it reads and what it changes before you send it.
- Readread
List everyone in Leapsome with their department and start date.
calls
leapsome.employees.list - Writewrite
Create praise in Leapsome. Show me exactly what you will send before you save it.
calls
leapsome.praise.create
Governance for Leapsome
Every write can wait for a yes.
None of Leapsome's actions is destructive. A key can still be held to reads, capped, and set so a person confirms every write.
A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.
account { op: "keys.create", name: "leapsome-agent", allowed_actions: ["leapsome.*"], cap_calls: 2000, confirm_policy: "human_for_writes"}Cost
What Leapsome costs on actionlake.
Every Leapsome action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Leapsome refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
- 1upstream call per actionall 25 Leapsome actions
- 25actions pageeach page of a long list is one call
- 19reads can be cacheda cache hit costs nothing
- 100,000calls a month, freepaid plans from US$49 a month for 250,000
Action index
Every Leapsome action.
25 actions by area: the id your agent calls, what it does, and its effect.
Goals2
leapsome.goals.getGet goal detailsreadleapsome.goals.listList goalsread
Review participants2
leapsome.review_participants.get_overviewGet results for a specific revieweereadleapsome.review_participants.listList review cycle participantsread
Reviews2
leapsome.reviews.getList review cyclesreadleapsome.reviews.listList review cyclesread
Absences1
leapsome.absences.listList absencesread
Access roles1
leapsome.access_roles.listList access rolesread
API info1
leapsome.api_info.getAPI inforead
Document categories1
leapsome.document_categories.listList document categoriesread
Employee access roles1
leapsome.employee_access_roles.updateUpdate employee access roleswrite
Employees1
leapsome.employees.listList employeesread
Employments1
leapsome.employments.listList employmentsread
Feedback1
leapsome.feedback.listList feedbackread
Goal comments1
leapsome.goal_comments.listget list of comments for a goalread
Goal tags1
leapsome.goal_tags.listget list of goal tagsread
Initiatives1
leapsome.initiatives.updateUpdate initiativewrite
Instant feedback1
leapsome.instant_feedback.createCreate instant feedbackwrite
Key results1
leapsome.key_results.updateUpdate key resultwrite
Payroll cycle participants1
leapsome.payroll_cycle_participants.listList payroll cycle participantsread
Payroll cycles1
leapsome.payroll_cycles.listList payroll cyclesread
Praise1
leapsome.praise.createCreate praisewrite
Private notes1
leapsome.private_notes.createCreate private notewrite
Timesheets1
leapsome.timesheets.listList timesheetsread
Work locations1
leapsome.work_locations.listList work locationsread
Questions
The Leapsome MCP server, answered.
Is there a Leapsome MCP server for Claude?
Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 25 Leapsome actions across goals, review participants, reviews and absences, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Leapsome.
What do I need to connect Leapsome?
Leapsome API secret. The free call account { op: "connections.requirements", service: "leapsome" } lists exactly what to paste.
Can an AI agent change things in Leapsome?
Only if its key allows it. 6 Leapsome actions write, and none is destructive. A key can be limited to reads, capped, and set so a person confirms every write.
Will an AI agent use up my Leapsome API limit?
actionlake paces every call to the limits in the Leapsome service file: 20 calls a second per connection. Repeated reads are answered from cache (19 Leapsome actions can be), which never reaches Leapsome.
What does a Leapsome action cost?
One upstream call, the only unit actionlake bills. A list that pages bills one call per page (25 Leapsome actions page). Cache hits, searches, dry runs and calls Leapsome refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
Which Leapsome API does it cover?
The Leapsome Content API v1 (OpenAPI 3.0.1, 1.0.1) at api.leapsome.com/v1. It is built from Leapsome's documentation as read on 23 October 2026. 25 actions in 22 areas, each one in the signed service file (version 1.0.0).
Does actionlake keep my Leapsome data, and where?
actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Leapsome credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.
Which AI clients can use it?
Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.
Give your agent Leapsome today.
Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.