Generic MCP Client
Use this guide for Claude Desktop, Cline, Codex, OpenCode, Roo Code, Goose, or any other MCP client that accepts a standard MCP server definition.
Prerequisites
- PowerMem installed with MCP support. Use
powermem[mcp,seekdb]for zero-config local seekdb, orpowermem[mcp]when your.envpoints at non-seekdb storage/embedder providers. - PowerMem configured with your LLM provider, API key, and model.
Start an MCP server
Choose one transport.
Stdio
Use stdio when the client can launch a local command:
powermem-mcp stdio
Client config shape:
{
"mcpServers": {
"powermem": {
"command": "powermem-mcp",
"args": ["stdio"]
}
}
}
Streamable HTTP
Use streamable HTTP for remote or long-running MCP:
powermem-mcp streamable-http 8848
Client config shape:
{
"mcpServers": {
"powermem": {
"url": "http://localhost:8848/mcp"
}
}
}
SSE
Use SSE when the client specifically expects SSE:
powermem-mcp sse 8848
Use the same URL shape:
{
"mcpServers": {
"powermem": {
"url": "http://localhost:8848/mcp"
}
}
}
OpenCode stores the same server under mcp.powermem instead of
mcpServers.powermem; see OpenCode for the exact JSON shape.
Exposed tools
PowerMem exposes core memory tools:
add_memorysearch_memoriesget_memory_by_idupdate_memorydelete_memorydelete_all_memorieslist_memories
It also exposes user-profile tools when supported by the client.
Verify
- Reload the MCP client.
- Confirm the
powermemserver is connected. - Confirm the tools above are listed.
- Add and search a probe memory containing
dragonfruit-zx9.
Troubleshooting
- If stdio fails, confirm
powermem-mcp stdiostarts from the same environment where you installed PowerMem. - If remote MCP fails, confirm the URL and port match the transport you started.
- If auth is enabled, pass
POWERMEM_API_KEYthrough env for stdio or configure headers for remote MCP. - If memory operations fail, check
.env, LLM provider, embedding provider, and server logs.
Uninstall
Remove only the powermem MCP server entry from your client config, then reload the client.