x=hub

your toolset

    build deployment
    sign in

    Leantime MCP (Unofficial)

    mcpother
    io.github.4lador/leantime-mcp · v2.9.0
    deploy just this

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

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    # once, as root:
cargo install --locked leantime-mcp --version 2.9.0 --root /usr/local

#!/usr/bin/env bash
# leantime (io.github.4lador/leantime-mcp), recipe baremetal (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-leantime.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec uvx mcp-proxy --host 127.0.0.1 --port 8101 --pass-environment -- leantime-mcp

[Unit]
Description=MCP server leantime (toolset my-agent), generated by Hub
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=mcp
Group=mcp
EnvironmentFile=/etc/mcp/my-agent.env
Environment=HOME=/var/lib/mcp/leantime
WorkingDirectory=/var/lib/mcp/leantime
ExecStart=/opt/mcp/my-agent/bin/leantime.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/leantime

[Install]
WantedBy=multi-user.target

    connect to it

    copy what your client needs
    leantime-mcp
    {
  "mcpServers": {
    "leantime": {
      "command": "leantime-mcp",
      "args": []
    }
  }
}
    #!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add leantime -- leantime-mcp

    {
  "mcpServers": {
    "leantime": {
      "command": "leantime-mcp",
      "args": []
    }
  }
}
    {
  "servers": {
    "leantime": {
      "type": "stdio",
      "command": "leantime-mcp",
      "args": []
    }
  }
}
    name: my-agent
target: local
servers:
- hub: io.github.4lador/leantime-mcp
    • not probed yet: tools unpinned, ingest lists them

    tools

    Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.