Google Keep

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.