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
목록은 사용 점수(100점 만점)로 정렬되며 구성은 다음과 같습니다
| 인기 | 0/80 | GitHub 별 또는 주간 다운로드: 큰 쪽 60, 작은 쪽 20 |
|---|---|---|
| 최신성 | 7/12 | 30일 안에 릴리스나 코드 변경이 있으면 만점 |
| 응답 중 | 0/8 | 마지막 점검 때 클라우드 엔드포인트가 응답 |
| 사용 점수 | 7/100 |
품질: 기본 점검 3/3개 통과(표시만, 정렬에는 안 씀) · 상승세: 데이터 없음 (급상승 탭에서만 사용)
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
검사 3/3 통과 · 내 컴퓨터에서 실행돼요
먼저: 어떤 AI를 쓰시나요?
쓰는 앱을 고르면 아래에 단계가 나옵니다.
Claude는 아직 Leantime MCP (Unofficial)에 연결할 수 없어요
제작자가 아직 MCP 레지스트리에 설치 방법을 올리지 않았어요
ChatGPT는 아직 Leantime MCP (Unofficial)에 연결할 수 없어요
제작자가 아직 MCP 레지스트리에 설치 방법을 올리지 않았어요
B · 기타에서 ChatGPT에 연결되는 다른 서버
같은 분류에서 많이 쓰는 것 중 키 없이 주소만으로 연결되는 것을 골랐어요
Claude Code는 아직 Leantime MCP (Unofficial)에 연결할 수 없어요
제작자가 아직 MCP 레지스트리에 설치 방법을 올리지 않았어요
Cursor는 아직 Leantime MCP (Unofficial)에 연결할 수 없어요
제작자가 아직 MCP 레지스트리에 설치 방법을 올리지 않았어요
VS Code는 아직 Leantime MCP (Unofficial)에 연결할 수 없어요
제작자가 아직 MCP 레지스트리에 설치 방법을 올리지 않았어요
cargo: leantime-mcp이 서버의 연결 방식과 각 앱의 공식 문서를 바탕으로 했어요. 2026년 11월 10일 확인.
내 컴퓨터에서 실행하는 앱
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 18일 점검
레지스트리 이름이 GitHub 계정 4lador 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
코드 마지막 변경: 2개월 전
MIT 사용
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/servers/4lador-leantime-mcp)질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.
아직 리뷰가 없어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 2개월 전 변경됐고, 최신 버전(2.9.0)은 2개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Rust도 있어야 해요.
같은 카테고리에는: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
같은 카테고리, 다른 제작자, 명령 확인 완료. 공식이 먼저, 그다음 스타 순.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
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.
| 이 항목 Leantime MCP (Unofficial) | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 실행 위치 | 컴퓨터에 설치 필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 |
| 키 필요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 |
| Claude에서 +로 추가 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 |
| 기본 점검 | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 라이선스 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 가격 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 |
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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