Ask how many hours went into a Scoro project this month, and what is still open.
Connect Scoro with your site, the company API key and the company account id, and Memtro reads projects, tasks with assignees and planned and actual hours, task comments, time entries, contacts, people with a login, and invoices with paid and outstanding amounts. Contacts' phone numbers and addresses are never returned. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can comment on tasks, log time, create and update projects, tasks and contacts, and permanently delete a task, with its subtasks, or a time entry.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Scoro tool, reads what it needs, and answers with the source cited.
These tools change something in Scoro. 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 Scoro 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.
Scoro + MemtroHow many hours were logged on the Northwind website project this month?
Which tasks on the Acme rebrand are overdue?
Which Scoro invoices still have money outstanding?
Log 2 hours against the BigCo onboarding task for me
Move the homepage copy task to Friday and give it to Tom Hughes
The project manager asks how the Brightwave Ltd retainer is tracking. Memtro reads the project's tasks and this month's time entries: 46 hours logged against 60 planned, with most of it on two design tasks, and 8 hours not yet billed.
Priya Nair asks Memtro to move the Globex homepage copy task to Friday and hand it to Tom Hughes. Memtro changes the task's due time and owner in Scoro, where everyone who can see the task sees the change, and logs the hour Priya already spent on it in her name.
The teams that lean on Scoro most, a question each of them asks, and what they connect beside it.
A record in Scoro 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.
Clio Manage
YouTrack
Canny
Float
Productive
Smartsheet
Wrike
Financial Cents
Karbon
Kanboard
Kimai
Leantime
Acuity Scheduling
Luma
Tito
Fellow
Samsara
ServiceM8
Cliniko
Fleetio
SavvyCal
Chili Piper
Humanitix
Circleback
Aha!
Tempo
Smoobu
Semble
Airmeet
Beds24
Bookeo
Commusoft
Fergus
Fixflo
Housecall Pro
Nookal
Paymo
ProductPlan
SimplyBook.me
TimeCamp
Workiz
Guesty
Buildium
Skilljar
Runn
ClockodoOpen Scoro → Settings → External Connections → API, usually as an administrator, and copy the company API key and the Company account id beside it
The key reaches what the whole site holds. Scoro does not state which plans include API access
In Memtro open Connections → Scoro, enter the Scoro site as the part before .scoro.com (acme for acme.scoro.com), paste the API key and the Company account id, and connect
Ask how many hours went into the Northwind project this month
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Scoro tools are the same everywhere.
Only when you ask, and only what it has been granted: add a comment to a Scoro task; log a time entry against a Scoro task; change a Scoro task's name, description, status, owner, priority, dates, project or completion; create a Scoro project; change a Scoro project's name, status, manager, deadline or client; add a company or person contact in Scoro; change a Scoro contact's name, position or client and supplier flags; delete a Scoro task (and its subtasks), permanently; delete a Scoro time entry, permanently. 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.
Scoro site, API key and company account id. Open Scoro → Settings → External Connections → API, usually as an administrator, and copy the company API key and the Company account id beside it.
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