AI / MCPDeveloper

Claude + Keepra: The Ultimate AI Productivity Setup Guide (2026)

Install Keepra, create an MCP key, configure Claude Desktop or Claude Code CLI, and give your AI assistant real access to your tasks, notes, and links, all locally, in under 5 minutes.

Prerequisites

Before starting, you need:

  • Keepra Desktop: download from keepra.app (Windows installer or run from source with Electron)
  • Claude Desktop or Claude Code CLI: download from claude.ai/download
  • Node.js: v18+ (required to run the MCP server subprocess)
Important: Keepra Desktop must be running whenever you want Claude to access your data. The MCP server is a subprocess that runs locally, it requires the Keepra app to be open and the embedded http server to be live.

Step 1: Launch Keepra Desktop

Run launch-electron.bat (Windows) or launch the Electron app directly. The app will start at http://localhost (the embedded server). Verify it loads correctly before proceeding.

If you're starting from scratch, Keepra will seed example data automatically. You can delete it later.

Step 2: Create an MCP Key in Settings

  1. Open Keepra and click the settings gear icon (top right) or press Ctrl+,
  2. Navigate to the AI Access (MCP) tab
  3. Click + Create New Key
  4. Give it a name like "Claude Desktop" or "Claude Code"
  5. Select the tools you want this key to access (see Step 3)
  6. Click Generate: copy the key immediately (it won't be shown again in full)

Step 3: Choose Your Permission Scopes

MCP keys in Keepra have per-tool scopes. Here are recommended configurations:

Use CaseRecommended ScopesRationale
Daily assistanttasks:read+write, notes:read, links:readCan create tasks, read notes and links. Can't write notes or create links.
Full productivityAll tools except vaultClaude can manage your full workspace except passwords.
Read-only researcherAll tools, read-onlyClaude can answer questions from your data but can't modify anything.
Vault accessvault:list_titles + per-item grantClaude sees titles only; you explicitly grant access to specific items.
Recommendation: Start with tasks:read+write and notes:read. Add more scopes as you discover use cases. You can always create additional keys with different permission sets.

Step 4a: Configure Claude Desktop

Claude Desktop reads its MCP server configuration from a JSON file. The location depends on your OS:

  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Open (or create) this file and add the Keepra MCP server:

{
  "mcpServers": {
    "keepra": {
      "command": "node",
      "args": ["C:\\Keepra\\keepra-mcp.js"],
      "env": {
        "KEEPRA_MCP_KEY": "your-generated-key-here"
      }
    }
  }
}

Replace your-generated-key-here with the key from Step 2. On macOS/Linux, use the appropriate path to keepra-mcp.js. Restart Claude Desktop after saving.

Step 4b: Configure Claude Code (CLI)

If you use Claude Code (the CLI tool), add Keepra via the /mcp add command:

# In your terminal with Claude Code active:
/mcp add keepra node /path/to/keepra-mcp.js

# Or add it to your project's .mcp.json:
{
  "mcpServers": {
    "keepra": {
      "command": "node",
      "args": ["/path/to/keepra-mcp.js"],
      "env": { "KEEPRA_MCP_KEY": "your-key" }
    }
  }
}

Step 4c: Configure Cursor IDE

Add a .cursor/mcp.json file in your project root or in ~/.cursor/mcp.json globally:

{
  "mcpServers": {
    "keepra": {
      "command": "node",
      "args": ["C:\\Keepra\\keepra-mcp.js"],
      "env": {
        "KEEPRA_MCP_KEY": "your-key-here"
      }
    }
  }
}

Step 5: Test with Your First Command

With Keepra Desktop running and Claude configured, try these commands to verify the integration:

# Create a task:
"Add a task called 'Review the PR' due tomorrow with high priority"

# Read your notes:
"What are my most recent notes in Keepra?"

# Find a contact:
"Find John Smith in my Keepra contacts and tell me his email address"

# Save a link:
"Save this URL to my Keepra Links under the 'Work' category: https://docs.example.com"

Claude will call the appropriate MCP tools, Keepra will execute them locally, and you'll see the results both in Claude's response and in your Keepra app (after a refresh if needed).

Real-World Use Cases

Morning Standup Prep

"Claude, list all my tasks due today and this week, grouped by priority. Also check if I have any notes from recent meetings."

Meeting Notes → Action Items

"I just had a meeting. Here are my rough notes: [paste notes]. Create a Keepra note called 'Sprint Planning 2026-06-14' with these notes, and create tasks for each action item you identify."

Client Research

"I'm about to call Acme Corp. Look up their contact in Keepra and tell me everything I have on them, phones, emails, notes."

Link Collection

"Save all these research links to Keepra under the category 'AI Research' with tag 'MCP': [list of URLs]"

Security Best Practices

  • Never grant Vault write access: Claude cannot add new credentials; you should always do this manually
  • Use separate keys for different clients, one for Claude Desktop, one for Cursor, so you can revoke independently
  • Review the MCP key list regularly in Settings → AI Access, delete keys you no longer use
  • Don't share your MCP key: it's equivalent to granting read/write access to your Keepra data

For a deeper technical explanation of MCP architecture, see What is MCP?. For the full developer AI workflow, read The Developer's AI Workflow.

Keepra Team

Keepra

Built the Keepra MCP server. Uses Claude + Keepra daily for task management and meeting prep.

Ready to give Claude access to your workspace?

Keepra Desktop + MCP, local-only, scoped permissions. Setup takes 5 minutes.