Skip to main content
Glama
google-keep-mcp
by orssdev

google-keep-mcp

An MCP server that exposes Google Keep notes as tools, so an MCP client (Claude Code, Claude Desktop, etc.) can work with them.

Google Keep has no official public API. This project talks to Keep through gkeepapi, an unofficial client — expect it to break whenever Google changes the private endpoints.

Tools

Tool

Does

list_notes

Search the account's notes. Filters: query, labels, pinned, archived, trashed, limit. Returns id, title, text, labels, color, timestamps and the Keep URL for each match.

delete_note

Move a note to the trash by id, or delete it outright with permanent: true.

Both tools sync with Google on every call, so results reflect the account's current state and deletions are pushed immediately.

Related MCP server: NotesKeep MCP Server

Requirements

  • Python 3.13+

  • uv

Setup

uv sync
cp .env.example .env   # then fill in your credentials

Credentials

gkeepapi authenticates with a Google master token, not your password. Obtain one once (see the gkeepapi docs), then set GOOGLE_KEEP_EMAIL and GOOGLE_KEEP_MASTER_TOKEN — see .env.example.

A master token grants full access to the account. Treat it like a password: keep it out of version control and out of shell history.

Running

The server speaks MCP over stdio:

uv run google-keep-mcp

Register it with a client — for Claude Code:

claude mcp add google-keep -- uv run --directory /path/to/google-keep-mcp google-keep-mcp

Credentials are read from the process environment, falling back to a .env file in the working directory. To pass them through the client config instead, add --env GOOGLE_KEEP_EMAIL=... --env GOOGLE_KEEP_MASTER_TOKEN=... to the command above. Sign-in is deferred until the first tool call, so a misconfigured server still starts and reports the problem in the tool result.

Development

uv run ruff check .      # lint
uv run ruff format .     # format
uv run pytest            # tests

License

MIT — see LICENSE.

Available Tools

2 tools
delete_noteDelete noteA
DestructiveIdempotent

Move a Google Keep note to the trash, or delete it permanently.

Inputs: note_id (required), permanent. Returns: Confirmation that a note was removed.

list_notesList notesA
Read-only

Search the Google Keep account and return the matching notes.

Inputs: limit, query, labels, pinned, +2 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    list_notes and delete_note target completely distinct actions with no overlap. An agent can easily choose the right tool based on the operation needed.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (list_notes, delete_note). The naming is predictable and uniform.

    Tool Count3/5

    With only 2 tools, the server feels thin for a Google Keep integration. The count is borderline but not absurdly small.

    Completeness2/5

    The surface lacks essential operations like creating, updating, or fetching a single note by ID. Only list and delete are supported, leaving significant workflow gaps.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables interaction with Google Keep notes through an MCP server, allowing users to search, create, update, and delete notes via natural language commands.
      23
      532 PyPI
      114
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Enables users to manage their notes on NotesKeep directly through Claude Code or other MCP clients. It supports creating, updating, and organizing both text and checklist notes using natural language commands.
      14
      15 npm
      1
      MIT