Qwen Memory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_STORE | No | Memory store type: 'memory', 'file', or 'mysql'. | memory |
| QWEN_API_KEY | No | API key for Qwen on Alibaba Cloud (DashScope). Falls back to offline deterministic intelligence if not set. | |
| MCP_TRANSPORT | No | Transport mode: 'stdio' or 'http'. | stdio |
| QWEN_BASE_URL | No | Optional base URL for Qwen API (e.g., for different region). | |
| MCP_AUTH_TOKEN | No | Bearer token for HTTP transport authentication. | |
| MEMORY_FILE_PATH | No | Path to JSON file when MEMORY_STORE is 'file'. |
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 |
|---|---|
| memory_writeA | Persist something worth remembering about a user (a preference, fact, commitment, or event). Qwen derives a short summary, tags, importance (salience), and kind. Call this whenever the user reveals durable information you should recall in future sessions. |
| memory_searchA | Semantic search over a user's memories, ranked by similarity, importance, recency, and how often each memory has been recalled. Returns the top matches. Recalled memories are reinforced. |
| memory_recall_contextB | Returns the most critical memories for a query, greedily packed to fit a token budget, as a ready-to-inject context block. Use this to load long-term memory into a limited context window before answering. |
| memory_forgetA | Runs the maintenance pass: clusters of related memories are merged by Qwen into one canonical memory, contradicted/outdated items are forgotten, and stale low-importance memories decay away. Returns a report of what was consolidated, archived, forgotten, and retained. |
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 4 tools
Each tool has a clearly distinct purpose: writing new memories, searching them, recalling context for a query, and running maintenance. No overlap in functionality.
All tool names follow a consistent 'memory_<verb>' pattern, making the action clear and predictable.
Four tools cover the core memory operations (write, search, recall, maintenance) without unnecessary bloat. The scope is appropriate for a memory management server.
Missing explicit update and list operations; however, the automatic maintenance and selective retrieval cover common use cases. Gaps exist for direct manipulation of individual memories.