Google Keep MCP Server

A Model Context Protocol (MCP) server that connects Google Keep to Claude, giving it full note management capabilities.

Uses the unofficial gkeepapi library — the only viable way to access Google Keep programmatically.

Features

20 tools across 5 categories:

Related MCP server: Claude MCP x Google Docs

Setup

1. Install

make install

2. Get a Google Master Token

Google no longer allows programmatic login. You need to extract a token from a browser session:

1. Open Chrome and go to https://accounts.google.com/EmbeddedSetup

2. Sign in with your Google account and click "I agree" (the page may show a loading screen forever — that's OK)

3. Open DevTools (Cmd+Option+I on Mac, F12 on Windows/Linux)

4. Go to Application > Cookies > accounts.google.com

5. Find the cookie named oauth_token and copy its value (starts with oauth2_4/...)

6. Run the helper script immediately (the token is single-use and short-lived):

uv run python scripts/get_token.py

The master token it returns does not expire. You only need to do this once.

3. Configure Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "google-keep": {
      "command": "/path/to/uv",
      "args": ["--directory", "/path/to/Google Keep MCP", "run", "keep-mcp"],
      "env": {
        "GOOGLE_EMAIL": "you@gmail.com",
        "GOOGLE_MASTER_TOKEN": "aas_et/..."
      }
    }
  }
}

Use the full path to uv (run which uv to find it). Claude Desktop doesn't inherit your shell PATH.

Restart Claude Desktop after saving.

Safety

By default, write operations only work on notes that have a keep-mcp label. Notes created through the server get this label automatically.

This prevents Claude from accidentally modifying your existing notes.

To allow modifications to all notes, add to the env:

"UNSAFE_MODE": "true"

Additional safety gates:

• delete_note (permanent delete) requires UNSAFE_MODE=true

• delete_label (globally destructive) requires UNSAFE_MODE=true

• trash_note is always available as a safe, reversible alternative

Development

make install      # install dependencies
make start        # run server (stdio)
make start-sse    # run server (SSE for remote use)
make test         # run unit tests
make smoke        # run integration tests (needs credentials)
make lint         # check code style
make format       # auto-fix code style

Environment Variables