# feuerdev/keep-mcp [Health: Active]

**Category:** 🛠️ Other Tools and Integrations  
**Repository:** https://github.com/feuerdev/keep-mcp  
**GitHub Stars:** 108  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/feuerdev-keep-mcp

## Description
Read, create, update and delete Google Keep notes.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "keep-mcp": {
    "command": "uvx",
    "args": ["keep-mcp"],
    "env": {
      "GOOGLE_EMAIL": "",
      "GOOGLE_MASTER_TOKEN": "",
      "UNSAFE_MODE": ""
    }
  }
}
```

**Requires environment variables:** `GOOGLE_EMAIL`, `GOOGLE_MASTER_TOKEN`, `UNSAFE_MODE` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/feuerdev-keep-mcp/readme_