Smara Memory MCP Server
# @smara/mcp-server
MCP server for the [Smara Memory API](https://smara.io) — give any AI app persistent memory with Temporal Memory Scoring™.
## Quick Start
Add to your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json`):
```json
{
"mcpServers": {
"smara": {
"command": "npx",
"args": ["-y", "@smara/mcp-server"],
"env": {
"SMARA_API_KEY": "your-api-key-here"
}
}
}
}
```
Get a free API key at [smara.io](https://smara.io) (10,000 memories, no credit card).
## Tools
| Tool | Description |
|------|-------------|
| `store_memory` | Store a fact about a user with importance scoring |
| `search_memories` | Semantic search with Temporal Memory Scoring™ |
| `get_user_context` | Pre-formatted context string for LLM system prompts |
| `delete_memory` | Delete a specific memory |
| `get_usage` | Check plan limits and memory count |
## How It Works
Smara uses **Temporal Memory Scoring™** — a proprietary ranking system that makes AI memory work like human recall. Memories naturally fade over time, modulated by importance and access patterns. Recent, critical memories surface first. Stale, trivial ones fade. Contradictions are auto-detected and resolved.
## Works With
- Claude Desktop
- Claude Code
- Cursor
- Windsurf
- VS Code (GitHub Copilot)
- Any MCP-compatible client
## Environment Variables
| Variable | Required | Default |
|----------|----------|---------|
| `SMARA_API_KEY` | Yes | — |
| `SMARA_API_URL` | No | `https://api.smara.io` |
## License
MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap. For example, 'list_memories' shows stored memories, 'search_memories' performs semantic search, 'store_memory' creates new memories, 'update_memory' modifies existing ones, 'delete_memory' removes memories, 'get_user_context' retrieves formatted context, and 'get_usage' monitors system usage. The descriptions reinforce these unique roles, eliminating any ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'list_memories', 'search_memories', 'store_memory', 'update_memory', 'delete_memory', 'get_user_context', and 'get_usage'. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 7 tools, this server is well-scoped for a memory management system. The count is appropriate as it covers essential operations like CRUD (create, read, update, delete), search, context retrieval, and usage monitoring without being excessive or insufficient. Each tool serves a clear, necessary function in the domain.
The tool set provides complete coverage for memory management, including storing, listing, searching, updating, deleting, retrieving context, and monitoring usage. There are no obvious gaps; it supports full lifecycle management from creation to deletion, with additional utilities for context and system health, ensuring agents can handle all typical workflows without dead ends.