keep-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TZ | No | Time zone for the server (e.g. Europe/London). | |
| GOOGLE_EMAIL | Yes | Google account email address associated with the master token (required for authentication to Google Keep). | |
| MCP_AUTH_TOKEN | No | Authentication token required for HTTP mode and OAuth consent flow. Generate one with `openssl rand -hex 24`. | |
| KEEP_DEFAULT_LIST | No | Name of the default Google Keep list used by `keep_get` and other tools when no list argument is provided. | |
| KEEP_WRITE_TITLES | No | Comma-separated list of list titles that write operations (add/check/uncheck/remove/create) are restricted to. Leave empty to allow writes on all lists. | |
| GOOGLE_MASTER_TOKEN | Yes | Google master token for authenticating with the unofficial gkeepapi. Treat like a password. | |
| MCP_PUBLIC_BASE_URL | No | Public base URL of the HTTP endpoint (e.g. https://kpr-xxxx.example.com) used for the OAuth consent flow. |
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 |
|---|---|
| keep_findA | Search Keep notes and checklists by title or body text. Returns id, title, type (list/note), pinned, and for lists the items. Use this to find the shopping list if you do not know its exact title. |
| keep_getA | Get one Keep note or checklist. Pass list_title (e.g. 'Shopping') or note_id from keep_find. If both are omitted, uses KEEP_DEFAULT_LIST. Lists include each item's text and checked state. |
| keep_add_itemsA | Add one or more unchecked items to a Keep checklist (the shopping list). Does not create duplicates automatically — check keep_get first. |
| keep_check_itemsA | Tick off Keep checklist items after they have been added to the Tesco basket (or bought). Match by item name; unique substrings are ok. |
| keep_uncheck_itemsB | Untick Keep checklist items (put them back on the shopping list). |
| keep_remove_itemsB | Delete items from a Keep checklist by name. |
| keep_create_listA | Create a new Keep checklist. Use this only if the shopping list does not already exist — prefer keep_add_items on the existing list. |
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 7 tools
Each tool has a clear, distinct purpose: searching, retrieving, creating lists, and performing specific item actions. The find/get distinction is slight but descriptions make it clear.
All tools follow a consistent keep_ prefix with snake_case verb_noun naming, making the action and target obvious across the set.
Seven tools is well-scoped for a Keep-focused MCP server, covering core list and item operations without unnecessary bloat.
The main workflows are covered: create, find, get, add, check/uncheck, and remove. Minor gaps like deleting a whole list or editing note text prevent a perfect score.