Skip to main content
+
L

OKR MCP server · Works with Claude

Your OKRs, inside Claude

Connect Leemu to Claude, Claude Code, or Cursor. Ask about progress, submit check-ins in plain language, and find at-risk OKRs without opening another tab.

Free plan: read-only access and 500 tool calls per month.

Connect in 3 steps

1

Create a Leemu account

Sign up free and set up your objectives and key results.

2

Add the connector

In Claude, go to Settings → Connectors → Add custom connector and paste the server URL.

3

Sign in and approve

Sign in to Leemu, review the consent screen, and start asking about your OKRs.

# Server URL (Claude, Claude Desktop, Cursor)

https://app.leemu.io/api/mcp

# Claude Code

$ claude mcp add --transport http leemu https://app.leemu.io/api/mcp

Remote MCP server over Streamable HTTP with OAuth sign-in. Listed in the MCP Registry as io.leemu/okr.

Ask the way you'd ask a colleague

Example prompts and the kind of response you can expect. Responses below are illustrative; real answers come from your own Leemu data.

What are my key results this quarter, and which ones haven't I checked in on?
You own several key results in the current cycle. I've listed each with its latest progress, and flagged the ones with no recent check-in so you can update them first.

Illustrative response

Check in on my activation-rate key result: we're at 34% now. The onboarding rewrite shipped, but the email sequence is still blocked on design.
Done. I recorded a check-in on your activation-rate key result at 34%, noted that the onboarding rewrite shipped, and logged the email sequence as blocked on design.

Illustrative response

Which of my team's OKRs are at risk, and why?
I found the team OKRs that are behind pace for this point in the cycle. For each one I've summarized the gap and the blockers mentioned in recent check-ins.

Illustrative response

Draft a set of OKRs for Q4 focused on retention, and score them before proposing.
I drafted objectives and key results focused on retention and scored each against SMART criteria. I sent the set to Leemu as a proposal, so nothing changes until you approve it there.

Illustrative response

What the assistant can do

Read your OKRs

Objectives, key results, check-ins, and cycles, available to Claude when you ask.

See alignment

Follow the OKR hierarchy and how each objective ladders up to strategy.

Check in in plain language

Describe where things stand and the assistant records the check-in for you.

Create and update objectives

Draft and edit your own objectives without switching tabs.

Score drafts against SMART

Get a SMART score on a draft objective before you commit to it.

Find at-risk OKRs

Ask which goals are behind and why, based on progress and check-in notes.

Generate progress reports

Summaries of your OKRs, or your team's and company's if your role allows.

Check-in compliance

See who has and hasn't checked in, so follow-ups take one question.

Role-aware actions

Team leads act for their teams. Admins manage company objectives and strategic goals.

You stay in control

Connecting an AI assistant shouldn't mean handing over the keys.

Your permissions, never more

The assistant can only do what you can do in Leemu. Permissions are re-checked on every call, so a role change applies instantly.

Nothing is permanently deleted

Removals are archives, and archives are reversible.

You approve big changes

Full OKR sets and strategic goals become proposals that you review and approve in Leemu.

Every change is audit-logged

Each change is recorded and tagged with the assistant that made it.

Revoke access any time

Settings → Connections lists every connected assistant. Connections unused for 90 days expire.

Works with

Claude

claude.ai and Claude Desktop

Claude Code

One command in your terminal

Cursor

Add as a remote MCP server

Other MCP clients

Any client with OAuth discovery

Included in every plan

Free

Read-only access and 500 tool calls per month. Ask about progress, alignment, and at-risk OKRs.

Standard $8 · Premium $15 per user/month

Write access, so the assistant can submit check-ins and update objectives, plus higher limits.

Frequently asked questions

What is the Leemu MCP server?

It's a remote Model Context Protocol (MCP) server at https://app.leemu.io/api/mcp that lets AI assistants like Claude read and update your OKRs in Leemu. It uses Streamable HTTP with OAuth sign-in, and it's listed in the MCP Registry as io.leemu/okr.

How do I connect Leemu to Claude?

In Claude or Claude Desktop, open Settings → Connectors → Add custom connector and paste https://app.leemu.io/api/mcp. In Claude Code, run: claude mcp add --transport http leemu https://app.leemu.io/api/mcp. Then sign in to Leemu and approve access on the consent screen.

Does it work with tools other than Claude?

Yes. It works with Claude, Claude Code, Cursor, and any MCP client that supports OAuth discovery.

Can the assistant see or change things I don't have access to?

No. The assistant never exceeds your own Leemu permissions, and permissions are re-checked on every call. Nothing can be permanently deleted, big changes become proposals you approve in Leemu, and every change is audit-logged.

Is the Claude integration free?

The Free plan includes read-only access and 500 tool calls per month. Paid plans add write access, such as check-ins and objective updates, and higher limits. Standard is $8 per user per month and Premium is $15 per user per month.

How do I disconnect an assistant?

Go to Settings → Connections in Leemu to see every connected assistant and revoke access. Connections that go unused for 90 days expire automatically.

Full setup steps and the complete tool list are in the MCP documentation. For background, read Your OKRs now work inside Claude and Cursor.

Bring your OKRs into Claude

Create a free Leemu account, connect the MCP server, and ask your first question in a few minutes.