home / mcp / keep mcp server

Keep MCP Server

MCP server for Google Keep

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "feuerdev-keep-mcp": {
      "command": "uv",
      "args": [
        "--directory",
        "/ABSOLUTE/PATH/TO/keep-mcp",
        "run",
        "--no-sync",
        "--python",
        ".venv/bin/python",
        "-m",
        "server"
      ],
      "env": {
        "UNSAFE_MODE": "false",
        "GOOGLE_EMAIL": "[email protected]",
        "GOOGLE_MASTER_TOKEN": "your-master-token"
      }
    }
  }
}

You set up and run the keep-mcp server to manage Google Keep notes via MCP clients. This server provides tools to query, create, update, and organize notes, labels, collaborators, and media using a local or remote MCP workflow. It includes safety controls to restrict destructive actions to notes created by the MCP server, with an option to bypass that restriction if you explicitly enable UNSAFE_MODE.

How to use

To use the keep-mcp server, add it to your MCP client configuration and supply credentials for your Google account. You can run the server locally and connect any MCP client (Codex, Goose, Claude Desktop, Cursor, etc.) to it. The server exposes a set of tools to search, create, modify, and organize your Google Keep notes, with safeguards that only modify notes created by this server unless you enable UNSAFE_MODE.

Key capabilities include searching notes with filters, creating notes and checklists, updating note content and checklist items, changing note colors, pinning, archiving, trashing, restoring, and deleting notes. You can also manage labels, collaborators, and media associated with notes. By default, destructive operations apply only to notes you created with keep-mcp; enable UNSAFE_MODE to bypass this for other notes.

How to install

Prerequisites: ensure you have Python, uv, and a compatible environment setup. You will also need a way to run the MCP server locally, such as via the Makefile or direct uv commands.

Install and run the server locally using the included Makefile flow, or connect via your MCP client with a stdio configuration that uses uv. The following snippet shows a complete MCP client configuration for starting the server through pipx, including required Google credentials.

{
  "mcpServers": {
    "keep-mcp-pipx": {
      "command": "pipx",
      "args": [
        "run",
        "keep-mcp"
      ],
      "env": {
        "GOOGLE_EMAIL": "Your Google Email",
        "GOOGLE_MASTER_TOKEN": "Your Google Master Token - see README.md"
      }
    }
  }
}

Alternative local start without Makefile

If you prefer to run via uv without the Makefile, configure the MCP client to start the server using uv with the project directory and Python virtual environment as shown here.

[mcp_servers.keep_mcp]
command = "uv"
args = [
  "--directory", "/ABSOLUTE/PATH/TO/keep-mcp",
  "run", "--no-sync", "--python", ".venv/bin/python",
  "-m", "server"
]

Credentials and security

Provide the following credentials in your MCP client configuration for the server to operate with your Google Keep account.

GOOGLE_EMAIL: Your Google account email address.

GOOGLE_MASTER_TOKEN: Your Google account master token. You can obtain this token from sources described in the linked setup guides.

Optional safety setting UNSAFE_MODE: Set to true to bypass the default restriction that only notes created by keep-mcp can be modified.

Notes on startup

The server can be started via the mpcl client using a pipx-based approach or via uv with a local directory. When using the Makefile-based flow, you typically run commands through make install and make start. If you run manually, ensure you provide the correct GOOGLE_EMAIL and GOOGLE_MASTER_TOKEN values.

Additional notes

You can find more detailed setup steps and token acquisition guidance in the credential sources referenced in the credentials section. Always restart your MCP client after updating configuration files to ensure changes take effect.

Troubleshooting

If you encounter device management or authorization issues during setup, review your Google account security settings and token generation steps. Common issues may involve token validity or access permissions.

Available tools

find

Search notes with optional filters for labels, colors, pinned, archived, and trashed.

get_note

Retrieve a single note by its ID.

create_note

Create a new note with a title and text; automatically adds the keep-mcp label.

create_list

Create a checklist note.

update_note

Update a note's title and text.

add_list_item

Add an item to a checklist note.

update_list_item

Update checklist item text and checked state.

delete_list_item

Delete a checklist item.

set_note_color

Set a note color with predefined color values.

pin_note

Pin or unpin a note.

archive_note

Archive or unarchive a note.

trash_note

Move a note to trash.

restore_note

Restore a trashed note.

delete_note

Mark a note for deletion.

list_labels

List labels.

create_label

Create a label.

delete_label

Delete a label.

add_label_to_note

Add a label to a note.

remove_label_from_note

Remove a label from a note.

list_note_collaborators

List collaborator emails for a note.

add_note_collaborator

Add a collaborator email to a note.

remove_note_collaborator

Remove a collaborator email from a note.

list_note_media

List media blobs for a note (with media links).