Leantime MCP server

What the model can do

Leantime project management: projects, tasks and other tickets with status, assignee, milestone and due date, what changed since a date, a status summary, and ticket comments. Can create a task, a project, a client, a comment, or log time on a ticket, change a ticket's fields, edit a comment, move a ticket to another project, and delete a ticket, comment, sprint or project.

Reads

• leantime_projectsLeantime projects the key's user can see: id, name, client, open or closed, start and end, hour budget.
• leantime_ticketsSearch Leantime tickets (tasks, bugs, stories, subtasks): headline, project, status, assignee, milestone, due date, hours, when last changed.
• leantime_ticketOne Leantime ticket in full, with its description, and optionally its comments.
• leantime_commentsComments on a Leantime ticket or project (project comments include status updates), oldest first, the last 50.
• leantime_status_summaryCounts of Leantime tickets by type and status, plus the active ones (most recently changed first), for one project or every project the key can see.
• leantime_hour_typesThe kinds of time Leantime accepts on a time entry (the 'kind' for leantime_log_time).
• leantime_sprintsSprints of one Leantime project: id (for leantime_delete_sprint), name, start and end.

Acts, when you ask

These change something in Leantime. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• leantime_create_taskCreate a task in a Leantime project, as the API key's user.
• leantime_add_commentAdd a comment to a Leantime ticket or project, as the API key's user.
• leantime_log_timeLog hours against a Leantime ticket, as the API key's own user, on a day.
• leantime_create_projectCreate a Leantime project for a client, restricted to its assigned members, as the API key's user.
• leantime_update_ticketChange fields of an existing Leantime ticket.
• leantime_delete_ticketPermanently delete a Leantime ticket (a milestone is deleted with Leantime's own milestone cascade).
• leantime_delete_commentPermanently delete a Leantime comment.
• leantime_delete_projectPermanently delete a Leantime project and its members' assignments to it.
• leantime_edit_commentReplace the text of a Leantime comment.
• leantime_move_ticketMove a Leantime ticket to another project.
• leantime_delete_sprintPermanently delete a Leantime sprint.
• leantime_create_clientCreate a client (a customer company) in Leantime, to own projects.

Connect it

First connect Leantime on Dashboard → Connections, then add Memtro to your client once. The Leantime tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Leantime connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Where does the Website relaunch project stand?
• › Which tickets moved this week across all projects?
• › What are the latest status updates on the Northwind project?
• › Log two hours of development on ticket 418 for today
• › Move ticket 512 into the Acme rollout project

Questions

Is this an official Leantime MCP server?

No. It is Memtro's MCP server with Memtro's Leantime connector behind it: the connector reads Leantime through its API with the credentials you connect on Dashboard → Connections, and Leantime publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Leantime?

Only when you ask, and only what it has been granted: create a task in a Leantime project; add a comment to a Leantime ticket or project; log hours against a Leantime ticket; create a Leantime project; change fields of a Leantime ticket; delete a Leantime ticket; delete a Leantime comment; delete a Leantime project; edit the text of a Leantime comment; move a Leantime ticket to another project; delete a Leantime sprint; create a Leantime client. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server