The Setup
This workflow assumes you've completed the Claude + Keepra setup. Keepra Desktop is running, and your Claude client (Desktop, Code CLI, or Cursor) has an MCP key with tasks:read+write, notes:read+write, links:read+write, and contacts:read.
Everything described here runs locally. No data leaves your machine. Claude receives only structured JSON responses from Keepra MCP tools, not raw file access to your workspace.
Morning Standup Prep (9:00 AM)
Instead of manually opening Keepra, switching to Tasks, filtering by today, then switching to Notes to check yesterday's context:
You: "Good morning. What's on my plate today? List my tasks due today and this week,
sorted by priority. Also check if I have any notes from the past 3 days."
Claude: calls tasks:list({dueDate: "today", sort: "priority"})
calls tasks:list({dueDate: "this_week"})
calls notes:list({since: "72h"})
Claude: "Here's your morning brief:
TODAY (3 tasks):
• [High] Review PR #47 from Sarah, due 9 AM
• [Medium] Update deployment checklist
• [Medium] Reply to client proposal
THIS WEEK (5 more):
• Sprint planning prep (Wed)
• ...
RECENT NOTES (2):
• 'API rate limit issue', yesterday at 4:30 PM
• 'Client call summary, Acme Corp', 2 days ago"That's what used to be a 4-minute manual process, done in 15 seconds.
Deep Work: Research & Link Collection (10:00 AM)
While coding or researching, you encounter useful URLs, documentation, or references. Instead of interrupting your flow to switch to Keepra and manually create a bookmark:
You (in Claude Code): "Save these to my Keepra Links under 'Performance Research',
tag them 'v8,optimization':
- https://v8.dev/docs/turbofan
- https://webkit.org/blog/jsc-perf
- https://nodejs.org/en/docs/guides/perf"
Claude: calls links:create({url: ..., category: "Performance Research", tags: ["v8","optimization"]}) x3
Claude: "Saved all 3 links to Keepra under 'Performance Research' with tags v8 and optimization."You never leave your editor. The links are in Keepra for later, organized exactly how you want them.
Meeting Prep (1:55 PM)
Five minutes before a client call with "Acme Corp":
You: "I have a call with Acme Corp in 5 minutes. What do I have on them in Keepra?"
Claude: calls contacts:list({search: "Acme Corp"})
calls contacts:read({id: "..."})
calls notes:list({search: "Acme"})
Claude: "Here's your Acme Corp brief:
CONTACT: Jennifer Walsh (CTO)
• Mobile: +1-555-0192
• Email: j.walsh@acmecorp.com
• LinkedIn: linkedin.com/in/jwalsh
RECENT NOTES:
• 'Acme Corp, Sprint Review June 7' (7 days ago)
Key points: They want the dashboard MVP by July 15. Concerned about mobile performance.
• 'Acme Corp, Initial Requirements' (3 weeks ago)
Scope: React frontend, Node backend, PostgreSQL..."Everything you need, pulled from your private local workspace, in seconds. No digging through notes, no searching contacts.
Post-Meeting Action Items (3:30 PM)
Right after the meeting, while details are fresh:
You: "Meeting done. Notes: Jennifer wants to add a real-time notifications feature.
Budget approved for Q3. They want a demo by July 1st, not 15th.
Create tasks for the action items and save a meeting note."
Claude: calls notes:create({
title: "Acme Corp, Call June 14 2026",
content: "## Summary\nJennifer confirmed Q3 budget. Timeline moved up: demo July 1.\n\n## New Scope\n- Real-time notifications (WebSocket)\n- Mobile-first redesign priority\n\n## Action Items\n- Design WebSocket architecture (due June 16)\n- Update project timeline (due June 15)\n- Send revised proposal email (due tomorrow)"
})
calls tasks:create({title: "Design WebSocket architecture for Acme", dueDate: "2026-06-16", priority: "high"})
calls tasks:create({title: "Update Acme project timeline", dueDate: "2026-06-15", priority: "high"})
calls tasks:create({title: "Send revised proposal to Jennifer Walsh", dueDate: "2026-06-15", priority: "medium"})
Claude: "Created meeting note 'Acme Corp, Call June 14 2026' and 3 tasks:
• [High] Design WebSocket architecture, due Mon Jun 16
• [High] Update Acme project timeline, due Sun Jun 15
• [Medium] Send revised proposal to Jennifer Walsh, due Sun Jun 15"End-of-Day Review (6:00 PM)
You: "What did I complete today? And are there any overdue tasks I should know about?"
Claude: calls tasks:list({completed: true, completedSince: "today"})
calls tasks:list({overdue: true})
Claude: "Today you completed 4 tasks... You have 1 overdue item: 'Update team wiki'
from 3 days ago. Want me to reschedule it to tomorrow?"The Security Model, What Claude Can't Do
This is the critical safety layer. No matter what you tell Claude:
- Claude cannot read your vault passwords or API keys without explicit per-item grants in Settings → AI Access
- Claude cannot access vault:read_item unless that specific scope was granted for that specific vault item
- vault:list_titles shows Claude only the names of credentials (like "AWS Production Key"), not the values
- Revoking an MCP key instantly removes all Claude access, no shared secrets to rotate
vault:read_item access to any AI client unless you have a very specific use case (like letting Claude auto-fill a CI/CD token that you explicitly approved). Default: AI can list vault item titles only.
vs. Linear, Jira, Notion AI
| Feature | Linear + AI | Notion AI | Jira + Copilot | Claude + Keepra |
|---|---|---|---|---|
| Data leaves device? | ✗ Yes (cloud) | ✗ Yes (cloud) | ✗ Yes (cloud) | ✓ No (local) |
| Vault/cred integration | ✗ No | ✗ No | ✗ No | ✓ Yes (scoped) |
| Cross-tool context | ✗ Tasks only | ⚬ Notion only | ✗ Issues only | ✓ Tasks+Notes+Links+Contacts |
| Works offline | ✗ No | ✗ No | ✗ No | ✓ Yes |
| Open standard (MCP) | ✗ No | ✗ No | ✗ No | ✓ Yes |
| Monthly cost | $8+/user | $10+/user | $8.15+/user | $0–$2.50/mo |
For setup instructions, see the Claude + Keepra setup guide. For the MCP architecture, see What is MCP?.