google-keep-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_KEEP_EMAIL | Yes | Your Google account email address used to authenticate with gkeepapi. | |
| GOOGLE_KEEP_MASTER_TOKEN | Yes | A Google master token for gkeepapi authentication. Grants full access to the account; treat it like a password. |
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 |
|---|---|
| list_notesA | Search the Google Keep account and return the matching notes. |
| delete_noteA | Move a Google Keep note to the trash, or delete it permanently. |
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 2 tools
list_notes and delete_note target completely distinct actions with no overlap. An agent can easily choose the right tool based on the operation needed.
Both tools follow a consistent verb_noun pattern (list_notes, delete_note). The naming is predictable and uniform.
With only 2 tools, the server feels thin for a Google Keep integration. The count is borderline but not absurdly small.
The surface lacks essential operations like creating, updating, or fetching a single note by ID. Only list and delete are supported, leaving significant workflow gaps.