Google Keep MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNSAFE_MODE | No | Set to 'true' to allow modifying all notes | |
| GOOGLE_EMAIL | Yes | Your Google account email | |
| GOOGLE_MASTER_TOKEN | Yes | Master token from setup step 2 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| findC | Search notes with optional filters. Returns matching notes. |
| get_noteB | Get a specific note by its ID. |
| list_note_mediaA | List media attachments on a note. |
| create_noteA | Create a new text note. Auto-applies the 'keep-mcp' safety label. |
| create_listA | Create a new checklist note. Auto-applies the 'keep-mcp' safety label. Items are provided as a list of strings (all unchecked by default). |
| update_noteB | Update a note's title and/or text content. |
| set_note_colorA | Set the color of a note. Valid colors: WHITE, RED, ORANGE, YELLOW, GREEN, TEAL, BLUE, DARK_BLUE, PURPLE, PINK, BROWN, GRAY. |
| delete_noteA | Permanently delete a note. Requires UNSAFE_MODE=true. Use trash_note for reversible deletion. |
| restore_noteA | Restore a note from trash. Only works on trashed notes, not permanently deleted ones. |
| pin_noteC | Pin or unpin a note. |
| archive_noteC | Archive or unarchive a note. |
| trash_noteB | Move a note to trash. This is reversible with restore_note. |
| add_list_itemC | Add an item to a checklist note. |
| update_list_itemC | Update a checklist item's text and/or checked state. |
| delete_list_itemB | Remove an item from a checklist note. |
| list_labelsA | List all labels in Google Keep. |
| create_labelB | Create a new label. |
| delete_labelA | Delete a label. Requires UNSAFE_MODE=true as this is globally destructive. |
| add_label_to_noteC | Add a label to a note. |
| remove_label_from_noteA | Remove a label from a note. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Each tool maps to a clear resource and action: notes, checklist items, labels, media, and lifecycle states are all separate. Even closely related operations like delete_note vs trash_note are explicitly differentiated by permanence and reversibility.
The set consistently uses snake_case verb_noun names such as get_note, create_list, update_list_item, and add_label_to_note. The main inconsistency is the bare verb 'find' instead of something like search_notes, but the rest of the naming is highly predictable.
At 20 tools, the server sits in the borderline-heavy range and covers a broad amount of Google Keep functionality. The operations are not redundant, but the surface could be tightened by consolidating some state toggles or label operations.
The server covers note CRUD, trash/restore, pin/archive, color, checklist item operations, and label attachment and management. Notable gaps are the lack of a label rename/update operation and no way to add media to a note, but core Keep workflows are well represented.