How it works
There is no second step.
Every tracker you have abandoned died at the same place: the moment after the work, when somebody was supposed to write down that it happened. StratOps does not have that moment.
It is a connector, not an app.
StratOps runs as an MCP server — a set of tools Claude can call during a normal conversation. There is no window to switch to and no form to fill. When you describe something that happened, Claude recognises the verb in your sentence and calls the tool named for it.
That is the whole trick, and it is why this survives when a tracker does not. The record updates as a byproduct of a conversation you were having anyway, so it costs nothing extra to keep current.
You say
Just got off with Sarah at Acme. They want the pilot. I owe her a proposal by Friday.
- Meetingdated when it happened
- Contactmatched, or created
- Dealmoved, not duplicated
- Taskdue Friday, your timezone
One approval, not four.
Asking costs nothing. Changing asks first.
Every tool declares whether it can change anything, and Claude treats the two differently.
- ReadingRuns without interrupting you. Ask what is overdue, what a client has been told, how an initiative is doing — as often as you like, in the middle of anything.
- WritingPrompts once, naming what it is about to record. You see the sentence before it becomes a row.
- DeletingDoes not exist. There is no delete verb on the surface at all. Things get corrected forward, superseded, or lapsed — never removed.
Nothing is stored that could go stale.
Health, momentum, how long something has been stuck, whether throughput is rising — none of it is written down anywhere. It is worked out from the underlying rows at the moment you ask.
This matters more than it sounds. A stored score is a number that was true once. It drifts from the rows it describes, nobody notices, and eventually the dashboard and the database disagree — which is how a screen ends up showing a metric at 41 % while its actual reading is zero. Computing on read means there is only ever one answer, and it is the current one.
The same discipline runs through the interface: where a value genuinely cannot be determined, it says so rather than showing a zero. A metric that has never reported reads “no reading yet”, not “0 %”.
1
URL to paste
0
passwords typed
Three steps, once.
- Add the connectorIn Claude: Settings → Connectors → Add custom connector. Paste a URL ending in
/mcp. - Sign in with GoogleNo password is typed into StratOps and none is stored. It asks Google for a name and an email address, reads the answer once, and discards the token — it cannot reach your mail or your calendar because it never asked to.
- Start talkingPast tense, your own words. Nothing to configure first, and no empty state to fill in before it is useful.
What this does not do.
Stated here rather than discovered later.
- Nothing runs on a scheduleNo checker, no cron, no notifications. Alerts can be configured and stored faithfully, and none has ever fired on its own. Nothing arrives unprompted.
- One person per accountA second person cannot sign up. There is no invite, no seat, no sharing.
- No self-serve deploymentOne instance, in the account of the person who built it. That is what “not for sale” currently means.
- No export button yetAsk and it is done by hand, quickly. It is being built, and pretending otherwise would be the one dishonest sentence on this site.