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 the 7 servers and 5 skills are listed one by one. Every member is free, so the checkout lists them and asks for no card.
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 what the assistant should know about a project with the Agent Memory skill, so it is not 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.
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 free, so the monthly figure is $0 whatever you do with the stack: nothing here is billed by the call, and only adding a paid member could change it.
| Part | What you are paying for | Monthly, as quoted |
|---|---|---|
| Notion | Free | — |
| Obsidian | Free | — |
| Todoist (official) | Free | — |
| Google Calendar | Free | — |
| Gmail | Free | — |
| Weather | Free | — |
| Google Maps | Free | — |
| Skills | ||
| Second Brain | Free · context cost only | — |
| Agent Memory | Free · context cost only | — |
| File Organizer (PARA) | Free · context cost only | — |
| agent-email-inbox | Free · context cost only | — |
| Deep Research | Free · context cost only | — |
| Everything above | $0 of servers plus $0 of skills, the same in a quiet month and a busy one | $0/mo |
Subscriptions at their monthly plan price; one-off licences spread over 12 months.
Install only these and the bill is nothing: 7 servers and 5 skills, and all 59 tools.
Nothing in this stack carries a call allowance, so nothing here can run out before the month does. The bill is decided when you install it, not when you use it.
The spend cap is one figure for the whole account, set in your dashboard and checked when an order is placed. On the call path what stops a retry loop is the plan's call allowance and its rate limit, and a refused call is never billed.
The steps below come before the install lines: what to decide and scope before connecting anything, in the order it matters. The lines themselves follow, part by part, for the client you pick.
npx mcprush@latest stack add second-brain writes all 7 servers into Claude Code’s config in one go — or run the lines below one by one. The 5 skills are not included — add them with lines 08–12.
NOTION_API_TOKEN — Notion integration token (notion.so/my-integrations)VAULT_DIR_PATH — Absolute path to your Obsidian vault folderTODOIST_API_KEY — Your Todoist API token (Settings → Integrations → Developer)GOOGLE_OAUTH_CREDENTIALS — Path to your OAuth client file gcp-oauth.keys.json (Google Cloud → Credentials → OAuth client, Desktop app)GOOGLE_MAPS_API_KEY — Google Maps API key (get one at https://console.cloud.google.com)Set them where you start Claude Code — export NOTION_API_TOKEN=… in your shell profile on macOS and Linux, setx NOTION_API_TOKEN "…" on Windows, then open a new terminal. Claude Code reads them at start; the config keeps only the names.
Gmail needs one step before it answers — run this once, on its own:
npx -y @klodr/gmail-mcp auth# 01 · Notion
claude mcp add --scope user --env 'NOTION_API_TOKEN=${NOTION_API_TOKEN}' --transport stdio notion-mcp '--' npx -y @suekou/mcp-notion-server
# 02 · Obsidian
claude mcp add --scope user --env 'VAULT_DIR_PATH=${VAULT_DIR_PATH}' --transport stdio obsidian-mcp '--' npx -y @sunub/obsidian-mcp-server
# 03 · Todoist (official)
claude mcp add --scope user --env 'TODOIST_API_KEY=${TODOIST_API_KEY}' --transport stdio todoist-official-mcp '--' npx -y @doist/todoist-mcp
# 04 · Google Calendar
claude mcp add --scope user --env 'GOOGLE_OAUTH_CREDENTIALS=${GOOGLE_OAUTH_CREDENTIALS}' --transport stdio google-calendar-mcp '--' npx -y @cocal/google-calendar-mcp
# 05 · Gmail
claude mcp add --scope user gmail-mcp '--' npx -y @klodr/gmail-mcp
# 06 · Weather
claude mcp add --scope user weather-mcp '--' npx -y @dangahagan/weather-mcp
# 07 · Google Maps
claude mcp add --scope user --env 'GOOGLE_MAPS_API_KEY=${GOOGLE_MAPS_API_KEY}' --transport stdio google-maps-mcp '--' npx -y @cablate/mcp-google-map --stdio
# 08 · Second Brain
npx mcprush@latest skill add sean-esk/second-brain
# 09 · Agent Memory
npx mcprush@latest skill add terminalskills/agent-memory
# 10 · File Organizer (PARA)
npx mcprush@latest skill add smithjoshua/file-organizer-para
# 11 · agent-email-inbox
npx mcprush@latest skill add resend/agent-email-inbox
# 12 · Deep Research
npx mcprush@latest skill add lingzhi227/deep-researchnpx).Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.Nothing is connected until you approve it in Claude Code. mcprush is not in the path and meters nothing here.
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 | imported | 22 |
| Obsidian | imported | 2 |
| Weather | imported | 2 |
| Google Calendar | imported | 1 |
| Google Maps | not imported | not recorded |
| Notion | not imported | not recorded |
| Todoist (official) | 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 3 members of 7 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.
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 the ticket, the thread and the source into a page somebody can follow, in the words your product already uses.