Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Leantime MCP (Unofficial)

by 4ladorversion 2.9.0i★ 0iRuns on your computerRepository ↗
Registry nameio.github.4lador/leantime-mcp

How to install

What it does

Unofficial MCP server for Leantime: 42 agent-first tools, backup/restore, dry-run validation

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score7/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Passed 3/3 checks · Runs on your computer

First: which AI do you use?

Pick your app and the steps appear below.

Claude cannot connect Leantime MCP (Unofficial) yet

The maker has not listed install details in the MCP Registry yet

ChatGPT cannot connect Leantime MCP (Unofficial) yet

The maker has not listed install details in the MCP Registry yet

What you can do instead

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Claude Code cannot connect Leantime MCP (Unofficial) yet

The maker has not listed install details in the MCP Registry yet

Cursor cannot connect Leantime MCP (Unofficial) yet

The maker has not listed install details in the MCP Registry yet

VS Code cannot connect Leantime MCP (Unofficial) yet

The maker has not listed install details in the MCP Registry yet

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Leantime MCP (Unofficial)💬 Discussion →

At a glance

Downloads per weeki
Not on npm/PyPI
Connection
Runs on your computer
Latest versioni
2.9.0
Categoryi
Other
Published to registryi
Sep 14, 2026
Code last changedi
Sep 14, 2026
Maker
4lador
Packages
cargo: leantime-mcp
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account 4lador, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 months ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked: only npm and PyPI packages with a version can be checked

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/4lador-leantime-mcp.svg)](https://mcp.popnx.com/en/servers/4lador-leantime-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20653 servers in this category
  • Published to the registry more recently than 39% of the other 20653 servers in this category
  • Basic checks equal to or better than 99% of the other 20653 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Leantime MCP (Unofficial) safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 2 months ago, and the latest version (2.9.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Rust on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Leantime MCP (Unofficial)
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

leantime-mcp

  • MCP Registry name: mcp-name: io.github.4lador/leantime-mcp

An unofficial Model Context Protocol server for Leantime, designed agent-first: it lets LLM tools (opencode, Claude Code, Claude Desktop, Cursor, Codex, or any MCP client) work on your Leantime projects through 42 tools with dry-run validation, bulk operations, backup/restore and one-call project context.

It is an independent, open-source integration — stdio only, running locally with your own API key and your own instance. It does not aim to replace Leantime's official offerings; if you want vendor-supported integrations, use those.

~3 MB self-contained binary (rustls — no system OpenSSL), ~1.2 ms median startup and ~5 MB idle memory (VmRSS after handshake — measured on a Linux x86_64 dev machine, n=100 spawns).

Documentation: Quick start · Configuration · Safety · Tools · Troubleshooting · Harness setup · Backup & recovery · Migration from v1.x · CHANGELOG · CONTRIBUTING · SECURITY

Demo

An example session (abridged):

You: What's the status of the Acme launch project?

Agent calls leantime_project_context — one call returning progress, health, sprint and milestones:

`json

{ "project": { "name": "Acme launch", "progress": { "percentDone": 64.5, "ticketsTotal": 279, "ticketsDone": 180 } },

"health": { "blocked": 0, "overdue": 7, "unassigned": 3, "openTotal": 99 },

"currentSprint": { "name": "Sprint 4", "status": "current", "daysRemaining": 6, "openTickets": 8 } }

`

Agent: Acme launch is at 64.5% (180 of 279 tickets done). 99 tickets are open — 7 overdue, 3 unassigned, none blocked. Sprint 4 ends in 6 days with 8 open tickets; the milestone in progress (PHASE 8) sits at 47.8%.

Features

  • 42 tools: projects, tickets, subtasks, milestones, sprints, comments, time tracking, bulk operations
  • leantime_project_context — the whole project picture in one call (progress, health, sprint, milestones), under 4 KB
  • dryRun: true on every mutation — same validations, from → to diffs on updates, no write requests
  • idempotencyKey on creation tools — a retried call with an already-succeeded key replays the original result instead of writing a duplicate
  • Result envelopes: structured truncated on capped lists, changed/unchanged diffs on updates — agents see what a call actually did
  • LEANTIME_MCP_PROFILE=readonly — a server-wide execution profile that removes write capabilities entirely
  • Backup retention (LEANTIME_MCP_BACKUP_RETENTION_DAYS), atomic backup writes, and a restore manifest mapping every old→new id
  • Bulk operations up to 50 items, validated upfront (all-or-nothing on creates)
  • Backup & restore — snapshot a project to local JSON, rebuild it into a new project
  • Adaptive rate-limit retries, transparent to agents
  • Credentials in a local keyring (mode 0600) — harness configs hold a bare command
  • Deletes confirm-gated; LEANTIME_MCP_DESTRUCTIVE_POLICY=deny as an emergency stop
  • Per-instance tool management — disable what you don't use, read-only mode in two commands
  • Markdown → Leantime rich HTML, converted deterministically server-side

Install

Linux / macOS (x86_64, aarch64):

curl -fsSL https://raw.githubusercontent.com/4lador/leantime-mcp/main/install.sh | sh

Windows (PowerShell):

irm https://raw.githubusercontent.com/4lador/leantime-mcp/main/install.ps1 | iex

Both installers verify the published SHA-256 checksum before installing and abort on mismatch. Release binaries cover all 5 targets — Linux (x86_64, aarch64), Windows x86_64 and macOS (Intel, ARM) — on the releases page.

Via cargo (requires the Rust toolchain):

cargo install leantime-mcp   # installs the leantmcp binary to ~/.cargo/bin

From source:

cargo build --release   # → target/release/leantmcp

Quick start

leantmcp url set https://your-instance.leantime.io   # once

leantmcp key set # once — hidden prompt leantmcp setup # writes the config leantmcp doctor # verify everything end-to-end

Your Leantime API key: My Account → API Keys → Generate on your instance.

HarnessDefault scopeConfig file
opencodeglobal~/.opencode/opencode.json
Claude Codeproject./.mcp.json
Claude Desktopglobalclaude_desktop_config.json (path per OS)
Cursorglobal~/.cursor/mcp.json
Codexglobal~/.codex/config.toml

Every generated config is a bare command with no credentials — the binary resolves them from the keyring at startup. Project-scoped setups, --scope/--instance/--name options and multiple instances: see Harness setup.

Configuration

Credentials live in named instance profiles — ~/.config/leantime/instances/ / (api-key, mode 0600, and instance-url), with a default file naming the default. The key is read from the keyring file or environment — it is not accepted as a command-line argument (shell history) and is not logged; key commands are CLI-only and are not exposed as MCP tools.

leantmcp url show          # resolved URL + where it comes from

leantmcp key show # masked display (lt_h13…Fc3O) leantmcp key test # live validation against the instance leantmcp key rotate # mint a new key (same role), verify it live, replace the stored one leantmcp instance add … # multiple Leantime instances (see Harness setup)

LEANTIME_URL / LEANTIME_API_KEY environment variables remain available as per-run overrides; LEANTIME_INSTANCE selects a profile. Resolution order: env (explicit override) → LEANTIME_INSTANCE profile → the default file.

Safety

This software is provided without warranty (MIT). It drives Leantime with your API key on your behalf — back up your Leantime data before letting agents operate on it.

  • Deletes are confirm-gated (confirm: true required by default; LEANTIME_MCP_DESTRUCTIVE_POLICY=deny refuses them outright, allow skips the gate for CI). Project hiding/deletion is intentionally not exposed.
  • Dry runs: every mutation tool accepts dryRun: true — validations run, updates resolve from → to values (with status labels), bulk tools return per-item previews, and no write request is sent. Agent guidance is built into the tool descriptions on a three-tier policy: direct execution for explicit values, dry-run-then-confirm when the agent chose the values itself, dry-run mandated for bulk.
  • Assignment is mandatory on ticket/milestone creation (editorId validated against the real user list, or an explicit unassigned: true).
  • Tool management: disabled tools are omitted from tools/list (no context-window cost) and calling one is refused with an actionable error. Read-only mode: leantmcp tools disable all && leantmcp tools enable readonly. State is stored per instance profile.
  • Backup-first: leantime_backup_project (MCP) or leantmcp backup (CLI) snapshot a project cheaply — agents are instructed to use it before bulk modifications. See Backup & recovery.

Tools

42 tools across 9 domains: projects & clients (8), tickets (10), comments (4), time tracking (4), milestones (6), sprints (4), users (1), bulk operations (3), backup & context (2). Updates use the patch API — only provided fields change. Descriptions follow a Markdown subset converted server-side; raw HTML in input is escaped.

Supported Markdown subset (for descriptions and comments)

MarkdownResult
# … ####Headings (levels 5+ clamp to h4)
blank-line separated textParagraphs (single newlines become line breaks)
- item / 1. itemUnordered / ordered lists (nesting supported)
- [ ] x / - [x] xInteractive checklists
**bold**, *italic*, ~~strike~~Emphasis
`code` and fenced ` blocksInline and block code
[label](https://…)Links (http/https/mailto only)
> quoteBlockquote
---Horizontal rule

Raw HTML in descriptions is escaped before reaching Leantime — it renders as literal text.

All 42 tools (click to expand)

Projects & clients

ToolDescription
leantime_list_projectsList all projects
leantime_get_projectGet project details
leantime_get_project_progressGet project progress metrics
leantime_create_projectCreate a project (Markdown details, clientId required)
leantime_update_projectUpdate a project (patch — only provided fields change)
leantime_find_projectsSearch projects by name
leantime_list_project_usersList users assigned to a project (valid editorId candidates)
leantime_list_clientsList clients (clientId needed to create projects)

Tickets

ToolDescription
leantime_list_ticketsList tickets with filters (status, milestone, sprint, user, type, search)
leantime_get_ticketGet ticket details
leantime_create_ticketCreate a ticket (Markdown description, mandatory assignment, subtasks via dependingTicketId; dryRun supported)
leantime_update_ticketUpdate a ticket (patch — only provided fields change; dryRun supported)
leantime_delete_ticketDelete a ticket (confirm-gated)
leantime_list_subtasksList a ticket's subtasks
leantime_my_tasksOpen tickets assigned to a user (default: the API key owner)
leantime_get_ticket_optionsPriorities, efforts, kanban columns and ticket types
leantime_get_statusesGet status labels for a project
leantime_get_ticket_typesGet ticket types for a project

Comments

ToolDescription
leantime_list_commentsList a ticket's discussion
leantime_add_commentComment on a ticket (Markdown converted to rich HTML)
leantime_update_commentEdit a comment (Markdown)
leantime_delete_commentDelete a comment (confirm-gated)

Time tracking

ToolDescription
leantime_log_timeLog hours on a ticket (add accumulates, set is idempotent; dryRun supported)
leantime_get_ticket_timeTotal and per-day booked time for a ticket
leantime_list_timesheetsList time entries between two dates
leantime_delete_timesheet_entryDelete a time entry (confirm-gated)

Milestones

ToolDescription
leantime_list_milestonesList milestones of a project
leantime_get_milestoneGet milestone details
leantime_create_milestoneCreate a milestone (Markdown description, mandatory assignment; dryRun supported)
leantime_update_milestoneUpdate a milestone (patch; dryRun supported)

| `leantime_get_milestone_progres

Only the beginning is shown; read the rest in the repo