Resources
Start with the how-tos if you are setting something up: one page per thing you might connect. Then a group on recording and consent, from what to say before you start to what the law requires where you work; free templates for writing up the meetings a working week is made of; and the longer guides, in three groups. The first is about the meetings themselves, how to run them and how a group decides in them. The second is about the week around them, where the hours go and how work gets prioritised. The third is about what survives the week, how to organise and query what you learn. Written to be useful on their own.
Docs and how-tos
One page per thing you might connect: the calendar guides cover the four ways to get your meetings marked automatically, the MCP guides cover reading your meeting history from the tools you already work in, and the agent guides cover getting each of the ten built-in agents running inside the app.
Connect a calendar
Connect one and every event on your day can become a named meeting on its own. Four ways in, and the last one exists because the first three can be refused by an employer. What an automatic span is, and what happens when the meeting doesn't match the invite, is on calendar connection.
- Apple Calendar: one permission prompt, no account, and every calendar already on your Mac.
- Google Calendar: sign in through your browser, read-only.
- Microsoft Outlook: the same, for a work or personal Microsoft account.
- A calendar link (ICS): paste a published address. No account, nothing for IT to approve.
Connect an app over MCP
Earkeep runs a small MCP server so other tools on your machine can search and read your saved meetings. It listens on loopback only, and it is read-only: nothing connected here can change a meeting. The app's own Connect apps panel gives you the same commands with your real address already filled in.
- Claude Code: one terminal command, connects directly.
- Claude Desktop: the one client that needs a bridge.
- Codex CLI: one terminal command.
- Codex in your IDE: one entry in the config it shares with the CLI.
- Cursor: one JSON entry, globally or per project.
Set up an agent
The other direction: an agent running inside Earkeep, against the meeting you are looking at. You install the agent yourself and it runs on your own account, which is why there is no inference cost in the price of the app. Each of these covers installing it, signing in, and confirming Earkeep can see it. The wider argument is on agents and MCP.
Earkeep integrates with the Agent Client Protocol, not with ten separate agents, so anything else that speaks it can be added with Add custom agent in Settings → Agents, including agents that don't exist yet.
Recording, consent and the law
Earkeep announces itself to nobody, so telling the room is yours to do. One page on how to say it in a sentence and on the three ways to stop when somebody would rather you didn't, and two references on what the law actually requires where you and the people you meet are sitting.
- Telling people you're recording: what to say before the meeting starts, why a written banner may not be enough, and how pausing, never-record meetings and purging work.
- US recording laws, state by state: the federal baseline, why the published one-party and all-party counts disagree with each other, and a page for every state and DC.
- European recording laws: the four layers, who the controller is, the household exemption and why it does not save you, notice scripts in five languages, and a page for all 32 countries.
Legal information, not legal advice: every entry summarises a statute without replacing it, cites its sources, and says so where the sources disagree.
Meeting templates
A free template for each of the meetings a working week is actually made of, complete and on the page with nothing to sign up for. The meeting minutes template hub has the general-purpose frame that all of them vary, what a record has to contain whatever the layout, and the meetings too small for a page of their own, from design reviews to postmortems. Each page below also covers the part a template does not solve, which is who fills it in twenty minutes after the meeting while the next one is starting. For how to run these meetings instead of how to record them, see the group after this one.
- One-on-one meeting agenda template: the thread across months, and the block that keeps part of it out of the file.
- Team meeting agenda template: with a bucket for the blocker everybody nodded at and nobody took.
- Staff meeting agenda template: escalations with a status, and what you committed to upward.
- Project kickoff meeting agenda template: the out-of-scope list that is the only part anyone argues about later.
- Agile ceremony templates: daily scrum, sprint planning, review, retrospective and refinement, on one page.
- Strategic planning meeting agenda template: planning, OKRs and offsites, with the options you rejected and why.
- Project status meeting agenda template: a date-change log, and approvals in the words the approver used.
- All-hands meeting agenda template: the Q&A split into asked, answered, and still owed.
Running better meetings
Where the templates above are the blank to fill in, these are the argument: which meetings should exist, how to run the ones that should, how a group actually reaches a decision, and the interviewing craft the good ones run on.
- Meeting overload: 23 hours a week and how to stop
- Standup and retrospective formats that work
- Kickoff meetings: the agenda that prevents rework
- Skip-level meetings: what they are for, and how they go wrong
- Collaborative decision making: who decides, and how
- Decision log: the record of why, not just what
- Action items: what they are and how to write them
- Open-ended questions: what they do, and when to close
- Establishing rapport: what the research actually says
- Empathic listening: the orientation, not the technique
- Debrief: how to run one that changes the next time
- Cross-functional collaboration: where it breaks
Time management
Where the hours go and how to spend them deliberately, from the scheduling mechanics of a single day to the frameworks whole teams run on.
- Time blocking and timeboxing, two sides of one coin
- Time audit: how to find where your week actually goes
- Energy management: why to manage energy, not time
- The Eisenhower Matrix and the Pareto principle
- MoSCoW and RICE: prioritisation for product managers
- Ivy Lee, Eat the Frog and ABCDE: three daily methods
- Flow, deep work and the three enemies of focus
- Getting Things Done: a complete guide to GTD
- Pomodoro and Atomic Habits: focus and habits
- Agile, Scrum and Kanban: which one to choose
- Lean Six Sigma, CPM and PERT explained
- OKR and SMART: goals that survive the quarter
- Task and project management tools: a buyer's guide
- AI scheduling and time tracking tools in 2026
- Digital minimalism: fewer tools, better results
Knowledge management
Building a second brain: the methods that have held up, the tools that implement them, and what changes once a model can read your notes.
- Zettelkasten and evergreen notes
- PARA and CODE, filing notes by actionability
- LYT and maps of content, structure you discover
- Johnny Decimal and digital gardening, order and audience
- Obsidian vs Logseq vs SiYuan: how to choose
- PKM for developers: Dendron and Foam in VS Code
- Zettlr, Joplin, Anytype and AppFlowy compared
- The LLM Wiki: compiling knowledge, not retrieving it
- Local RAG in practice: Ollama, a vector store, a model
- AI-enhanced PKM and agent memory
- From what was said to what you know