google-keep-mcp
An MCP server for Google Keep. Apply the power of AI to organize, update, or just export your Keep notes.
Features
Search/List Operations
search_by_keyword- Search notes by keyword against title and text contentsearch_by_label- Search notes by label namefind- Alias forsearch_by_keyword(backwards compatible)get_pinned_notes- Get pinned notes (with optional search)get_archived_notes- Get archived notes (with optional search)get_trashed_notes- Get trashed notes (with optional search)
All search/list operations return notes with created, updated, and edited ISO 8601 timestamps.
Add Operations
create_note- Create a new note with title and text
Update Operations
update_note- Update a note's title and textset_note_color- Set the color of a note (12 colors available)archive_note- Archive a noteunarchive_note- Unarchive a noterestore_note- Restore a trashed note back to an active note
Delete Operations
delete_note- Mark a note for deletiondelete_archived_note- Permanently delete an archived note
Utility Operations
get_labels- Get all labels (with their usage count) for notesget_note_colors- Get available note colors and usage statistics
How to use
- Add the MCP server to your MCP servers:
"mcpServers": {
"google-keep-mcp": {
"command": "pipx",
"args": [
"run",
"google-keep-mcp"
],
"env": {
"GOOGLE_EMAIL": "Your Google Email",
"GOOGLE_MASTER_TOKEN": "Your Google Master Token"
}
}
}
- Add your credentials:
GOOGLE_EMAIL: Your Google account email addressGOOGLE_MASTER_TOKEN: Your Google account master token
Will you will need to create a master token (unless you have a Google Enterprise account, and can access the Google Keep API directly). Follow these steps:
- Goto https://myaccount.google.com/apppasswords and create an app password
- Run this docker command
docker run --rm -it breph/ha-google-home_get-tokenand enter your gmail address and app password (make sure it doesn't have a space at the end) - Obtain your master token. Be careful with this token, it has access to everything in your Google account.
Publishing
Releases publish to PyPI automatically via GitHub Actions (.github/workflows/publish.yml) using
PyPI Trusted Publishing, so no API token is stored anywhere.
- Update the version in
pyproject.tomland push tomain. - Create a GitHub release with a tag matching the version, e.g.
v1.2.1:gh release create v1.2.1 --generate-notes
- The workflow checks the tag matches the version, builds, smoke-tests the wheel and publishes.
One-time setup on pypi.org: project google-keep-mcp → Publishing → add a GitHub publisher with
owner davenicoll, repository google-keep-mcp, workflow publish.yml, environment pypi.
Metadata
Release files for google-keep-mcp 1.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| google_keep_mcp-1.2.1.tar.gz | 7.8 kB | With provenance | Details for google_keep_mcp-1.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| google_keep_mcp-1.2.1-py3-none-any.whl | Python 3 | none | any | Details for google_keep_mcp-1.2.1-py3-none-any.whl |
Total release size: 16.7 kB
Release files / google_keep_mcp-1.2.1.tar.gz
| Download URL | google_keep_mcp-1.2.1.tar.gz |
|---|---|
| Size | 7.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3b43620f1d258c85f0e0d00a271bfd67a8d0ca22b71400ccf66c347748e5972a
|
|
BLAKE2b-256 checksum How to use checksums |
082dbdcc4c130c97ffce6466056684a9aa62c6ecd756ca6e34eb4c637c9bdb3b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logRelease files / google_keep_mcp-1.2.1-py3-none-any.whl
| Download URL | google_keep_mcp-1.2.1-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
03d55c24414df60b3899cf72cd5e5dd4d4af5d69e96fc2c4aa8d4760191c016f
|
|
BLAKE2b-256 checksum How to use checksums |
d72fa74f3bbeece4e87830a4e7386d7b0651cef1b34d74324eb495a02bcdd8ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logSecurity for google-keep-mcp 1.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for google_keep_mcp-1.2.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.