Smara Memory MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMARA_API_KEY | Yes | Your Smara API key. Get a free key at smara.io. | |
| SMARA_API_URL | No | Smara API URL | https://api.smara.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| store_memoryA | Store a fact or preference about a user. Smara handles deduplication and contradiction detection automatically. Use importance 0.1-0.3 for trivia, 0.5 for general facts, 0.7-1.0 for critical preferences. |
| search_memoriesA | Semantic search across stored memories for a user. Ranked by Temporal Memory Scoring — balances semantic relevance with memory freshness and importance. When a team is configured, returns both private and team memories by default. |
| get_user_contextA | Retrieve a pre-formatted context string for a user, ready to inject into an LLM system prompt. Ranked by Temporal Memory Scoring. Can be called without a query to get the most important recent memories. When a team is configured, includes team memories automatically. |
| update_memoryA | Update a memory's visibility (private/team) or importance. Use when a user wants to make a memory private, share it with the team, or change its importance. Find the memory ID via search_memories or list_memories first. |
| list_memoriesA | List stored memories for a user with their visibility status (private or team). Use when the user wants to see what's remembered, review team vs private memories, or find a memory to update/delete. |
| delete_memoryA | Delete a specific memory by ID. Use when a user asks to forget something. |
| get_usageB | Check current memory usage — plan, limits, and how many memories are stored. Useful for monitoring quota. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.