Can I use Google Keep as a CLI?

Yes. KosmoKrator exposes a Google Keep CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Google Keep through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Google Keep tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Google Keep credentials stored?

Google Keep credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Google Keep MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Google Keep CLI for AI Agents

Use the Google Keep CLI from KosmoKrator to call Google Keep tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Google Keep CLI Setup

Google Keep can be configured headlessly with `kosmokrator integrations:configure google-keep`.

Install, configure, and verify

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure google-keep --enable --read allow --write ask --json
kosmokrator integrations:doctor google-keep --json
kosmokrator integrations:status --json

Credentials

Authentication type: Manual OAuth token oauth2_manual_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

No credentials are required.

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call google-keep.google_keep_notes_get '{}' --json

Provider shortcut

kosmo integrations:google-keep google_keep_notes_get '{}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

kosmo integrations:docs google-keep --json
kosmo integrations:docs google-keep.google_keep_notes_get --json
kosmo integrations:schema google-keep.google_keep_notes_get --json
kosmo integrations:search "Google Keep" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`google-keep.google_keep_notes_get`

Notes Get (GET /v1/{+name}).

Read read

Parameters: none

Generic call

kosmo integrations:call google-keep.google_keep_notes_get '{}' --json

Shortcut

kosmo integrations:google-keep google_keep_notes_get '{}' --json

`google-keep.google_keep_notes_list`

Notes List (GET /v1/notes).

Read read

Parameters: none

Generic call

kosmo integrations:call google-keep.google_keep_notes_list '{}' --json

Shortcut

kosmo integrations:google-keep google_keep_notes_list '{}' --json

`google-keep.google_keep_notes_delete`

Notes Delete (DELETE /v1/{+name}).

Write write

Parameters: none

Generic call

kosmo integrations:call google-keep.google_keep_notes_delete '{}' --json

Shortcut

kosmo integrations:google-keep google_keep_notes_delete '{}' --json

`google-keep.google_keep_notes_create`

Notes Create (POST /v1/notes).

Write write

Parameters: none

Generic call

kosmo integrations:call google-keep.google_keep_notes_create '{}' --json

Shortcut

kosmo integrations:google-keep google_keep_notes_create '{}' --json

`google-keep.google_keep_notes_permissions_batch_delete`

Notes Permissions Batch Delete (POST /v1/{+parent}/permissions:batchDelete).

Write write

Parameters: none

Generic call

kosmo integrations:call google-keep.google_keep_notes_permissions_batch_delete '{}' --json

Shortcut

kosmo integrations:google-keep google_keep_notes_permissions_batch_delete '{}' --json

`google-keep.google_keep_notes_permissions_batch_create`

Notes Permissions Batch Create (POST /v1/{+parent}/permissions:batchCreate).

Write write

Parameters: none

Generic call

kosmo integrations:call google-keep.google_keep_notes_permissions_batch_create '{}' --json

Shortcut

kosmo integrations:google-keep google_keep_notes_permissions_batch_create '{}' --json

`google-keep.google_keep_media_download`

Media Download (GET /v1/{+name}).

Read read

Parameters: none

Generic call

kosmo integrations:call google-keep.google_keep_media_download '{}' --json

Shortcut

kosmo integrations:google-keep google_keep_media_download '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

google-keep.google_keep_notes_get 0 parameters

Schema command

kosmo integrations:schema google-keep.google_keep_notes_get --json

Parameter	Type	Required	Description
No parameters.

google-keep.google_keep_notes_list 0 parameters

Schema command

kosmo integrations:schema google-keep.google_keep_notes_list --json

Parameter	Type	Required	Description
No parameters.

google-keep.google_keep_notes_delete 0 parameters

Schema command

kosmo integrations:schema google-keep.google_keep_notes_delete --json

Parameter	Type	Required	Description
No parameters.

google-keep.google_keep_notes_create 0 parameters

Schema command

kosmo integrations:schema google-keep.google_keep_notes_create --json

Parameter	Type	Required	Description
No parameters.

google-keep.google_keep_notes_permissions_batch_delete 0 parameters

Schema command

kosmo integrations:schema google-keep.google_keep_notes_permissions_batch_delete --json

Parameter	Type	Required	Description
No parameters.

google-keep.google_keep_notes_permissions_batch_create 0 parameters

Schema command

kosmo integrations:schema google-keep.google_keep_notes_permissions_batch_create --json

Parameter	Type	Required	Description
No parameters.

google-keep.google_keep_media_download 0 parameters

Schema command

kosmo integrations:schema google-keep.google_keep_media_download --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.