Friday summary
The founder asks where the Acme rollout stands. Memtro reads the status summary for that project, gives the counts of open, blocked and done tickets, and lists the four that changed this week with their assignees.
Ask where a Leantime project stands, and which tickets moved this week.
Connect Leantime with your host name and an API key and Memtro reads projects, tasks and other tickets with status, assignee, milestone and due date, changes since a date, a status summary and comments. The key acts as an API user with its role and sees only its projects, and there is no hourly sync. When you ask, and once an administrator has granted them by name, it can create tasks, projects and clients, comment, which notifies the project's members, log hours, change tickets or move them to another project, and permanently delete a ticket, comment, sprint or project.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Leantime tool, reads what it needs, and answers with the source cited.
These tools change something in Leantime. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Leantime is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
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
The founder asks where the Acme rollout stands. Memtro reads the status summary for that project, gives the counts of open, blocked and done tickets, and lists the four that changed this week with their assignees.
Priya Sharma asks Memtro to log three hours of design against the BigCo homepage ticket and create a follow-up task for the mobile layout. With the actions granted, Memtro logs the hours as the key's user and creates the task, and Leantime notifies the project's members of it.
The teams that lean on Leantime most, a question each of them asks, and what they connect beside it.
A record in Leantime is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Needs a Leantime 3.13 or later server reachable from the internet, and an administrator to create the key
An administrator opens Leantime → Company Settings → API Keys and creates a key with the narrowest role and projects that will do. A read-only role is enough for reading, Editor or above to create, change or delete tickets, and manager or above to delete a project
In Connections → Leantime in Memtro type the Host name only, with no https://, path or port, a public DNS name with a publicly trusted certificate, and paste the API key, shown once
Ask what moved in the Website project this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Leantime tools are the same everywhere.
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. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Host and API key. Needs a Leantime 3.13 or later server reachable from the internet, and an administrator to create the key.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time