Leapsome MCP server

What the model can do

Leapsome people platform: goals and OKRs with progress, key results, owners and comments, performance review cycles with their timeline and who has completed which step, the employee directory (title, team, department, manager, location, start date), absences (vacation and remote work by type, other leave without its type), public praise and who gave feedback to whom, and work locations; when you ask, can give praise or instant feedback from a named person, write a private note, update a key result's progress, or clock an employee in or out.

Reads

• leapsome_list_goalsGoals and OKRs in Leapsome: name, type (company, team, personal), owner, status, progress percent and whether on track, deadline…
• leapsome_get_goalOne Leapsome goal in full: description, owner, contributors, progress and status, each key result with its metric (start, target, current)…
• leapsome_list_review_cyclesPerformance review cycles in Leapsome: name, status (draft, peer nominations, peer reviews, manager reviews, conversations pending, complete)…
• leapsome_get_review_cycleOne Leapsome review cycle: its status and deadlines (peer nominations, peer reviews, manager reviews, conversations) and, per reviewee…
• leapsome_list_employeesLeapsome's employee directory: name, work email, title, level, status, manager, teams, departments, work location and start date.
• leapsome_list_absencesAbsences recorded in Leapsome starting within a date range: who (user id), when, half days, duration and status.
• leapsome_list_feedbackPraise and instant feedback in Leapsome: who gave it to whom, when, the badge, likes and comments.
• leapsome_list_work_locationsWork locations in Leapsome: name, city, country, whether remote and whether primary.

Acts, when you ask

These change something in Leapsome. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• leapsome_give_praisePosts praise in Leapsome from the named sender to one or more colleagues.
• leapsome_give_instant_feedbackSends instant feedback in Leapsome from the named sender to one colleague.
• leapsome_add_private_noteWrites a private note in Leapsome about a colleague, visible only to its sender (the person named, usually their manager); nobody is notified.
• leapsome_update_key_resultUpdates a key result on a Leapsome goal: its name, weight, or its metric (type, start, target and current value, all four together, whole numbers).
• leapsome_record_clock_punchClocks an employee in or out in Leapsome time tracking, now or at a time up to 24 hours ago.

Connect it

First connect Leapsome on Dashboard → Connections, then add Memtro to your client once. The Leapsome tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Leapsome connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which Q4 goals are off track?
• › How far has the autumn review cycle got?
• › Which absences start next week?
• › Who joined the sales team this quarter?
• › Update the churn key result to 4 percent.

Questions

Is this an official Leapsome MCP server?

No. It is Memtro's MCP server with Memtro's Leapsome connector behind it: the connector reads Leapsome through its API with the credentials you connect on Dashboard → Connections, and Leapsome publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Leapsome?

Only when you ask, and only what it has been granted: give praise from a named person to colleagues; give instant feedback from a named person; write a private note about a colleague (visible only to its sender); update a key result's name, weight or progress; clock an employee in or out. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · People and HR

• BambooHR MCP server
• Personio MCP server
• Microsoft Entra ID MCP server
• Google Workspace MCP server
• HiBob MCP server
• Greenhouse MCP server