Engram Mcp Server

Created By
lumetra-io8 months ago
Give your AI agents a memory they can trust. Engram lets your AI remember past conversations, facts, and decisions, so it feels more like a real teammate. This repository contains configuration templates for connecting MCP clients to Engram, a hosted memory service for AI agents.
Overview

What is Engram?

Engram is a hosted memory service for AI agents that allows them to remember past conversations, facts, and decisions, making interactions feel more like working with a real teammate.

How to use Engram?

To use Engram, sign up at lumetra.io to get your API key, then connect it to your MCP client by following the provided setup instructions for various clients like Claude Code, Windsurf, and Cursor.

Key features of Engram?

  • Reliable memory for AI agents to recall past interactions.
  • Easy setup with quick integration into various MCP clients.
  • Built-in controls for managing memory retention and cleanup.

Use cases of Engram?

  1. Providing support with prior context for customer service agents.
  2. Enhancing code reviews by storing relevant notes and decisions.
  3. Centralizing shared metric definitions for teams.
  4. Ensuring consistent on-brand content creation.

FAQ from Engram?

  • Is Engram free to use?

Yes! Engram is free during its public beta phase, and no credit card is required.

  • What clients are compatible with Engram?

Engram works with various MCP clients including Claude Code, Windsurf, and Cursor.

  • How does Engram ensure memory reliability?

Engram allows agents to remember conversations and decisions, providing explanations for their responses.

Server Config

{
  "mcpServers": {
    "engram": {
      "url": "https://engram.lumetra.io",
      "headers": {
        "X-API-Key": "<your-api-key>"
      }
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
lumetra-io
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

10 hours ago