Keep MCP logo

Keep MCP

by feuerdev

Manage Google Keep notes, lists, labels, collaborators, and media through MCP tools.

Install Keep MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "feuerdev-keep-mcp": {
      "command": "uvx",
      "args": [
        "keep-mcp"
      ],
      "env": {
        "GOOGLE_EMAIL": "YOUR_VALUE_HERE",
        "GOOGLE_MASTER_TOKEN": "YOUR_VALUE_HERE",
        "UNSAFE_MODE": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

feuerdev/keep-mcp MCP server connects MCP clients to Google Keep for reading, creating, updating, and deleting notes. It runs through pipx, uvx, or a local checkout and authenticates with a Google email address and master token. Tools cover note search, checklists, labels, collaborators, media, and note state such as pinned, archived, or trashed. Reach for it when an agent needs controlled access to Google Keep, with modifications restricted by default to notes created by the server.

Use cases

  • Search Google Keep notes by text and metadata
  • Create notes and checklist items from an MCP client
  • Organize notes with labels, colors, pins, and archives
  • Manage note collaborators and attached media
  • Restore or delete notes through controlled operations

Key features

  • Search and retrieve Google Keep notes
  • Create and update notes and checklists
  • Manage labels, collaborators, and media
  • Pin, archive, trash, restore, and delete notes
  • Restrict modifications to server-created notes by default

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 80d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · keep-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars108Stargazers on the source repository.
Last commit22d agoMost recent push to the default branch.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Keep MCP works

What feuerdev/keep-mcp MCP server does

The feuerdev/keep-mcp MCP server exposes Google Keep operations as MCP tools. It can search notes, retrieve a note by ID, create regular notes and checklists, edit note or checklist content, and manage note lifecycle state. It also supports labels, collaborators, and media associated with notes.

The server is listed in the Workplace & Productivity category and fits workflows where an MCP-compatible client needs to find or maintain Google Keep content. New notes created through the server automatically receive the keep-mcp label, which is also used as a safety boundary for later modifications.

Tools and capabilities

Search and retrieval include case-insensitive text search by default, optional label, color, pin, archive, trash, and ISO 8601 UTC date filters, plus a result limit. A separate tool retrieves one note by ID.

Creation and editing tools handle note titles and text, checklist creation, checklist item insertion, item text and checked-state updates, and item deletion. Note-state operations can set colors, pin or unpin notes, archive or unarchive them, move them to trash, restore them, or mark them for deletion.

Additional tools list, create, delete, add, and remove labels. Collaborator tools list collaborator email addresses and add or remove collaborators. Media tools list media blobs and links, then download images, drawings, or audio to a local directory through the authenticated session.

How it works

feuerdev/keep-mcp MCP server uses gkeepapi to communicate with Google Keep through an unofficial private API. MCP clients start the server as a local stdio process, using either the published package through pipx or uvx, or a local checkout through make or uv.

By default, modification and destructive operations apply only to notes carrying the keep-mcp label. Setting UNSAFE_MODE to true bypasses that restriction and allows operations on other notes as well.

Setup and configuration

Configure the server with GOOGLE_EMAIL and GOOGLE_MASTER_TOKEN. A JSON MCP configuration can run keep-mcp with uvx or pipx; local development can use make install followed by the repository's make start target. The client configuration must provide the repository path when using a local checkout, and make and uv must be available in PATH.

The master token is obtained through the browser-assisted exchange described by gpsoauth, using either its local Python flow or the Docker-based instructions from gkeepapi. The exchange requires a browser oauth_token. Older password-based instructions are not recommended because that login flow can fail with BadAuthentication.

Limitations and notes

The Google Keep connection relies on an unofficial private API rather than an official Google Keep API. The master token grants full access to the Google account, so it should be treated like a password and never committed or shared. Media links may return HTTP 403 to unauthenticated clients; use the server's authenticated download operation instead.

The repository provides unit tests with mocked Keep objects and a separate smoke test for a real account. The smoke test performs a note lifecycle including creation, editing, pinning, archiving, trashing, restoration, and deletion, so it should use a dedicated test account.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Keep MCP

feuerdev/keep-mcp is an MCP server that connects MCP clients to Google Keep through gkeepapi and an unofficial private API. Its main tools search and read notes, create and update notes and checklists, manage labels and collaborators, handle media, and change note state such as pinning, archiving, trashing, and restoration.

Run it through `pipx` or `uvx` in your MCP client configuration. Set the command to `pipx` with `run keep-mcp`, or to `uvx` with `keep-mcp`, then provide `GOOGLE_EMAIL` and `GOOGLE_MASTER_TOKEN`. A local checkout can be started with `make start` after `make install`.

It requires `GOOGLE_EMAIL` and `GOOGLE_MASTER_TOKEN`. Obtain the master token with the browser-assisted `gpsoauth` exchange, using either its local Python flow or the Docker instructions from `gkeepapi`. Treat the token like a password because it has full Google account access.

Yes, feuerdev/keep-mcp works with Cursor through a JSON `mcpServers` configuration. Add the server command and arguments, provide the Google credential environment variables, and restart Cursor after changing its configuration.

Set `UNSAFE_MODE` to `true` to bypass the default label restriction. Without it, modification and destructive operations are limited to notes carrying the `keep-mcp` label, which is automatically added to notes created by the server.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewKeep MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/feuerdev-keep-mcp?style=directory)](https://allmcps.com/mcp/feuerdev-keep-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/feuerdev-keep-mcp"><img src="https://allmcps.com/api/badge/feuerdev-keep-mcp?style=directory" alt="Keep MCP on AllMCPs" /></a>