Keep MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNSAFE_MODE | No | Set to 'true' to bypass the restriction that limits destructive and modification operations to notes that have been created by the MCP server (i.e. have the keep-mcp label). | false |
| GOOGLE_EMAIL | Yes | Your Google account email address | |
| GOOGLE_MASTER_TOKEN | Yes | Your Google account master token |
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 |
|---|---|
| findB | Find notes using text and optional filters. labels should be label IDs. colors should be ColorValue strings (e.g. DEFAULT, RED, CERULEAN). |
| get_noteB | Get a note by ID. |
| create_noteC | Create a new note with title and text. |
| create_listB | |
| add_list_itemC | Add an item to a checklist note. |
| update_list_itemB | Update checklist item text and/or checked state. |
| delete_list_itemC | Delete a checklist item. |
| update_noteC | Update a note's properties. |
| set_note_colorA | Set a note color. Valid values: DEFAULT (white), RED, ORANGE, YELLOW, GREEN, TEAL, BLUE, CERULEAN (dark blue), PURPLE, PINK, BROWN, GRAY. |
| pin_noteC | Pin or unpin a note. |
| archive_noteC | Archive or unarchive a note. |
| trash_noteC | Move a note to trash. |
| restore_noteB | Restore a trashed/deleted note. |
| delete_noteC | Delete a note (mark for deletion). |
| list_labelsA | List all labels. |
| create_labelC | Create a label. |
| delete_labelB | Delete a label by ID. |
| add_label_to_noteC | Add a label to a note. |
| remove_label_from_noteA | Remove a label from a note. |
| list_note_collaboratorsB | List collaborator emails for a note. |
| add_note_collaboratorC | Add a collaborator email to a note. |
| remove_note_collaboratorC | Remove a collaborator email from a note. |
| list_note_mediaB | List note media blobs and direct media links when available. |
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 23 tools
Each tool has a clearly distinct purpose, covering notes, labels, checklist items, collaboration, and media. There is minimal overlap; for example, archive, trash, delete, and restore are all separate actions. An agent can reliably select the correct tool.
Most tools follow a consistent verb_noun pattern with snake_case (e.g., add_label_to_note, create_note). Minor inconsistency: 'find' is a bare verb instead of 'find_notes', and 'create_list' creates a checklist note rather than using 'create_checklist'. Overall, the pattern is predictable.
23 tools is slightly above the typical 3-15 range but reasonable for a full-featured note-taking server. Each tool captures a specific operation, and the count is not overwhelming for the domain.
CRUD operations are covered for notes, labels, and checklist items. However, there is no tool to list all notes (only find with text search), and no explicit tool to unarchive or unpin (toggle behavior), which could cause agent failures if not inferred. Notable gaps exist.