One place for the notes, the tasks, the calendar and the inbox, with a memory that survives the session.
Built for: Anyone whose system is four apps and the belief that they will remember which one has the thing.
The button opens the checkout, where 8 servers and 5 skills are listed one by one with what each does to the bill — free, already yours, monthly or a one-off licence. Nothing is charged until you confirm it there, in Stripe’s own card frame on that page rather than a redirect, and each paid member keeps its own budget cap.
The reason to buy a stack rather than five listings: each line below needs more than one member connected at the same time.
Capture into Notion or Obsidian, and turn the capture into a Todoist task with a date rather than a note about a task.
Read the calendar and the inbox together, so the plan for tomorrow accounts for what is already in it.
Keep persistent memory across sessions, so the assistant knows the project without being told again each morning.
File what arrives — documents, notes, exports — into a structure that stays legible a year later.
What each part contributes, and why it was picked over the obvious alternative. Prices and permissions are read from the listings, so nothing here can disagree with the catalogue.
The workspace most of this already lives in, connected properly instead of through copy and paste.
The local-markdown alternative, for people whose notes should outlive any company's servers.
Doist's own server for the task list, so a capture becomes something with a date rather than a paragraph you will find later.
Persistent entities and relations across sessions — the difference between an assistant and a fresh conversation every morning.
The commitments that already exist, which is what makes a plan for tomorrow honest.
Scope-gated inbox access with attachment path jails, which is the version of this worth granting to a personal assistant.
Seventeen weather tools with no API key, for the plans that are actually decided by whether it rains.
Geocoding, places and directions for the errands and travel half of a personal system.
The method behind the tools — capture, organise, review — combining GTD, Zettelkasten and PARA rather than inventing a fourth system.
Sets up memory that survives between sessions deliberately, instead of a context window that grows until it is trimmed.
Files what lands on your disk into Projects, Areas, Resources and Archive, which is the part everyone skips and then regrets.
For turning mail into actions — the pattern behind an inbox that triages itself rather than one that is read twice.
Six-phase deep reading for the personal question that deserves more than a search: a structured note set and a synthesis at the end.
Every member is a subscription or a licence bought once, so the monthly figure is a price rather than an estimate: what moves it is adding or dropping a member, not how hard the stack is worked. The one assumption is that a one-off licence is spread over a year so it can sit in the same column as a subscription.
| Part | What you are paying for | Monthly, as quoted |
|---|---|---|
| Notion | Free | — |
| Obsidian | Free | — |
| Todoist (official) | Free | — |
| Memory (official) | Free | — |
| Google Calendar | Free | — |
| Gmail | from $15/mo | $15/mo |
| Weather | Free | — |
| Google Maps (official) | Free | — |
| Skills | ||
| Second Brain | Free · context cost only | — |
| Agent Memory | $59 · $4.92/mo over 12 months | $4.92/mo |
| File Organizer (PARA) | $35 · $2.92/mo over 12 months | $2.92/mo |
| agent-email-inbox | $59 · $4.92/mo over 12 months | $4.92/mo |
| Deep Research | Free · context cost only | — |
| Everything above | $15 of servers plus $13 of skills, the same in a quiet month and a busy one | $28/mo |
Subscriptions at their monthly plan price; one-off licences spread over 12 months. One-off purchases in this stack total $153 — Agent Memory $59, File Organizer (PARA) $35, agent-email-inbox $59 — paid once and spread here so they sit in the same column as a subscription. Everything arrives on one mcprush invoice, taken by Stripe from the card on your account, not one per publisher — mcprush.com is the merchant of record and each publisher is paid out of it.
Install only these and the bill is nothing: 7 servers and 2 skills.
Left out, and what goes with it:
Gmail at from $15/mo. Each of those plans states the calls it includes in a month, and running past one never arrives as a larger invoice: the gateway refuses the call over the allowance and returns an MCP error naming the plan. The figure above is what the stack costs in a busy month as well as a quiet one — what a heavy month changes is which plan you need, not what this one bills.
Budget caps are set per install and enforced at the gateway, so a retry loop is refused at the cap rather than left to run through an allowance overnight.
One step per part, in the order they are useful: connect what the work reads before what it writes, and install the skills that decide how the work is done last. Each step is a command you can read before you run it.
npx mcprush@latest stack add second-brainNothing in this stack installs from one command today: 13 members are either paid, run from its own source, or a skill with its own command — the steps above name each one. Nothing is connected until you approve it.
Installed together, these tool surfaces add up. It is the first thing a security reviewer asks for, so what has been counted — and what nobody has counted yet — is on the page rather than in a PDF.
| Member | Tool surface | Write tools |
|---|---|---|
| Gmail | not imported | not recorded |
| Google Calendar | not imported | not recorded |
| Google Maps (official) | not imported | not recorded |
| Memory (official) | not imported | not recorded |
| Notion | not imported | not recorded |
| Obsidian | not imported | not recorded |
| Todoist (official) | not imported | not recorded |
| Weather | not imported | not recorded |
A stack's blast radius is the union of its members, not the worst of them. That union cannot be taken here, because 8 members of 8 have no imported tool surface — so the figure a review asks for is missing rather than low, and a member marked not imported is one nobody has counted rather than one that cannot write.
A stack is a default, not a verdict. These are the substitutions the maintainer would make, and what each one costs or saves.
The same read-and-draft loop for a Microsoft household, with the calendar arriving from the same account instead of a second one.
For people who think in boards rather than in lists; the capture step is identical and the review step looks completely different.
Written by the maintainer, kept on the page rather than in a support thread.
It cannot send email for you unless you allow it to. Read and draft is the default here, and it should stay the default.
It does not replace judgement about priority. It can order a list; deciding what actually matters this week is not a tool's job.
Everything here is personal data by definition. Every credential should be your own, scoped narrowly, and revocable in one place.
A stack has an owner: whoever keeps it re-checks the combination when a member changes, and the members themselves are published by the people named on each row.
Researches the account, writes the sequence, keeps the CRM current, and books the meeting without four tabs.
Reads the ticket, finds whether it is a bug or a billing question, and drafts the reply in your own voice.
Turns a bug report into a reproduction that fails, before anybody writes a line of the fix.