Who rebooted it
After an alert the on-call engineer at Acme asks who rebooted the web-02 instance last night. Memtro reads the activity log and finds a reboot by Priya Nair at 23:40, with its status and the resize she ran an hour earlier.
Ask Akamai Linode which servers run in a region, and who rebooted an instance.
Connect Akamai Linode with a personal access token and Memtro reads compute instances with plan, region, status, addresses and backups, block storage volumes, DNS domains and records, cloud firewalls and what they protect, and the activity log for the last 90 days. Billing and contact details are never returned. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can boot, reboot or shut down an instance, take a snapshot, change DNS records live, replace a firewall's rules, and permanently delete an instance with its disks.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Akamai Linode tool, reads what it needs, and answers with the source cited.
These tools change something in Akamai Linode. 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 Akamai Linode 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.
Which servers run in Frankfurt?
Who rebooted the web-01 instance this week?
Which volumes are not attached to any instance?
What are the DNS records for brightwave.co.uk?
Point the staging A record for brightwave.co.uk at the new instance
After an alert the on-call engineer at Acme asks who rebooted the web-02 instance last night. Memtro reads the activity log and finds a reboot by Priya Nair at 23:40, with its status and the resize she ran an hour earlier.
Dan Fletcher asks Memtro to point staging.brightwave.co.uk at the new web-03 instance. Memtro reads the zone's records, notes the old target so it can be set back, and changes the A record, which is live in public DNS within minutes.
The teams that lean on Akamai Linode most, a question each of them asks, and what they connect beside it.
A record in Akamai Linode 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.
In Cloud Manager open your name → API Tokens → Create a Personal Access Token, and give it a label and an expiry
Set Read Only on Linodes, Volumes, Domains, Firewalls, Events and Account and None on everything else, or Read/Write on Linodes, Domains or Firewalls for the actions you want Memtro to take. Access cannot be changed later: to change it, create a new token
Create and copy the token, then in Memtro open Connections → Akamai Linode, paste the Personal access token and connect
Ask which instances are offline, and in which region
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Akamai Linode tools are the same everywhere.
Only when you ask, and only what it has been granted: boot, reboot or shut down a Linode; rename a Linode or set its tags or watchdog; take a manual snapshot of a Linode; delete a Linode and its disks (permanent); add a DNS record to a domain; change a DNS record; delete a DNS record; add a DNS zone; rename, enable or disable a cloud firewall or set its tags; replace a cloud firewall's rules. 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.
Personal access token. In Cloud Manager open your name → API Tokens → Create a Personal Access Token, and give it a label and an expiry.
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