What changed on our product roadmap this week, and who owns it?
airfocus shows you your product workspaces with their statuses, then the items in them: features, ideas, epics, tasks and bugs. Memtro reads each item's status, assignees, description, parents and children, the comments on it, and team members by name and role. An hourly sync brings recent records into memory. When asked and granted, it can create, edit, archive or delete items and add or delete comments. It can also watch or unwatch items and move them to another workspace. The API key acts as you, with your workspace permissions, and team members' email addresses are never shown.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right airfocus tool, reads what it needs, and answers with the source cited.
These tools change something in airfocus. 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 airfocus 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.
What changed on the roadmap this week?
Which bugs are assigned to Dan Fletcher and still open?
What do the comments on DEV-123 say?
What are the child items of the onboarding epic?
Archive the old pricing experiment idea.
Maya Okafor, head of product at Northwind, asked what had changed on the roadmap this week. Memtro listed the most recently updated items with their status and assignees, and read the comments on the ones that had moved into progress.
Priya Sharma, product manager at Acme Ltd, asked Memtro to add a customer's bulk export request as an idea. With the action granted, Memtro created the item in the Ideas workspace with her description. Everyone with access to that workspace could see it.
The teams that lean on airfocus most, a question each of them asks, and what they connect beside it.
A record in airfocus 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
Scoro
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
ClockodoIn airfocus, open your name → Account settings → API keys and add a key. Choose the read scopes, plus workspace:comment or workspace only for the changes you want. Copy the key, which is shown once.
Open Connections → airfocus in Memtro and paste the API key. Set Region to us if you sign in at app.us.airfocus.com.
An administrator grants actions such as create an item or move items by name to the teams that may use them.
Ask what changed on the roadmap this week.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The airfocus tools are the same everywhere.
Only when you ask, and only what it has been granted: create an item in a workspace; edit, re-status, re-assign or archive an item; delete an item; add a comment to an item; delete a comment; watch or unwatch items; move items to another workspace. 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. An hourly sync anchors recently changed airfocus records into memory as entities.
API key. In airfocus, open your name → Account settings → API keys and add a key. Choose the read scopes, plus workspace:comment or workspace only for the changes you want. Copy the key, which is shown once.
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