Google Keep integration for AI agents.
Google Keep integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Google Keep tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real Google Keep actions, managed and audited.
Your user connects Google Keep once; your agent can then manage Google Keep notes for an enterprise Workspace domain. The OAuth client must be approved by a Workspace administrator — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants Google Keep access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported Google Keep tools.
6 tools are generated from the published Google Keep catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 6 tools. All published catalog entries are included in this page's server-rendered HTML.
- Keep Media Download
- Gets an attachment. To download attachment media via REST requires the alt=media query parameter. Returns a 400 bad request error if attachment media is not available in the requested MIME type.
- media
- Keep Notes Create
- Creates a new note.
- notes
- Keep Notes Delete
- Deletes a note. Caller must have the `OWNER` role on the note to delete. Deleting a note removes the resource immediately and cannot be undone. Any collaborators will lose access to the note.
- notes
- Keep Notes List
- Lists notes. Every list call returns a page of results with `page_size` as the upper bound of returned items. A `page_size` of zero allows the server to choose the upper bound. The ListNotesResponse contains at most `page_size` entries. If there are more things left to list, it provides a `next_page_token` value. (Page tokens are opaque values.) To get the next page of results, copy the result's `next_page_token` into the next request's `page_token`. Repeat until the `next_page_token` returned with a page of results is empty. ListNotes return consistent results in the face of concurrent changes, or signals that it cannot with an ABORTED error.
- notes
- Keep Notes Permissions BatchCreate
- Creates one or more permissions on the note. Only permissions with the `WRITER` role may be created. If adding any permission fails, then the entire request fails and no changes are made.
- notes
- Keep Notes Permissions BatchDelete
- Deletes one or more permissions on the note. The specified entities will immediately lose access. A permission with the `OWNER` role can't be removed. If removing a permission fails, then the entire request fails and no changes are made. Returns a 400 bad request error if a specified permission does not exist on the note.
- notes
Google Keep integration, answered
- How do AI agents use Google Keep through Open Connector?
- Your user connects Google Keep once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Keep tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Google Keep MCP server?
- Yes. Open Connector can serve Google Keep as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Keep actions with credentials injected server-side.
- Where do Google Keep credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents Google Keep — keep the keys.
Open source, self-hostable, with Google Keep credentials that never leave your infrastructure. Run it from source today.