Overview

Command-line integration with Google Keep using the unofficial gkeepapi, allowing listing, searching, creating, and managing notes from scripts or terminals.

Key Advantages

1.Provides convenient CLI access to Google Keep notes (list, search, create, get, pin, archive, delete).

2.Supports search by text, enabling automations around existing Keep content.

3.Uses a dedicated App Password with 2FA, which is safer than reusing the main Google password.

4.Persists an auth token locally, reducing friction after initial login.

5.Actively maintained project with recent updates, which improves chances of compatibility and bug fixes.

Use Cases

Automating creation of Google Keep notes from scripts or cron jobs.
Quick terminal-based note capture without opening the Google Keep UI.
Batch management of notes: archiving, pinning/unpinning, or deleting via scripts.
Integrating Google Keep with other CLI tools (e.g., piping search results into other commands).
Developer workflows where notes are manipulated as part of build or deployment scripts.

Evaluation Scores

6.8

/ 10

Reliability

6.5

Functionality

7.5

Usability

7.0

Safety

5.5

Performance

8.0

Compatibility

7.0

Based on 1 evaluation · Latest: 3/19/2026

Download Trend

Loading...

Evaluation History (1)

6.8/103/19/2026linux-arm64

▼

OS: linux-arm64LLM: z-ai/glm-5

**Quick judgement:** A useful and fairly polished CLI wrapper for Google Keep that makes it easy to script and automate basic note operations. It’s powerful for power-users and automation scenarios but relies on an unofficial, reverse-engineered API and Google App Passwords, which introduces stability and account-risk considerations. **Key strengths:** - Good coverage of common note operations: list, search, get, create, archive, delete, pin/unpin. - Simple, memorable CLI commands suitable for scripting and automation. - Uses an app-specific password (with 2FA requirement), which is safer than using the main account password. - Active and recently updated project, which is encouraging for ongoing maintenance. **Major risks & limitations:** - **Unofficial API:** Built on a reverse-engineered Google Keep API; functionality can break without notice if Google changes internals. - **Policy / ToS risk:** Use of unofficial APIs may violate Google’s terms of service; users should evaluate the compliance and risk to their accounts. - **Account security considerations:** Requires Google credentials via an App Password and stores a token in `~/.config/gkeep/token.json`; misconfigured systems or shared accounts can increase risk. - **No formal uptime/SLA:** Reliability is best-effort and community-maintained; unsuitable for mission-critical workflows that demand strong guarantees. **Recommended scenarios:** - Power users and developers who need **terminal or script-based access** to Google Keep and are comfortable with unofficial APIs. - Personal or low-risk automation where occasional breakage is acceptable (e.g., personal note workflows, small scripts). - Environments where the convenience of CLI-based note management outweighs the risk of API changes and potential ToS issues. **Not recommended for:** - Highly regulated or security-sensitive environments where unofficial APIs and stored tokens are unacceptable. - Mission-critical systems that depend on guaranteed access to Google Keep data. - Users who are uncomfortable managing app passwords and reviewing the security implications of storing auth tokens locally.

Google Keep