01
Write the runbook
Give it a name, an owner and the steps, with notes and links where they help. Choose a cadence (every 90 days) or an expiry date for things like API keys. One runbook per chore; the team can read all of them.
Product · Runbooks
Runbooks: recurring chores with an owner, a date and a record.
Key rotations, backup drills, server updates, certificate renewals. Write the steps once. OpsMinder reminds the owner when a run is due and keeps a record of each one.
Rotate prod-db keyRUN #8 · DUE THU
ownerj.bergcadenceevery 90 dayslast run#7 · 86 days ago · m.vos
STEPS
Create a new key in the AWS console (link)
Update DB_KEY in the payments and api services
Check the dashboards for 10 minutes, then revoke the old key
How it works
A runbook is the chore. A run is one time you did it.
nameRotate prod-db keyownerj.bergscheduleevery 90 daysremind7 days before · #opssteps3
02
The owner gets a reminder
A week before the run is due, a message goes to the channel you picked: Slack, Teams, a webhook or email. It carries the steps and the buttons to act on it. If the run goes overdue, the team is told too.
Rotate prod-db key is due Thursday. Last done 86 days ago by m.vos. Assigned to j.berg.
Open stepsMark doneSnooze
03
Do the run, say what you did
Follow the steps and mark the run done from the message button, the web app, the API or by replying to the email. Add a comment so the next person knows what happened. Every run keeps who, when and the comments.
Run #8done · Thu 15:12 · j.berg
JBRotated via the console. Old key revoked at 15:10, dashboards quiet.
MVThanks. Added the staging key to this runbook for next time.
04
The next run is scheduled
Completing a run schedules the next one. By default it follows the cadence. When the date depends on something else, such as a key that expires in 30 days, pick it here. The runbook is never without a next date.
NEXT RUN
MCP server
Your AI agent can read the runbook and do the run with you.
OpsMinder exposes runbooks over MCP. An agent in your editor or terminal can list what is due, read the steps and notes, carry out the parts it has access to, and ask you for the parts it doesn't, such as a console login or a final check.
When the run is done, the agent marks it complete and writes the comment: what it did, what you did, and anything the next person should know.
list_due_runsget_runbookcomplete_runschedule_next
JBWhat's due this week?
One run: Rotate prod-db key, due Thursday. Three steps. I can create the new key and update the two services. You'll need to revoke the old one in the console after we check the dashboards. Start?JBGo ahead.
New key created. DB_KEY updated in payments and api, both healthy. Step 3 is yours: revoke key AKIA…7Q in the console. Tell me when it's done and I'll close the run.JBRevoked.
Run #8 marked done with a comment. Next run scheduled for 4 Jan 2027.Marking a run done
From wherever the reminder found you.
Message button
Mark done or snooze from the Slack or Teams message.
Web app
Tick the steps, write the comment, pick the next date.
API or webhook
Let the script that did the work report it. POST /runs/8/complete
Email reply
Reply "done" to the reminder. The reply body becomes the comment.
MCP
An agent does the run with you and closes it with a comment.
Start with the chore you forget most.
Free for one developer. €1 per seat a month after that.