MCP Servers · supermemoryai

supermemory-mcp

Supermemory MCP is a TypeScript-based Model Context Protocol server that syncs your conversation memories across multiple LLM applications without requiring login or payment. It integrates with the Supermemory cloud service (or self-hosted via API key) to enable universal memory portability across ChatGPT, Claude, and other MCP-compatible clients.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/supermemoryai/supermemory-mcp

1.7k

GitHub stars

173

Forks

TypeScript

Primary language

MIT

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	supermemoryai/supermemory-mcp
Owner	supermemoryai
Primary language	TypeScript
License	MIT — OSI-approved
Stars	1.7k
Forks	173
Open issues	10
Latest release	Unknown
Last updated	2025-12-30
Source	https://github.com/supermemoryai/supermemory-mcp

What supermemory-mcp is

An MCP server implementation that exposes Supermemory's API as callable tools for LLM clients, enabling persistent memory management across heterogeneous LLM platforms. Supports both cloud-hosted (no auth) and self-hosted (API-key authenticated) deployments via Cloudflare Workers or local execution.

Quickstart

Get the supermemory-mcp source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/supermemoryai/supermemory-mcp.git2cd supermemory-mcp3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-LLM Continuity

Teams or individuals using multiple LLM platforms (Claude, ChatGPT, Llama, etc.) who need shared conversation history and memory context without re-onboarding per platform.

AI Agent Memory Backend

Building autonomous agents or multi-turn systems that require persistent state across MCP-compliant clients, particularly in internal tools or enterprise automation scenarios.

Self-Hosted Agentic Systems

Organizations requiring air-gapped or on-premise LLM deployments with centralized memory management, using the self-hosted API key model to maintain control.

Implementation considerations

The project warns MCP v1 is deprecated; integration should reference the monorepo at supermemoryai/supermemory/apps/mcp for ongoing support and latest version.
Self-hosting requires Supermemory API credentials (console.supermemory.ai); cloud-hosted mode is passwordless but depends on external service availability.
MCP server setup is described as 'one command' for cloud mode; self-hosted requires .env configuration and API key management.
Memory persistence relies entirely on Supermemory backend; no local fallback or offline mode is documented.
TypeScript build and deployment via Node.js; ensure compatible runtime environment for your MCP client (Claude DXT, OpenAI plugins, etc.).

When to avoid it — and what to weigh

Strict Data Residency Requirements — If you need guaranteed on-premise storage, the default cloud-hosted mode (app.supermemory.ai) may not meet compliance requirements. Self-hosting requires separate API infrastructure.
Non-MCP LLM Ecosystems — If your primary LLM environment does not support the Model Context Protocol (older APIs, proprietary platforms), this tool provides no direct integration.
Production Stability Dependency — The README warns MCP v1 is deprecated; the main codebase has migrated to a monorepo. Production adoption should verify monorepo version stability and release cadence first.
High-Security / Zero-Trust Contexts — Reliance on third-party Supermemory infrastructure for memory storage introduces external dependency. No security audit data provided; requires vendor security review.

License & commercial use

MIT License. Permissive open-source license allowing commercial use, modification, and distribution with attribution and liability disclaimer.

MIT license permits commercial use without restriction. However, memory storage and inference rely on Supermemory cloud service (free tier available, commercial usage terms Unknown). Self-hosting shifts infrastructure cost to operator. Recommend reviewing Supermemory service ToS and pricing for production commercial deployments.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Moderate
Documentation	Limited
License clarity	Clear
Deployment complexity	Low
DEV.co fit	Good
Assessment confidence	Medium

Security considerations

Cloud-hosted mode delegates memory storage to external Supermemory service; no audit trail or encryption details provided. Self-hosted requires secure API key management (.env exposure risk). MCP protocol runs locally but depends on external backend. No security certifications, penetration test results, or incident response policy documented. Recommend vendor security review and API rate-limiting validation before production use.

Alternatives to consider

Mem0 (mem0.ai)

Alternative memory layer for LLMs with multi-provider support and persistent storage; more mature release history and documentation.

LangChain Memory (with PostgreSQL backend)

Framework-level memory abstraction compatible with multiple LLM providers; requires self-hosting and explicit chain integration but more transparent/auditable.

Embedbase or Qdrant

Vector DBs with MCP adapters for semantic memory retrieval; lower-level but offer more control over storage, encryption, and data residency.

Software development agency

Build on supermemory-mcp with DEV.co software developers

If you need multi-LLM memory continuity without vendor lock-in, Supermemory MCP offers a lightweight entry point. However, verify current stability via the monorepo, review Supermemory service SLAs, and assess self-hosting overhead before committing to production.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

servers mcp-server-qdrant MCP-SuperAssistant

Related on DEV.co

Explore the category and the services that help you build with it.

MCP Servers AI Application Development API Development Talk to DEV.co

supermemory-mcp FAQ

Is this deprecated?

MCP v1 is being deprecated. The maintainers direct new users to app.supermemory.ai and the monorepo version (supermemoryai/supermemory). This repo remains active but is considered legacy.

Can I use this without Supermemory cloud?

Yes. Self-hosting requires an API key from console.supermemory.ai and separate Supermemory backend infrastructure. Cloud mode requires no authentication but uses external service.

Which LLM clients are supported?

MCP v1 server works with any MCP-compatible client (Claude via DXT one-click, plus open-source frameworks). Older APIs (direct OpenAI, Anthropic) not directly supported; requires MCP client wrapper.

What happens to my memories if Supermemory service goes down?

Unknown. No SLA, uptime guarantees, or offline/fallback behavior documented. Self-hosting eliminates this risk but requires operator responsibility.

Software developers & web developers for hire

Need help beyond evaluating supermemory-mcp? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and mcp servers integrations — and maintain them long-term.

Evaluate Supermemory MCP for Your Memory-Persistent LLM Stack

Talk to DEV.co Schedule a Consultation