Keepsake MCP vs Context Apps MCP

In-depth architectural comparison of the Keepsake MCP and Context Apps 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.

Which MCP Server Should You Choose?

Choose Keepsake MCP when:

• You need dedicated capabilities in the Workplace & Productivity domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: KEEPSAKE_API_KEY.
• Primary tools included: list_contacts, get_contact, create_contact.

Explore Keepsake MCP Details

Choose Context Apps MCP when:

• You need dedicated capabilities in the Workplace & Productivity domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: OAuth 2.0 (Free / Open Source).
• Primary tools included: todo_search, todo_insert, todo_update.

Feature & Specification Comparison

Specification	Keepsake MCP nicolascroce Workplace & Productivity	Context Apps MCP tubasasakunn Workplace & Productivity
Summary
Category & Scope	Workplace & Productivity	Workplace & Productivity

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "nicolascroce-keepsake-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "keepsake-mcp"
      ],
      "env": {
        "KEEPSAKE_API_KEY": "YOUR_KEEPSAKE_API_KEY_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "tubasasakunn-context-apps-mcp": {
      "url": "https://mcp-server.basaapp.com/mcp"
    }
  }
}

Related MCP Server Comparisons