Ecosystem Integrations
First-party integrations that connect PowerMem to AI clients, IDEs, and agent
frameworks. Every integration points at the same backend (the HTTP API server or
the local pmem CLI) — there are no per-client schema rewrites.
AI clients & IDEs
- Claude Code — Plugin (
memory-powermem) with silent HTTP-mode capture via hooks and an optional MCP mode for in-chatsearch_memories/add_memorytools. - VS Code — First-party extension with setup UI, status bar, query/add commands, dashboard, and AI-tool config linking.
- Cursor — MCP setup through the VS Code extension, writing
~/.cursor/mcp.json. - Windsurf — MCP or HTTP context setup through
~/.windsurf/context/powermem.json. - GitHub Copilot — Provider config through
~/.github/copilot/powermem.json. - Qoder — Manual MCP setup for Qoder IDE or Qoder CLI.
- OpenClaw —
memory-powermemplugin with local CLI mode and optional HTTP backend mode. - Cline — Standard MCP setup for Cline.
- Generic MCP client — Stdio, streamable HTTP, and SSE setup for Claude Desktop, Cline, Codex, OpenCode, Roo Code, Goose, and other MCP clients.
Frameworks & SDKs
- LangChain and LangGraph — Persistent memory patterns for LCEL chains and LangGraph workflows.
For FastAPI and custom LLM / embedding / storage providers, see the Integrations Guide.
See also
- Getting Started — install,
.env, firstMemoryusage - MCP API — Model Context Protocol server
- HTTP API Server — REST endpoints used by the integrations