Google Keep vs Hindsight

A side-by-side look at the Google Keep and Hindsight MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Google Keep logoGoogle KeepKnowledge & Memory · Remote HTTP/SSEGoogle Keep MCP, read and edit your notes, lists, labels and collaborators. Connect with your Google57GoodAuth: not declaredHindsight logoHindsightKnowledge & Memory · Local subprocess (stdio)Hindsight: Agent Memory That Works Like Human Memory - Built for AI Agents to manage Long Term Memory57GoodAuth: api key required

Verdict: choose Google Keep for knowledge & memory work over a hosted endpoint; choose Hindsight for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Google Keep logoChoose Google Keep when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like keep_list_accounts, keep_find, keep_get_note.
Explore Google Keep

Hindsight logoChoose Hindsight when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: HINDSIGHT_API_LLM_API_KEY, HINDSIGHT_API_LLM_PROVIDER, HINDSIGHT_DB_PASSWORD.
Explore Hindsight

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGoogle Keep logoGoogle KeepHindsight logoHindsight
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal57/100 · Good57/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsNone listedHINDSIGHT_API_LLM_API_KEYHINDSIGHT_API_LLM_PROVIDERHINDSIGHT_DB_PASSWORD
Verified ownerCommunity listingCommunity listing
GitHub stars153,323
Directory activity 0 views 0 installs 0 upvotes 14 views 0 installs 0 upvotes
Tools30Not listed

Tools & capabilities

Google Keep tools 30

  • keep_list_accountsLista as contas Google Keep vinculadas a este install (id/email, label). Use pra descobrir o `account` quando há várias.
  • keep_findBusca notas no Google Keep. Filtros opcionais: query (título/texto), labels, colors, pinned, archived, trashed (default false).
  • keep_get_noteRetorna uma nota (ou lista) do Google Keep pelo id. Bulk support: accepts note_ids for batched execution.
  • keep_create_noteCria uma nota de texto no Google Keep. Recebe a label 'keep-mcp' automaticamente pra poder ser gerida depois.
  • keep_create_listCria uma checklist no Google Keep. `items` = array de { text, checked }. Recebe a label 'keep-mcp' automaticamente.
  • keep_update_noteAtualiza título e/ou texto de uma nota. Pra listas, edite os itens com os tools de list item. Bulk support: accepts note_ids for batched execution.
  • keep_pin_noteFixa ou desafixa uma nota (`pinned`, default true). Bulk support: accepts note_ids for batched execution.
  • keep_archive_noteArquiva ou desarquiva uma nota (`archived`, default true). Bulk support: accepts note_ids for batched execution.
  • keep_set_note_colorDefine a cor de uma nota. Uma de: DEFAULT, RED, ORANGE, YELLOW, GREEN, TEAL, BLUE, CERULEAN, PURPLE, PINK, BROWN, GRAY. Bulk support: accepts note_ids for batched execution.
  • keep_trash_noteMove uma nota pra lixeira. Bulk support: accepts note_ids for batched execution.
  • keep_restore_noteRestaura uma nota da lixeira. Bulk support: accepts note_ids for batched execution.
  • keep_delete_noteApaga uma nota permanentemente (não dá pra desfazer). Bulk support: accepts note_ids for batched execution.
  • +18 more on the listing page

Hindsight tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Google Keep

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "google-keep": {
      "url": "https://api.mcp.ai/p_keep"
    }
  }
}

Hindsight

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vectorize-io-hindsight": {
      "command": "npx",
      "args": [
        "-y",
        "@vectorize-io/hindsight-coding-agents"
      ],
      "env": {
        "HINDSIGHT_API_LLM_API_KEY": "YOUR_HINDSIGHT_API_LLM_API_KEY_HERE",
        "HINDSIGHT_API_LLM_PROVIDER": "YOUR_HINDSIGHT_API_LLM_PROVIDER_HERE",
        "HINDSIGHT_DB_PASSWORD": "YOUR_HINDSIGHT_DB_PASSWORD_HERE"
      }
    }
  }
}

Frequently asked questions

Google Keep is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Hindsight belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Google Keep for knowledge & memory work and Hindsight for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Google Keep has no declared pricing — check the project's own site. Hindsight is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add google-keep and vectorize-io-hindsight as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Google Keep has a quality signal of 57/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Hindsight has 57/100 (Good) with 14 views, 0 installs and 53,323 GitHub stars.