Labsco
MCP SERVER

wlater-McpServer

by briansbrian

Google Keep from an assistant — search and read notes, tick items off lists, create notes and labels — with every change previewed before it syncs.

Note-Taking & Personal Knowledge Bases
Summary
Write access, with the brakes built in.

Two decisions make this comfortable to connect: deletion is simply absent from the tool surface, and every write waits for your approval. That turns the scary version of "an assistant with access to my notes" into something closer to a proposal queue. The master token is the awkward part — Keep has no official API, so the credential is broader than an API key would be, which is why keyring storage matters.

What it is

An MCP server over Google Keep, built on the gkeepapi library. It reads the whole note collection with filtering, and writes back changes, but with a deliberate safety design: every modification is previewed for approval before it reaches Keep, deletion is not exposed at all, and credentials live in your operating system's keyring rather than a config file.

What you get
  • Search and read every note, filtered by label, colour, pinned state or archived state, including notes with images, drawings and audio attached
  • Create notes and todo lists, and check items off a shopping or task list
  • Update note content, titles and colours, pin notes, archive them, and sort a list alphabetically
  • Organise with labels, and share notes with collaborators
  • A preview step on every change — nothing syncs to Keep until you approve it, and nothing happens automatically
  • No delete: notes can only be trashed and untrashed, with permanent deletion left to the Keep app itself
Requirements

A Google account and its master token, obtained either by running `wlater-setup token` with Selenium and a webdriver installed — a browser opens, you sign in, and the token is extracted — or by fetching it manually through the gpsoauth route and running `wlater-setup`. `pip install wlater-mcp` installs the package (0.2.0 in pyproject); the client entry runs `python -m wlater_mcp.server` over stdio. Credentials are stored in the system keyring — Windows Credential Locker, macOS Keychain or the Linux Secret Service. If the connection fails after a restart, re-run `wlater-setup` and decline reconfiguration; that step exists so credentials are not left open on every start.

Setup effort

One command plus a key — pip install wlater-mcp, then supply credentials