Who is booked on which project, who is free and who is away, from Float.
Connect Float with an API access token and Memtro reads people with job title and department, projects with client, budget and dates, scheduled allocations with hours per working day, logged time with totals, and time off for any period. 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 book and change allocations, log time, book time off, and create or change projects, phases, milestones, clients and people. Deleting a project or a person also permanently deletes their allocations and logged time.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Float tool, reads what it needs, and answers with the source cited.
These tools change something in Float. 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 Float 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.
Float + MemtroWho is free next week?
How booked is Priya Sharma this month, and on which projects?
Who has time off in the next fortnight?
Book Dan Fletcher on Northwind for three days next week at six hours a day
Move Priya Sharma's Acme booking to start on Wednesday
The studio lead needs two people for Brightwave Ltd from Monday. Memtro reads the next four weeks of allocations and time off, lists who has fewer than four booked hours a day, and books Priya Sharma once the lead confirms the dates.
The Acme kickoff slips by two days, and the producer, Dan Fletcher, asks Memtro to move the team's bookings. Memtro changes the start and end dates on each allocation, leaving hours and projects as they were, and the schedule everyone sees updates.
The teams that lean on Float most, a question each of them asks, and what they connect beside it.
A record in Float 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
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 Float open Account Settings → Integrations and copy the API access token, which Float shows to account owners and admins
In Memtro open Connections → Float, paste the API access token and connect, noting the token reads and schedules for the whole company
Logging time from Memtro needs Time Tracking switched on for the team in Float
Ask who is free next week, or how booked a person is this month
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Float tools are the same everywhere.
Only when you ask, and only what it has been granted: schedule a person on a Float project for a date range; create a project in Float; log time for a person on a Float project; add a client in Float; change an allocation on the Float schedule; delete an allocation from the Float schedule; change or archive a Float project; delete a Float project with its allocations and logged time; book time off in Float; delete a time-off booking in Float; change or archive a person in Float; delete a person from Float with their allocations and logged time; add a milestone to a Float project; add a phase to a Float project; rename a client in Float. 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.
API access token. In Float open Account Settings → Integrations and copy the API access token, which Float shows to account owners and admins.
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