World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Unofficial MCP server for Leantime: 42 agent-first tools, backup/restore, dry-run validation
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 7/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
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
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
cargo: leantime-mcpBased 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
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account 4lador, which owns the repo
Code last changed 2 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/4lador-leantime-mcp)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.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed 2 months ago, and the latest version (2.9.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Rust on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
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
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Leantime MCP (Unofficial) | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
mcp-name: io.github.4lador/leantime-mcpAn 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
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%.
leantime_project_context — the whole project picture in one call (progress, health, sprint, milestones), under 4 KBdryRun: true on every mutation — same validations, from → to diffs on updates, no write requestsidempotencyKey on creation tools — a retried call with an already-succeeded key replays the original result instead of writing a duplicatetruncated on capped lists, changed/unchanged diffs on updates — agents see what a call actually didLEANTIME_MCP_PROFILE=readonly — a server-wide execution profile that removes write capabilities entirelyLEANTIME_MCP_BACKUP_RETENTION_DAYS), atomic backup writes, and a restore manifest mapping every old→new idLEANTIME_MCP_DESTRUCTIVE_POLICY=deny as an emergency stopLinux / 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
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.
| Harness | Default scope | Config file |
|---|---|---|
| opencode | global | ~/.opencode/opencode.json |
| Claude Code | project | ./.mcp.json |
| Claude Desktop | global | claude_desktop_config.json (path per OS) |
| Cursor | global | ~/.cursor/mcp.json |
| Codex | global | ~/.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.
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.
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.
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.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.editorId validated against the real user list, or an explicit unassigned: true).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.leantime_backup_project (MCP) or leantmcp backup (CLI) snapshot a project cheaply — agents are instructed to use it before bulk modifications. See Backup & recovery.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)
| Markdown | Result |
|---|---|
# … #### | Headings (levels 5+ clamp to h4) |
| blank-line separated text | Paragraphs (single newlines become line breaks) |
- item / 1. item | Unordered / ordered lists (nesting supported) |
- [ ] x / - [x] x | Interactive checklists |
**bold**, *italic*, ~~strike~~ | Emphasis |
`code` and fenced ` blocks | Inline and block code |
[label](https://…) | Links (http/https/mailto only) |
> quote | Blockquote |
--- | Horizontal rule |
Raw HTML in descriptions is escaped before reaching Leantime — it renders as literal text.
All 42 tools (click to expand)
Projects & clients
| Tool | Description |
|---|---|
leantime_list_projects | List all projects |
leantime_get_project | Get project details |
leantime_get_project_progress | Get project progress metrics |
leantime_create_project | Create a project (Markdown details, clientId required) |
leantime_update_project | Update a project (patch — only provided fields change) |
leantime_find_projects | Search projects by name |
leantime_list_project_users | List users assigned to a project (valid editorId candidates) |
leantime_list_clients | List clients (clientId needed to create projects) |
Tickets
| Tool | Description |
|---|---|
leantime_list_tickets | List tickets with filters (status, milestone, sprint, user, type, search) |
leantime_get_ticket | Get ticket details |
leantime_create_ticket | Create a ticket (Markdown description, mandatory assignment, subtasks via dependingTicketId; dryRun supported) |
leantime_update_ticket | Update a ticket (patch — only provided fields change; dryRun supported) |
leantime_delete_ticket | Delete a ticket (confirm-gated) |
leantime_list_subtasks | List a ticket's subtasks |
leantime_my_tasks | Open tickets assigned to a user (default: the API key owner) |
leantime_get_ticket_options | Priorities, efforts, kanban columns and ticket types |
leantime_get_statuses | Get status labels for a project |
leantime_get_ticket_types | Get ticket types for a project |
Comments
| Tool | Description |
|---|---|
leantime_list_comments | List a ticket's discussion |
leantime_add_comment | Comment on a ticket (Markdown converted to rich HTML) |
leantime_update_comment | Edit a comment (Markdown) |
leantime_delete_comment | Delete a comment (confirm-gated) |
Time tracking
| Tool | Description |
|---|---|
leantime_log_time | Log hours on a ticket (add accumulates, set is idempotent; dryRun supported) |
leantime_get_ticket_time | Total and per-day booked time for a ticket |
leantime_list_timesheets | List time entries between two dates |
leantime_delete_timesheet_entry | Delete a time entry (confirm-gated) |
Milestones
| Tool | Description |
|---|---|
leantime_list_milestones | List milestones of a project |
leantime_get_milestone | Get milestone details |
leantime_create_milestone | Create a milestone (Markdown description, mandatory assignment; dryRun supported) |
leantime_update_milestone | Update a milestone (patch; dryRun supported) |
| `leantime_get_milestone_progres