MCP Memory Graph vs Store API — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
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.
At a Glance & Executive Verdict
MCP Memory Graph
Finance & Fintech · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Store API
Finance & Fintech · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Memory Graph if you need specialized Finance & Fintech tools running via a local process. Choose Store API if your workspace requires Finance & Fintech integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
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.
MCP Memory Graph is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Store API belongs to Finance & Fintech using remote streaming HTTP/SSE transport. Select MCP Memory Graph when you need capabilities focused on finance & fintech and Store API when you require tools for finance & fintech.