Skip to main content
Glama
davenicoll

google-keep-mcp

by davenicoll
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOOGLE_EMAILYesYour Google account email address
GOOGLE_MASTER_TOKENYesYour 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_by_keywordA
Search notes by keyword against title and text content.

Args:
    query (str, optional): A string to match against the title and text
    include_archived (bool, optional): Include archived notes in results (default: True)
    include_trashed (bool, optional): Include trashed notes in results (default: False)
    
Returns:
    str: JSON string containing the matching notes with their id, title, text, pinned status, color, labels and timestamps
findA
Find notes based on a search query. Alias for search_by_keyword.

Args:
    query (str, optional): A string to match against the title and text
    include_archived (bool, optional): Include archived notes in results (default: True)
    include_trashed (bool, optional): Include trashed notes in results (default: False)
    
Returns:
    str: JSON string containing the matching notes
search_by_labelA
Search notes by label name.

Args:
    label_name (str): The label name to filter by (case-insensitive)
    include_archived (bool, optional): Include archived notes in results (default: True)
    include_trashed (bool, optional): Include trashed notes in results (default: False)
    
Returns:
    str: JSON string containing the matching notes with their id, title, text, pinned status, color, labels and timestamps
get_pinned_notesA
Get only pinned notes (active, non-archived, non-trashed).

Args:
    query (str, optional): A string to match against the title and text
    
Returns:
    str: JSON string containing pinned notes
get_archived_notesB
Get only archived notes.

Args:
    query (str, optional): A string to match against the title and text
    
Returns:
    str: JSON string containing archived notes
get_trashed_notesA
Get only trashed notes.

Args:
    query (str, optional): A string to match against the title and text
    
Returns:
    str: JSON string containing trashed notes
create_noteC
Create a new note with title and text.

Args:
    title (str, optional): The title of the note
    text (str, optional): The content of the note
    
Returns:
    str: JSON string containing the created note's data
update_noteA
Update a note's properties.

Args:
    note_id (str): The ID of the note to update
    title (str, optional): New title for the note
    text (str, optional): New text content for the note
    
Returns:
    str: JSON string containing the updated note's data
    
Raises:
    ValueError: If the note doesn't exist or cannot be modified
set_note_colorA
Set the color of a note.

Args:
    note_id (str): The ID of the note to update
    color (str): The color to set. Valid values: WHITE, RED, ORANGE, YELLOW, GREEN, TEAL, BLUE, CERULEAN, PURPLE, PINK, BROWN, GRAY
    
Returns:
    str: Success message
    
Raises:
    ValueError: If the note doesn't exist, color is invalid, or note cannot be modified
archive_noteA
Archive an active note.

Args:
    note_id (str): The ID of the note to archive
    
Returns:
    str: Success message
    
Raises:
    ValueError: If the note doesn't exist, is already archived, or cannot be modified
unarchive_noteA
Unarchive a note (move it back to active notes).

Args:
    note_id (str): The ID of the archived note to unarchive
    
Returns:
    str: Success message
    
Raises:
    ValueError: If the note doesn't exist, is not archived, or cannot be modified
restore_noteA
Restore a trashed note back to active notes.

Args:
    note_id (str): The ID of the trashed note to restore
    
Returns:
    str: Success message
    
Raises:
    ValueError: If the note doesn't exist, is not trashed, or cannot be modified
delete_noteC
Delete a note (mark for deletion).

Args:
    note_id (str): The ID of the note to delete
    
Returns:
    str: Success message
    
Raises:
    ValueError: If the note doesn't exist or cannot be modified
delete_archived_noteB
Permanently delete an archived note (moves to trash).

Args:
    note_id (str): The ID of the archived note to delete
    
Returns:
    str: Success message
    
Raises:
    ValueError: If the note doesn't exist, is not archived, or cannot be modified
get_labelsA
Analyze all labels across notes and return counts for label management.

Args:
    include_archived (bool, optional): Include archived notes in analysis (default: True)
    include_trashed (bool, optional): Include trashed notes in analysis (default: False)
    
Returns:
    str: JSON string containing label analysis with counts, sorted by usage
get_note_colorsA
Get available note colors and their current usage statistics.

Returns:
    str: JSON string containing available colors and usage statistics

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 16 tools

Disambiguation4/5

Most tools target distinct operations, but 'find' is an exact alias for 'search_by_keyword', creating redundancy. 'delete_note' and 'delete_archived_note' could also cause confusion since both move notes to trash, though the latter requires archived status.

Naming Consistency4/5

Tools predominantly use verb_noun or get_noun in snake_case (e.g., create_note, get_archived_notes). The exception is 'find', which breaks the pattern. Otherwise, naming is consistent and predictable.

Tool Count5/5

16 tools is appropriate for a note-taking server. It provides a solid range of operations without being overwhelming, covering creation, updates, deletions, archiving, trashing, searching, and customization.

Completeness3/5

The set covers basic CRUD and status management, but lacks tools for pinning/unpinning notes or assigning labels to notes. The 'get_labels' tool only analyzes usage, not modification. These are notable gaps for a full note management system.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources