What is the key difference between Keymem and Ews Meeting MCP?

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

How do I install Keymem or Ews Meeting MCP 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 Ews Meeting MCP free or paid?

Keymem operates under a Free / Open Source model (No auth required). Ews Meeting MCP 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. Ews Meeting MCP lists 21 tools with 4 views and 3 GitHub stars.

Can I use both Keymem and Ews Meeting MCP 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 Ews Meeting MCP

In-depth architectural comparison of the Keymem and Ews Meeting MCP 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

Ews Meeting MCP

Workplace & Productivity · Local stdio

Quality: 63/100 (Good) | Auth: other

Verdict Summary: Choose Keymem if you need specialized Workplace & Productivity tools running via a local process. Choose Ews Meeting MCP 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 Ews Meeting MCP 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).
You have access to required keys: EWS_ENDPOINT, EWS_EMAIL, EWS_USERNAME, EWS_AUTH_TYPE, EWS_TIMEZONE, ACCOUNT_PASSWORD, ACCOUNT_PASSWORD_KEYCHAIN_SERVICE, ACCOUNT_PASSWORD_KEYCHAIN_ACCOUNT.
Primary tools included: ews_keychain_status, ews_setup_check, ews_signature_setup_guide.

Feature & Specification Comparison

Specification	Keymem donggyun112 Workplace & Productivity	Ews Meeting MCP ap311036 Workplace & Productivity
Summary	Associative key-graph memory for LLM agents — recall by association, not vector similarity.	Safely schedule Outlook meetings on on-prem Exchange EWS. Resolves attendees, discovers rooms, suggests slots, and requires preview-confirmed create/update/cancel writes with local credential handling and audit-friendly lifecycle records.
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"
      ]
    }
  }
}

Ews Meeting MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ap311036-ews-meeting-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ews-meeting-mcp"
      ],
      "env": {
        "EWS_ENDPOINT": "YOUR_EWS_ENDPOINT_HERE",
        "EWS_EMAIL": "YOUR_EWS_EMAIL_HERE",
        "EWS_USERNAME": "YOUR_EWS_USERNAME_HERE",
        "EWS_AUTH_TYPE": "YOUR_EWS_AUTH_TYPE_HERE",
        "EWS_TIMEZONE": "YOUR_EWS_TIMEZONE_HERE",
        "ACCOUNT_PASSWORD": "YOUR_ACCOUNT_PASSWORD_HERE",
        "ACCOUNT_PASSWORD_KEYCHAIN_SERVICE": "YOUR_ACCOUNT_PASSWORD_KEYCHAIN_SERVICE_HERE",
        "ACCOUNT_PASSWORD_KEYCHAIN_ACCOUNT": "YOUR_ACCOUNT_PASSWORD_KEYCHAIN_ACCOUNT_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Keymem More alternatives to Ews Meeting MCP Workplace & Productivity category hub Canonical compare URL