Leemu OKRs

io.leemuPublished by leemu.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Read OKRs, submit key-result check-ins, and generate progress reports in Leemu.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant read OKRs, submit key-result check-ins, and generate progress reports in Leemu.

What you can do
This remote MCP server connects an assistant to Leemu, a goal and OKR tracking service. According to the registry description, it lets the assistant read OKRs, submit key-result check-ins, and generate progress reports. No individual tool names or parameters are listed in the supplied material.
When to use it
Use it when a team or individual tracks objectives and key results in Leemu and wants an assistant to review current OKRs, record check-ins, or produce progress reports without switching to the Leemu interface. It fits recurring goal-review and reporting routines rather than general task management.
Requirements
A remote MCP endpoint at using streamable HTTP. OAuth authentication is required, so a Leemu account and a completed authorization flow are needed. No environment variables, headers, or local packages are declared. Network access to the remote endpoint is required.
Before you install
The server can submit key-result check-ins, which writes data into Leemu and may change recorded progress; review what the assistant proposes before confirming. Access is granted through OAuth, so the connected account's permissions and any data the remote service stores should be considered. No other risks are shown in the supplied material.

Installation

In SourceWeft

  1. Open Leemu OKRs in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.leemu%2Fokr/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "leemu-okrs": {
      "type": "http",
      "url": "https://app.leemu.io/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 13, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.