mengram try # see what memory would know about you — local only, # no account, nothing leaves your machine ```
Mengram MCP server exists for a simple reason — assistants are far more useful when they can act on Mengram directly instead of describing what you should do. mengram try # see what memory would know about you — local only, # no account, nothing leaves your machine ```.
Once Mengram is connected, these are the calls the assistant has available:
Endpoint — DescriptionBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need one environment variable: MENGRAM_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mengram's toolset — Endpoint — is a fair guide to whether it matches your workflow. It is maintained by alibaizhanov; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Mengram's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Endpoint | Description |
{
"mcpServers": {
"mengram": {
"command": "npx",
"args": ["-y", "mengram-ai"],
"env": {
"MENGRAM_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| MENGRAM_API_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.