Google Keep vs Codebase Memory MCP

A side-by-side look at the Google Keep and Codebase Memory MCP 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 declaredCodebase Memory MCP logoCodebase Memory MCPKnowledge & Memory · Local subprocess (stdio)Code-intelligence engine that indexes a repo into a persistent knowledge graph — functions, classes, call chains, HTTP routes, cross-service links. 159 languages via tree-sitter + Hybrid LSP, sub-ms structural queries, 99% fewer tokens than grep. Single static binary, zero dependencies, 100% local. npx codebase-memory-mcp73GreatAuth: no auth required

Verdict: choose Google Keep for knowledge & memory work over a hosted endpoint; choose Codebase Memory MCP 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

Codebase Memory MCP logoChoose Codebase Memory MCP when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like index_repository, search_graph, query_graph.
Explore Codebase Memory MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGoogle Keep logoGoogle KeepCodebase Memory MCP logoCodebase Memory MCP
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal57/100 · Good73/100 · Great
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars147,386
Directory activity 0 views 0 installs 0 upvotes 9 views 1 installs 1 upvotes
Tools3017

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

Codebase Memory MCP tools 17

  • index_repositoryIndex a repository. full/moderate add semantics; fast omits them; cross-repo-intelligence links services. Reports coverage gaps.
  • search_graphFind symbols via BM25 query, regex name/qn filters, or semantic_query. Rows keep qn/file/lines and in/out over CALLS/USAGE/CALL_REFERENCE/INHERITS/IMPLEMENTS.
  • query_graphRead-only Cypher for multi-hop, aggregation, complexity, or cross-service analysis. Default: 200 visible rows with exact/lower-bound totals and truncation; continue safely with next_cursor. graph=missed is a file tree of flagged coverage gaps; absence is not proof of completeness. Use get_graph_schema(diagnostics=full) for properties.
  • trace_pathTrace callers/callees, data flow, or cross-service paths. Defaults exclude tests and resolver evidence. Rows keep qn/hop with explicit totals, relations, and continuations.
  • get_code_snippetRead a search_graph symbol. auto bounds source and outlines large containers; full restores up to 500 lines. Source/outline pages continue; coverage_note marks gaps.
  • get_file_outlineDeclaration outline of one exact repository-relative file: optional exact label filter, source order, exact total/offset/limit paging; file/folder/container nodes excluded.
  • get_graph_schemaGet node-label and edge-type counts. diagnostics=full also lists queryable properties.
  • compare_graphsCompare two indexed snapshots: deterministic target-only additions and base-only removals of stable node/edge identities; each set capped by limit and a 512 KiB budget with exact totals and truncation reasons.
  • get_architectureCompact counts, languages, packages, entry points. Request structure, dependencies, routes, hotspots, boundaries, layers, clusters, cycles, or file_tree; path scopes a directory.
  • search_codeGraph-ranked text search: compact symbols, full bounded source, or file paths.
  • list_projectsList projects with stable paging. Identity is lean; stats adds graph sizes.
  • delete_projectDelete a project from the index
  • +5 more on 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"
    }
  }
}

Codebase Memory MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "deusdata-codebase-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "codebase-memory-mcp"
      ]
    }
  }
}

Frequently asked questions

Google Keep is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Codebase Memory MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Google Keep for knowledge & memory work and Codebase Memory MCP 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. Codebase Memory MCP is listed as free. Auth: no auth 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 deusdata-codebase-memory-mcp 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. Codebase Memory MCP has 73/100 (Great) with 9 views, 1 installs and 47,386 GitHub stars.