PowerMem MCP Server
PowerMem MCP Server - Model Context Protocol server for PowerMem memory management.
English | 简体中文
Startup
Support for multiple types of MCP
You can start PowerMem MCP with different protocols using the following commands:
uvx powermem-mcp sse # sse mode, default port 8000 (recommended)
uvx powermem-mcp stdio # stdio mode
uvx powermem-mcp sse 8001 # sse mode, specify port 8001
uvx powermem-mcp streamable-http # streamable-http mode, default port 8000
uvx powermem-mcp streamable-http 8001 # streamable-http mode, specify port 8001
Usage
Use with MCP Client, must use a client that supports Prompts, such as: Claude Desktop. Before entering a request, you need to manually select the required Prompt, then enter the request.
Claude Desktop config example:
{
"mcpServers": {
"powermem": {
"url": "http://{host}:8000/mcp"
}
}
}
Available Tools
The PowerMem MCP Server provides the following memory management tools:
- add_memory: Add new memory to storage. Supports string, message dict, or message list format. Can use intelligent mode for automatic inference.
- search_memories: Search memories by query text with optional filters, limit, and similarity threshold.
- get_memory_by_id: Get a specific memory by its ID.
- update_memory: Update the content and metadata of an existing memory.
- delete_memory: Delete a specific memory by its ID.
- delete_all_memories: Batch delete memories by user_id, agent_id, or run_id.
- list_memories: List all memories with pagination support (limit and offset) and optional filters.
Community
When you need help, you can find developers and other community partners at https://github.com/oceanbase/powermem.
When you discover project defects, please create a new issue on the issues page.
License
For more information, see LICENSE.
Release files for powermem-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| powermem_mcp-0.2.0.tar.gz | 14.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| powermem_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.0 kB
Release files / powermem_mcp-0.2.0.tar.gz
| Download URL | powermem_mcp-0.2.0.tar.gz |
|---|---|
| Size | 14.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ed8ce9444fcf538051a20e2e426a2bedad971a4e668438c36a45564a5032f89
|
|
BLAKE2b-256 checksum How to use checksums |
080a13dd308860feb4ff35b73741c7b01f1bdd7e759b56eb9d6b0b91af8c0e7f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 8, 2026.
Transparency logRelease files / powermem_mcp-0.2.0-py3-none-any.whl
| Download URL | powermem_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 13.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8230e219370b9acaab6ffc5b726255dbd23fed38a956a251e23d4666fa9621ad
|
|
BLAKE2b-256 checksum How to use checksums |
1d4a47c1b085af93a2e6edeb136084454c8f21ca16f3129dd40d50095a778b89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 8, 2026.
Transparency log