MCP Memory Graph vs Store API

In-depth architectural comparison of the MCP Memory Graph and Store API 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 MCP Memory Graph when:

• You need dedicated capabilities in the Finance & Fintech domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Freemium).
• Primary tools included: SQLite-based persistent local memory, Hybrid semantic and keyword search, Knowledge graph for linked entities and memories.

Explore MCP Memory Graph Details

S

Choose Store API when:

• You need dedicated capabilities in the Finance & Fintech domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: ask_model, list_models, generate_image.

Explore Store API Details

Feature & Specification Comparison

Specification	MCP Memory Graph Finance & Fintech	S Store API Finance & Fintech
Summary	Local-first memory for Claude Code and any MCP client: hybrid search + knowledge graph, $0/token.	GPT, Claude, Gemini, DeepSeek, Grok, Qwen and GLM through one API key. Pay per token.
Category & Scope	Finance & Fintech	Finance & Fintech

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

{
  "mcpServers": {
    "store-api": {
      "url": "https://store-api.com/mcp"
    }
  }
}

Related MCP Server Comparisons