Developer · Remote MCP server
Engram
Persistent, verbatim, searchable memory for AI assistants - one memory across every MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
app.getengram/engram- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-08
- Updated
- 2026-09-08
- Publisher
- app.getengram
- Namespace
- Namespace verified by the MCP Registry via the domain getengram.app · how
- Website
- getengram.app
- Repository
- github.com/get-engram/engram
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.getengram.app/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Engram
Engram is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.getengram.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| En301549 LintFlags the EN 301 549 clause each line breaks, and separates what is in force today from what arrives. | Local · stdio |
| EnergyatitConnect AI agents to energy infrastructure. Dispatch, attest carbon, read meters. | Local · stdio |
| Eng Leadership ToolkitEngineering leadership benchmarks, 1:1 playbooks, developer value calculator. 3,400+ sessions. | Remote · HTTPLive check: ✓ handshake |
| Engineering BoardRepository-owned engineering pattern intelligence - 19 MCP tools over stdio. | Local · stdio |
| EngramCognitive memory for coding agents: hybrid recall, remember/forget, knowledge graph, nightly dreams. | Local · stdio |
| EngramLocal-first persistent memory for AI agents - SQLite + local embeddings, MCP-native, no cloud. | Local · stdio |
| EngramRanked local code-graph context for AI coding agents. Intercepts reads + greps. Apache-2.0. | Local · stdio |
| EngramAgent memory with automatic extraction, consolidation, and bi-temporal recall. | Local · stdio |