keep-mcp
MCP server for Google Keep
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/feuerdev/keep-mcp with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/feuerdev/keep-mcp'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/feuerdev--keep-mcp)HTML
<a href="/listings/feuerdev--keep-mcp"><img src="/api/listings/feuerdev--keep-mcp/badge.svg" alt="findsafeskills safety rating" /></a>Install
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 383 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- # keep-mcp
- MCP server for Google Keep
- See [CONTRIBUTING.md](CONTRIBUTING.md) for contribution guidelines and required visual evidence.
- 
- ## How to use
- 1. Add the MCP server to your MCP servers:
- ```json
- "mcpServers": {
- "keep-mcp-pipx": {
- "command": "pipx",
- "args": [
- "run",
- "keep-mcp"
- ],
- "env": {
- "GOOGLE_EMAIL": "Your Google Email",
- "GOOGLE_MASTER_TOKEN": "Your Google Master Token - see README.md"
- }
- }
- }
- ```
- Or with `uvx`:
- ```json
- "mcpServers": {
- "keep-mcp": {
- "command": "uvx",
- "args": [
- "keep-mcp"
- ],
- "env": {
- "GOOGLE_EMAIL": "Your Google Email",
- "GOOGLE_MASTER_TOKEN": "Your Google Master Token - see README.md"
- }
- }
- }
- ```
- 2. Add your credentials:
- * `GOOGLE_EMAIL`: Your Google account email address
- * `GOOGLE_MASTER_TOKEN`: Your Google account master token
- ### Obtain a Google master token
- `keep-mcp` uses [gkeepapi](https://gkeepapi.readthedocs.io/), which connects to Google Keep through an unofficial private API. A Google master token has full access to your account. Treat it like a password and never commit or share it.
- You need [Docker](https://docs.docker.com/get-started/get-docker/) and a desktop browser.
- 1. Open https://accounts.google.com/EmbeddedSetup and sign in with the Google account you use for Keep.
- 2. Click **I agree**. The page may keep loading forever. Leave it open and continue.
- 3. Copy the `oauth_token` cookie:
- * **Chrome or Edge:** Press F12, open the **Application** tab, then **Cookies** → `https://accounts.google.com`.
- * **Firefox:** Press F12, open the **Storage** tab, then **Cookies** → `https://accounts.google.com`.
- Find the row named `oauth_token` and copy its value. It starts with `oauth2_4/`.
- 4. Right away, run this in a terminal and paste your email and the cookie value when asked:
- ```bash
- docker run --rm -it ghcr.io/astral-sh/uv:python3.13-bookworm-slim uv run --no-project --with gpsoauth python -c "import gpsoauth; r = gpsoauth.exchange_token(input('Email: '), input('oauth_token: '), '0123456789abcdef'); print(r.get('Token', r))"
- ```
- Without Docker, install [uv](https://docs.astral.sh/uv/getting-started/installation/) and run the same command without the `docker run --rm -it ghcr.io/astral-sh/uv:python3.13-bookworm-slim` part.
- 5. The command prints your master token. It starts with `aas_et/`. Use it as `GOOGLE_MASTER_TOKEN`.
- If it prints an error such as `BadAuthentication` instead, the cookie has expired. Repeat steps 1 to 4 to get a fresh one.
- #### More details
- * [`gpsoauth`'s alternative flow](https://github.com/simon-weber/gpsoauth#alternative-flow) describes the token exchange.
- * [gkeepapi's "Obtaining a Master Token" instructions](https://gkeepapi.readthedocs.io/en/latest/#obtaining-a-master-token) describe the same exchange.
- Older instructions may ask for your Google password or an app password and call `perform_master_login()`. That flow is unreliable and can return `BadAuthentication`. Use the browser-assisted flow above instead.
- ## Features
- ### Query and read tools
- * `find`: Search notes (case-insensitive by default) with optional filters for labels, colors, pinned, archived, trashed, creation/update date ranges (ISO 8601, UTC), and a result limit (default 50)
- * `get_note`: Get a single note by ID
- ### Creation and update tools
- * `create_note`: Create a new note with title and text (automatically adds keep-mcp label)
- * `create_list`: Create a checklist note
- * `update_note`: Update a note's title and text
- * `add_list_item`: Add an item to a checklist note
- * `update_list_item`: Update checklist item text and checked state
- * `delete_list_item`: Delete a checklist item
- * `move_list_item`: Move an item to a zero-based final position
- * `reorder_list_items`: Bulk reorder a checklist using all its item IDs
- * `replace_list_items`: Replace the entire checklist, creating new item IDs
- #### Checklist ordering and replacement
- Get the current item IDs and order with `get_note`. `move_list_item` takes
- `note_id`, `item_id`, and `position`: `0` means first, and the last valid position
- is the item count minus one. The position is the item's final index after moving.
- For bulk ordering, call `reorder_list_items` with `note_id` and `item_ids` in the
- desired first-to-last order. Supply **every current item ID exactly once**, including
- checked items. Missing, duplicate, unknown, foreign, or deleted IDs are rejected
- before mutation. Ordering preserves item IDs, text and checked states. Positions
- refer to the combined order returned by `get_note`; Keep may display checked items
- in a separate section according to its settings.
- Example tool arguments (substitute IDs returned by `get_note`):
- ```json
- {"note_id":"NOTE_ID","item_id":"THIRD_ITEM_ID","position":0}
- ```
- ```json
- {"note_id":"NOTE_ID","item_ids":["THIRD_ITEM_ID","FIRST_ITEM_ID","SECOND_ITEM_ID"]}
- ```
- `replace_list_items` takes `note_id` and an `items` array. Each item requires
- `text`; `checked` is optional and defaults to `false`. Only these two item fields
- are accepted. The full payload is validated before any item is changed. All old
- items are marked for deletion and new items are created in input order with new
- IDs. The note itself, title, labels, collaborators and other note metadata remain.
- Passing `items: []` clears the checklist; an empty bulk order is valid only for an
- already empty checklist.
- ```json
- {"note_id":"NOTE_ID","items":[{"text":"Milk","checked":false},{"text":"Bread","checked":true}]}
- ```
- All three tools currently require flat checklists: an existing checklist with
- indented items is rejected without changes, so hierarchy cannot be silently lost.
- They are annotated as destructive because ordering overwrites the existing order
- and replacement deletes the old items.
- They use the same keep-mcp label / `UNSAFE_MODE` restriction as other modification
- tools. They refresh through the shared client, then sync once after mutation.
- Moving an item to its current position or supplying the current bulk order leaves
- the items untouched and skips the post-mutation sync.
- This is not a server-side atomic transaction: a network failure can leave the
- remote outcome uncertain. Read the note again before retrying, particularly after
- replacement. Concurrent external edits can also affect the final order.
- ### Note state tools
- * `set_note_color`: Set a note color (valid values: DEFAULT, RED, ORANGE, YELLOW, GREEN, TEAL, BLUE, CERULEAN, PURPLE, PINK, BROWN, GRAY)
- * `pin_note`: Pin or unpin a note
- * `archive_note`: Archive or unarchive a note
- * `trash_note`: Move a note to trash
- * `restore_note`: Restore a trashed/deleted note
- * `delete_note`: Mark a note for deletion
- ### Labels, collaborators, and media tools
- * `list_labels`: List labels
- * `create_label`: Create a label
- * `delete_label`: Delete a label
- * `add_label_to_note`: Add a label to a note
- * `remove_label_from_note`: Remove a label from a note
- * `list_note_collaborators`: List collaborator emails for a note
- * `add_note_collaborator`: Add a collaborator email to a note
- * `remove_note_collaborator`: Remove a collaborator email from a note
- * `list_note_media`: List media blobs for a note (with media links)
- * `download_media`: Download a note's media (images, drawings, audio) to a local directory through the authenticated session (the raw media links answer 403 to plain HTTP clients). Not available over Streamable HTTP, where the files would land on the server
- By default, all destructive and modification operations are restricted to notes that have were created by the MCP server (i.e. have the keep-mcp label). Set `UNSAFE_MODE` to `true` to bypass this restriction.
- ```
- "env": {
- ...
- "UNSAFE_MODE": "true"
- }
- ```
- ## Local development (uv + make)
- If you prefer a JS-style workflow (`npm i`, `npm start`), use the included `Makefile`:
- ```bash
- make install # like npm i
- make start # like npm start
- make test
- make lint
- ```
- Run the real-account smoke test with credentials:
- ```bash
- GOOGLE_EMAIL="you@example.com" \
- GOOGLE_MASTER_TOKEN="..." \
- make smoke
- ```
- Equivalent direct `uv` commands (without `make`):
- ```bash
- UV_CACHE_DIR=/tmp/uv-cache uv venv --python 3.11 .venv
- UV_CACHE_DIR=/tmp/uv-cache uv pip install --python .venv/bin/python -e .
- UV_CACHE_DIR=/tmp/uv-cache uv run --no-sync --python .venv/bin/python -m server
- ```
- ## Testing
- ### Unit tests (default)
- The project includes a lightweight unit test suite under `tests/`.
- It validates:
- * note serialization shape for note and list objects (including labels, collaborators, media, and list items)
- * modification safety behavior (`keep-mcp` label requirement and `UNSAFE_MODE=true` override)
- * MCP tool behavior in `src/server/cli.py` using mocked Keep client objects (tool happy paths and key error paths)
- Run locally:
- ```bash
- make test
- ```
- ### Smoke test against a real Keep account
- For additional confidence, run a basic lifecycle smoke test against a dedicated test account:
- ```bash
- GOOGLE_EMAIL="you@example.com" \
- GOOGLE_MASTER_TOKEN="..." \
- make smoke
- ```
- What it does:
- * create note
- * update note
- * pin/unpin
- * archive/unarchive
- * trash/restore
- * delete
- This script is intended for manual verification and is not run in CI.
- ### CI checks
- GitHub Actions runs on every pull request and executes:
- * lint (`ruff check .`)
- * unit tests with coverage (`pytest -q --cov=src/server --cov-report=term-missing --cov-fail-under=70`)
- * bytecode sanity (`python -m compileall src`)
- ## Publishing
- ### Automatic publish on merge to `main` (GitHub Actions)
- This repo includes a release workflow at `.github/workflows/release.yml` that runs on every push to `main` (including merged PRs).
- It will:
- * inspect commits since the last release tag (`vX.Y.Z`)
- * compute the next semantic version from Conventional Commit types
- * skip publishing when there are no releasable commit types
- * run lint and unit tests
- * build `dist/*`
- * publish to PyPI
- * create a GitHub release/tag `v<computed-version>` with generated notes
- Version bump rules:
- * major: commit subject with `!` (example: `feat!:` or `fix(api)!:`) or commit body containing `BREAKING CHANGE`
- * minor: `feat:`
- * patch: `fix:`, `perf:`, `revert:`
- * no release: `docs:`, `chore:`, `ci:`, `test:`, `refactor:` (unless the commit is marked as breaking)
- Required repository secret:
- * `PYPI_API_TOKEN`: a PyPI API token (recommended scope: this project only)
- ### Manual publish
- To publish manually to PyPI:
- 1. Update the version in `pyproject.toml`
- 2. Build the package:
- ```bash
- pipx run build
- ```
- 3. Upload to PyPI:
- ```bash
- pipx run twine upload --repository pypi dist/*
- ```
- ## Run locally with MCP clients
- This is useful when you want a client to run this server from your local checkout instead of PyPI.
- 1. Create a local virtualenv and install in editable mode:
- ```bash
- cd /ABSOLUTE/PATH/TO/keep-mcp
- make install
- ```
- 2. Add the server to your MCP client config.
- ### `config.toml` clients (Codex, Goose, etc.)
- ```toml
- [mcp_servers.keep_mcp]
- command = "make"
- args = ["-C", "/ABSOLUTE/PATH/TO/keep-mcp", "start"]
- [mcp_servers.keep_mcp.env]
- GOOGLE_EMAIL = "you@example.com"
- GOOGLE_MASTER_TOKEN = "your-master-token"
- UNSAFE_MODE = "false"
- ```
- ### JSON `mcpServers` clients (Claude Desktop, Cursor, Cline, etc.)
- ```json
- {
- "mcpServers": {
- "keep-mcp-local": {
- "command": "make",
- "args": ["-C", "/ABSOLUTE/PATH/TO/keep-mcp", "start"],
- "env": {
- "GOOGLE_EMAIL": "you@example.com",
- "GOOGLE_MASTER_TOKEN": "your-master-token",
- "UNSAFE_MODE": "false"
- }
- }
- }
- }
- ```
- Alternative (without `make`):
- ```toml
- [mcp_servers.keep_mcp]
- command = "uv"
- args = [
- "--directory", "/ABSOLUTE/PATH/TO/keep-mcp",
- "run", "--no-sync", "--python", ".venv/bin/python",
- "-m", "server"
- ]
- ```
- Notes:
- * Run `make install` once before starting from an MCP client.
- * Only the repo root path is required (no absolute `/.venv/bin/python` path).
- * Ensure `make` and `uv` are in your `PATH`.
- * Restart your MCP client after updating config files.
- * `UNSAFE_MODE` is optional; keep it `"false"` unless you explicitly want to modify non-`keep-mcp` notes.
- ## Running over Streamable HTTP
- `keep-mcp` supports the MCP Streamable HTTP transport (`/mcp` endpoint) in addition to the default `stdio` transport:
- ```bash
- # Start Streamable HTTP server on localhost (default: 127.0.0.1:8000)
- keep-mcp --transport streamable-http
- # Customize host or port
- keep-mcp --transport streamable-http --host 127.0.0.1 --port 8000
- ```
- > [!NOTE]
- > `keep-mcp` binds to `127.0.0.1` by default with DNS rebinding protection enabled. To expose the server to remote or web clients (such as Gemini web), place an authenticating proxy (such as [mcp-auth-proxy](https://github.com/sigbit/mcp-auth-proxy)) in front of the server.
- ## Running in Docker
- A `Dockerfile` is provided for running `keep-mcp` as a containerized Streamable HTTP server listening on port 8000.
- 1. Build the container image:
- ```bash
- docker build -t keep-mcp .
- ```
- 2. Run the container:
- ```bash
- docker run -d \
- -e GOOGLE_EMAIL="you@example.com" \
- -e GOOGLE_MASTER_TOKEN="aas_et/..." \
- -p 127.0.0.1:8000:8000 \
- keep-mcp
- ```
- > [!WARNING]
- > The container has no built-in authentication. Publish it only to localhost (`-p 127.0.0.1:8000:8000`) or place it behind an authenticating reverse proxy if exposing it over a network.
- ## Troubleshooting
- * If you get "DeviceManagementRequiredOrSyncDisabled" check https://admin.google.com/ac/devices/settings/general and turn "Turn off mobile management (Unmanaged)"
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.