Integration
Long-term memory for Dify
Dify is the no-code platform for shipping LLM apps (Agents, Chatflows, Workflows). The Lumetra-maintained `lumetra/engram` plugin adds six native memory tools to the catalog: install, Authorize with your Engram key, and drag them into any flow. No MCP bridge in the loop, and no community-plugin dependency to chase.
Install
Three steps: sign up for an Engram API key, paste a BYOK LLM-provider key on /models, then drop the snippet below into Dify.
Three steps to memory in your agent
- Sign up. Free, no card. You'll land on a Getting Started page that walks the next two steps.
- Add your LLM key. Engram is BYOK. Paste an OpenAI / Anthropic / Groq / Together / Fireworks key and we'll route every extraction and query call through your provider. You pay your provider directly. We never see your inference.
- Paste the snippet below into your agent and restart it. Use
Authorization: Bearer <api-key>with the API key from your portal.
engram-dify: first-party Marketplace plugin
Six native Dify tools (store_memory, query_memory, and four more) call the hosted Engram REST API directly. No MCP bridge, no servers_config JSON, no community-plugin dependency. Source: github.com/lumetra-io/engram-dify.
- In your Dify console, open Plugins → Marketplace, search for Engram, and install the
lumetra/engramplugin. - Open Plugins → Installed → Engram, click Authorize, and paste your
eng_live_…API key. - The six Engram tools appear in the tool catalog and can be added to any Agent, Chatflow, or Workflow.
Self-hosting Engram? Set the Engram API Base URL field in the Authorize dialog to your endpoint (e.g. https://engram.internal.example.com).
What you can do once memory's wired in
- Build a chatbot in the Dify visual editor and give it durable memory in five clicks
- Add `engram_query_memory` to a Chatflow so the bot grounds every reply in stored user facts
- Add `engram_store_memory` to a Workflow that auto-captures specific event types
- Run Dify multi-tenant: each customer gets their own bucket via a per-tenant Engram key
FAQ
Is this the community `dify-plugin-tools-mcp_sse` plugin?
No, that's a generic MCP shim. The Engram plugin is Lumetra-maintained and calls Engram's REST API directly with six native tools, no MCP bridge involved.
How do I install it today?
The Marketplace listing is pending Dify's review process. Until it's approved, install from the GitHub repo as a local plugin: download the `.difypkg` from [github.com/lumetra-io/engram-dify/releases](https://github.com/lumetra-io/engram-dify/releases) and upload it via **Plugins → Install from local package** in your Dify console. Once the Marketplace listing is live we'll update this page to point at it.
Where does the API key live?
In the plugin's Authorize dialog, stored by Dify in its plugin credential store. Each Dify workspace can have its own key.
Can I self-host Engram and point the plugin at my own instance?
Yes. The Authorize dialog has an `Engram API Base URL` field; set it to your endpoint (e.g. `https://engram.internal.example.com`) and the plugin uses that for all calls.
Related integrations
Ship durable memory in Dify today
Free tier: 10K memories and 50K retrievals per month. No credit card. Same Engram backend powers all 41 integrations, so memories you write from one client are immediately queryable from the rest.