It covers Keep more completely than the official surface allows — checklists, collaborators, labels and colors are all here — because it drives the same private API the app uses. That is also the caveat: it needs a Google master token, which grants full account access, so decide you are comfortable holding one that way before you wire this up.
A server for Google Keep, driven through the gkeepapi library: 23 tools covering note and checklist CRUD, labels, colors, the note lifecycle, and per-note collaborators.
- find searches title and text (case-insensitive unless you ask otherwise) with filters for labels, colors and ISO 8601 date bounds, and get_note reads one by ID
- create_note makes a text note, and create_list makes a checklist from items shaped like {text, checked}, with add_list_item, update_list_item and delete_list_item to work the checklist afterwards
- update_note changes a note's properties, set_note_color takes one of Keep's named colors (DEFAULT, RED, ORANGE, YELLOW, GREEN, TEAL, BLUE, CERULEAN, PURPLE, PINK, BROWN, GRAY), and pin_note pins or unpins
- The full lifecycle: archive_note, trash_note, restore_note and delete_note
- Labels handled end to end — list_labels, create_label, delete_label, and add_label_to_note / remove_label_from_note
- Collaborators managed per note: list_note_collaborators, add_note_collaborator and remove_note_collaborator by email
- list_note_media lists a note's media blobs with direct links where available
Your Google account email in GOOGLE_EMAIL and a Google master token in GOOGLE_MASTER_TOKEN. Run it with uvx keep-mcp or pipx run keep-mcp. It connects through gkeepapi's unofficial private API, and the master token has full access to your account — the README is explicit that you should treat it like a password and never commit or share it.
One command plus a key — uvx keep-mcp, then supply credentials