Manage OKRs from your AI assistant
Leemu runs a remote MCP (Model Context Protocol) server. Connect it to Claude, Cursor, or any MCP client and your assistant can read your OKRs, submit check-ins, and write progress reports without you leaving the tool you already work in. Read the announcement.
Server URL
https://app.leemu.io/api/mcpSign-in uses OAuth. Your assistant acts with your permissions, never more, and every change is recorded in your workspace audit log.
Setup
Claude (claude.ai and Claude Desktop)
- Open Settings → Connectors and choose Add custom connector.
- Paste
https://app.leemu.io/api/mcpas the URL. - A Leemu consent screen opens. Sign in, review the permissions, and approve.
Claude Code
claude mcp add --transport http leemu https://app.leemu.io/api/mcpCursor and other MCP clients
Add this to your MCP configuration. Clients that support OAuth discovery find the sign-in endpoints automatically.
{
"mcpServers": {
"leemu": {
"url": "https://app.leemu.io/api/mcp"
}
}
}Verify the connection
Ask your assistant: “Use the whoami tool on Leemu.” It should return your name, role, teams, and the permissions you granted.
Example prompts
- What are my key results this quarter, and which ones haven't I checked in on?
- 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.
- Which of my team's OKRs are at risk, and why?
- Draft a set of OKRs for Q4 focused on retention, and score them before proposing.
What your assistant can do
Available tools depend on your role in Leemu and the permissions you approved when connecting.
Everyone
- List and read objectives, key results, check-ins, and cycles
- See the OKR hierarchy and how work aligns to strategy
- Submit check-ins on key results you own
- Create and update your own objectives
- Generate reports on your own OKRs
- Score a draft objective against SMART criteria
Team leads, additionally
- Update objectives and submit check-ins for teams you lead
- Report on team progress and check-in compliance
Workspace admins, additionally
- Create and update company-level objectives
- Create and manage strategic goals
- Generate company-wide reports
- List workspace members
Security and control
- Never more than your own permissions. The same rules that apply to you in the web app apply to your assistant.
- Permissions are checked live. If your role changes, the assistant's access changes on its next request. No reconnect needed.
- Nothing is permanently deleted. The assistant can archive objectives and key results, which you can undo in the web app.
- Big changes need your approval. A full OKR set or a strategic goal is created as a proposal you review and approve in Leemu.
- Everything is logged. Assistant-made changes appear in your audit log, tagged with the client that made them.
Settings → Connections lists every connected assistant, its permissions, and when it was last used. Revoking takes effect immediately. Connections stay signed in while in use; one left unused for 90 days expires.
Plans and limits
- Free: read-only access, 500 tool calls per month. Enough to try it on your real OKRs.
- Paid plans: write access (check-ins, objective edits, proposals) and higher limits.
- Usage is counted in tool calls. Failed calls are not counted.
- Rate limit: 120 tool calls per minute, up to 30 writes.
Troubleshooting
- “Please verify your email address”
- Writes require a verified email. Reads work without it.
- A tool says it needs a permission you don't have
- Either your role doesn't allow it (ask a workspace admin), or you didn't grant it when connecting. Disconnect and reconnect to grant more.
- “Not found” for an OKR you know exists
- It's outside your permissions. Leemu reports “not found” rather than “forbidden” so private objectives aren't disclosed.
Don't have a Leemu workspace yet?
Create a free workspace, add your OKRs, then connect your assistant.
Start free