# Google Keep [Health: Active]

**Category:** 🧠 Knowledge & Memory  
**Repository:** https://github.com/mcp-dir/keep-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/google-keep

## Description
Google Keep MCP, read and edit your notes, lists, labels and collaborators. Connect with your Google

## Tools
Capabilities this server exposes over MCP:

- **keep_list_accounts** — Lista as contas Google Keep vinculadas a este install (id/email, label). Use pra descobrir o `account` quando há várias.
- **keep_find** — Busca notas no Google Keep. Filtros opcionais: query (título/texto), labels, colors, pinned, archived, trashed (default false).
- **keep_get_note** — Retorna uma nota (ou lista) do Google Keep pelo id.

Bulk support: accepts note_ids for batched execution.
- **keep_create_note** — Cria uma nota de texto no Google Keep. Recebe a label 'keep-mcp' automaticamente pra poder ser gerida depois.
- **keep_create_list** — Cria uma checklist no Google Keep. `items` = array de { text, checked }. Recebe a label 'keep-mcp' automaticamente.
- **keep_update_note** — Atualiza título e/ou texto de uma nota. Pra listas, edite os itens com os tools de list item.

Bulk support: accepts note_ids for batched execution.
- **keep_pin_note** — Fixa ou desafixa uma nota (`pinned`, default true).

Bulk support: accepts note_ids for batched execution.
- **keep_archive_note** — Arquiva ou desarquiva uma nota (`archived`, default true).

Bulk support: accepts note_ids for batched execution.
- **keep_set_note_color** — Define a cor de uma nota. Uma de: DEFAULT, RED, ORANGE, YELLOW, GREEN, TEAL, BLUE, CERULEAN, PURPLE, PINK, BROWN, GRAY.

Bulk support: accepts note_ids for batched execution.
- **keep_trash_note** — Move uma nota pra lixeira.

Bulk support: accepts note_ids for batched execution.
- **keep_restore_note** — Restaura uma nota da lixeira.

Bulk support: accepts note_ids for batched execution.
- **keep_delete_note** — Apaga uma nota permanentemente (não dá pra desfazer).

Bulk support: accepts note_ids for batched execution.
- **keep_add_list_item** — Adiciona um item a uma checklist.

Bulk support: accepts note_ids for batched execution.
- **keep_update_list_item** — Atualiza texto e/ou estado (checked) de um item de checklist (por item_id).

Bulk support: accepts item_ids for batched execution.
- **keep_delete_list_item** — Remove um item de checklist por item_id.

Bulk support: accepts item_ids for batched execution.
- **keep_list_labels** — Lista todas as labels da conta.
- **keep_create_label** — Cria uma nova label.
- **keep_delete_label** — Apaga uma label pelo nome.
- **keep_add_label_to_note** — Anexa uma label (por nome, criada se não existir) a uma nota.

Bulk support: accepts note_ids for batched execution.
- **keep_remove_label_from_note** — Remove uma label (por nome) de uma nota.

Bulk support: accepts note_ids for batched execution.
- **keep_list_note_collaborators** — Lista os colaboradores (emails) com quem a nota é compartilhada.

Bulk support: accepts note_ids for batched execution.
- **keep_add_note_collaborator** — Compartilha uma nota com um colaborador (por email).

Bulk support: accepts note_ids for batched execution.
- **keep_remove_note_collaborator** — Remove um colaborador (por email) de uma nota.

Bulk support: accepts note_ids for batched execution.
- **keep_list_note_media** — Lista os blobs de mídia (imagens/áudio/desenhos) de uma nota, com links.

Bulk support: accepts note_ids for batched execution.
- **show_version** — Show the current MCP platform and adapter versions.
- **report_bug** — Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
- **connect** — Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
- **toolkit_info** — Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
- **marketplace** — The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
- **authenticate** — MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "google-keep": {
    "url": "https://api.mcp.ai/p_keep"
  }
}
```

## Documentation

## What Google Keep MCP server does

The Google Keep MCP server gives MCP-compatible agents access to Google Keep notes and related organization data. It supports reading and writing text notes, creating checklists, changing note state, managing labels, and handling collaborators. Agents can also inspect media blobs attached to notes, including images, audio, and drawings, with links returned by the server.

The service exposes 24 tools. Search can filter by text, labels, colors, pinned state, archived state, and trash status. Note operations cover creation, retrieval, updates, pinning, archiving, coloring, trashing, restoration, and permanent deletion. Checklist tools add, edit, and remove individual items. Label tools list, create, delete, attach, and detach labels. Collaboration tools list, add, and remove collaborators by email.

## How it works

The Google Keep MCP server uses the private API used by the Google Keep Android app rather than an official public Google Keep API. Authentication uses a Google email address and a Google master token. A magic-link login flow is provided, so the documented setup does not require entering a password into the server.

The hosted service is stateless and runs on Cloudflare Workers. It supports multiple Google accounts associated with an installation. Credentials are kept in the platform’s WCA, while data returned by tools is sent to the selected LLM host, such as the MCP client or agent using the service.

By default, operations are limited to notes carrying the `keep-mcp` label. Requests that need to work with notes outside that scope can pass `unsafe=true`. Permanent deletion cannot be undone, so agents should use trash or archive operations when reversibility matters.

## Setup and configuration

Connect an MCP client to the streamable HTTP endpoint:

`https://api.mcp.ai/p_keep`

The README provides one-click installation links for Claude, Cursor, and VS Code. Claude Web and Claude Desktop use the same custom-connector flow. Other clients can connect if they support MCP over HTTP. After connecting, complete the magic-link authentication and associate the required Google account or accounts.

No environment variables are documented for running the hosted endpoint. The repository is an MIT-licensed public wrapper containing manifests, documentation, and agent skills; the hosted MCP server itself is proprietary.

## Tools and capabilities

The Google Keep MCP server includes tools for:

- Listing linked accounts and searching notes with metadata filters.
- Creating, reading, and updating text notes and checklists.
- Pinning, archiving, coloring, trashing, restoring, and permanently deleting notes.
- Managing checklist item text and checked state.
- Listing, creating, deleting, attaching, and removing labels.
- Listing, adding, and removing note collaborators by email.
- Listing attached media blobs and their links.

Color and trash operations support batched execution by accepting multiple note IDs.

## Limitations and notes

Google Keep does not provide an official public API for this use case, so the service depends on the private Android application API and a Google master token. The hosted implementation is not open source, even though the repository wrapper is MIT licensed. The LLM host selected by the user receives data returned by the tools; the project recommends checking whether that host offers a training opt-out. The default label restriction and the `unsafe=true` override should be considered when granting an agent access to existing notes.

_Full upstream README: https://allmcps.com/mcp/google-keep/readme_