SOKI (想起) — Personal Memory vs AIMEAT

In-depth architectural comparison of the SOKI (想起) — Personal Memory and AIMEAT 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?

S

Choose SOKI (想起) — Personal Memory when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore SOKI (想起) — Personal Memory Details

Choose AIMEAT when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore AIMEAT Details

Feature & Specification Comparison

Specification	S SOKI (想起) — Personal Memory Knowledge & Memory	AIMEAT Knowledge & Memory
Summary	Personal memory outside the AI. Due dates, loose ends and old notes come back on their own.	Persistent memory, identity, shared workspaces, skills and tasks for AI agents
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

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": {
    "soki-personal-memory": {
      "command": "npx",
      "args": [
        "-y",
        "soki-personal-memory"
      ]
    }
  }
}

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

Related MCP Server Comparisons