What is the key difference between Keymem and MCP Odoo?

Keymem belongs to the Workplace & Productivity category with local stdio execution, while MCP Odoo belongs to the Workplace & Productivity category with local stdio execution.

How do I install Keymem or MCP Odoo in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Keymem and MCP Odoo free or paid?

Keymem operates under a Free / Open Source model (No auth required). MCP Odoo operates under a Free / Open Source model (other).

Which MCP server has more tools and community activity?

Keymem lists 12 tools with 2 views and 3 GitHub stars. MCP Odoo lists 41 tools with 4 views and 413 GitHub stars.

Can I use both Keymem and MCP Odoo together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Keymem vs MCP Odoo

In-depth architectural comparison of the Keymem and MCP Odoo MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Keymem

Workplace & Productivity · Local stdio

Quality: 64/100 (Good) | Auth: No auth required

MCP Odoo

Workplace & Productivity · Local stdio

Quality: 69/100 (Great) | Auth: other

Verdict Summary: Choose Keymem if you need specialized Workplace & Productivity tools running via a local process. Choose MCP Odoo if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Keymem when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: recall, browse_keys, read_key.

Explore Keymem Details

Choose MCP Odoo when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
Primary tools included: data_quality_report, diagnose_odoo_call, generate_json2_payload.

Explore MCP Odoo Details

Feature & Specification Comparison

Specification	Keymem donggyun112 Workplace & Productivity	MCP Odoo tuanle96 Workplace & Productivity
Summary	Associative key-graph memory for LLM agents — recall by association, not vector similarity.	Production-grade MCP server for Odoo ERP (16-19) with zero Odoo-side install. 24 tools across read, write (approval-token gated), diagnose, migrate, and audit. JSON-2 transport for Odoo 19+, real Docker Compose smoke tests against Odoo 16/17/18/19, diagnostics (diagnoseodoocall, upgraderiskreport, fitgapreport, scanaddonssource), and 5 reusable agent prompts.
Category & Scope

Tools & Capabilities Breakdown

Keymem Tools (12)

recall

Search long-term memory for what is already known about the user, project, or topic — call this before your first reply and whenever the topic shifts. Always pass the active namespace when known. Returns matching key clusters only (not memory content): canonical concept, aliases, key type, match score, linked-memory count, hub status, and specificity. For a core lookup, complete read_key(key_id, original_query, namespace) then read_memory(memory_id, via_key_id, namespace): only the full read grows depth/access, reinforces the traversed edge, and learns aliases. Use short focused noun queries and decompose multi-fact questions into several recall calls. inject:true is only an unconfirmed passive preview and must not replace that traversal; injected memories are not reinforced. inject_top_k defaults to 1; inject_max_chars defaults to 2000 and marks truncated previews. An empty result returns {status:'no_match', nearest_keys} — the closest stored concepts below the gate; retry with one of those concepts when relevant.

browse_keys

Browse the vocabulary of one namespace when recall has no hit or you need an entry point. Returns active key clusters with hubs first, then by linked-memory count. This is index metadata only; continue with read_key(key_id, query, namespace) and read_memory(memory_id, via_key_id, namespace).

read_key

List the memories stored under one key (concept), ranked. Returns the canonical key, its aliases, and hub metadata plus ranked memory IDs and metadata — never memory content. Always pass the original focused query and active namespace when known: handles are then ranked by content relevance, which is essential for hubs. Call read_memory(memory_id, via_key_id=key_id, namespace) on the selected handle to confirm the fact and reinforce the path. Use limit/offset to page without flooding context.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Keymem Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "donggyun112-keymem": {
      "command": "npx",
      "args": [
        "-y",
        "keymem"
      ]
    }
  }
}

MCP Odoo Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tuanle96-mcp-odoo": {
      "command": "uvx",
      "args": [
        "odoo-mcp"
      ]
    }
  }
}

Frequently Asked Questions

Keymem is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, MCP Odoo belongs to Workplace & Productivity using local stdio subprocess. Select Keymem when you need capabilities focused on workplace & productivity and MCP Odoo when you require tools for workplace & productivity.

More alternatives to Keymem More alternatives to MCP Odoo Workplace & Productivity category hub