A previous release had provenance metadata, but this release does not. View details.
Engram Notion MCP - Semantic Memory for AI Agents
Engram Notion MCP is a powerful Model Context Protocol (MCP) server that gives your AI agents a permanent, semantic memory. It seamlessly integrates with Notion to store, retrieve, and organize information, turning your workspace into an intelligent knowledge base.
🧠 Why Engram? AI Agents often suffer from amnesia. Engram solves this by providing a persistent memory layer backed by Notion's robust database structure.
📦 Features
Notion Integration
| Feature | Tool Name | Description |
|---|---|---|
| Page Creation | create_page |
Create new pages with content. Auto-chunks large text to avoid limits. |
| Page Updates | update_page |
Append content to existing pages. Auto-chunks large text. |
| Logging | log_to_notion |
Fast logging wrapper for appending notes/logs. |
| Reading | read_page_content |
Read and parse page content into Agent-friendly text. |
| Databases | list_databases |
detailed list of accessible databases. |
| Querying | query_database |
Query databases with filters to find specific items. |
| Organization | list_sub_pages |
List pages within a parent page. |
| Cleanup | delete_block |
Archive/Delete blocks or pages. |
Semantic Memory (SQLite)
| Feature | Tool Name | Description |
|---|---|---|
| Store Facts | remember_fact |
Saves key info to internal vector-like storage. |
| Search | search_memory |
Full-text search over stored memories. |
| Recall | get_recent_memories |
Retrieve the latest context/facts. |
Operations
| Feature | Tool Name | Description |
|---|---|---|
| Alerts | send_alert |
Send push notifications via Telegram. |
🛠 Configuration
To use Engram Notion MCP, you need to set up your environment variables.
| Variable | Required | Description |
|---|---|---|
NOTION_API_KEY |
Yes | Your Notion Internal Integration Token (secret_...). |
NOTION_PAGE_ID |
No | Default Page ID for creating pages if no parent is specified. |
TELEGRAM_BOT_TOKEN |
No | For send_alert tool. |
TELEGRAM_CHAT_ID |
No | For send_alert tool. |
AGENT_MEMORY_PATH |
No | Custom path for the SQLite memory database. |
💡 Quick Setup Tips
🔑 How to get Notion API Key
- Go to Notion My Integrations.
- Click New integration.
- Name it (e.g., "Engram Notion MCP") and submit.
- Copy the Internal Integration Secret. this is your
NOTION_API_KEY.🤖 How to get Telegram Bot Token & Chat ID
Bot Token:
- Open Telegram and search for @BotFather.
- Send the command
/newbot.- Follow the prompts to name your bot.
- Copy the HTTP API Token.
Chat ID:
- Search for @userinfobot in Telegram.
- Click Start or send
/start.- It will reply with your Id. Copy this number.
Configuration Patterns
1. Minimal Setup (Flexible / Unbound)
You can omit NOTION_PAGE_ID to keep the agent "unbound". It will force the agent to ask for a destination or search for one.
"env": {
"NOTION_API_KEY": "secret_your_key_here"
}
2. Multi-Page Support
You don't need to configure an array of IDs. Engram relies on Notion's native permissions. To give the agent access to multiple specific pages:
- Open any page in Notion.
- Click the ... (three dots) menu (top-right) -> Connections.
- Look for the name you gave your integration (e.g., "Engram Notion MCP").
- Once connected, the agent can automatically see this page using the
list_accessible_pagestool. - Repeat this for any other page you want the agent to see.
🔌 Installation & Client Setup Instructions
⚡ Recommended (Fastest) - Bun
Use bunx to run the server with native performance (bun:sqlite).
Add this to your claude_desktop_config.json or mcp.json.
Config using bunx (Recommended):
{
"mcpServers": {
"engram-notion-mcp": {
"command": "bunx",
"args": ["engram-notion-mcp"],
"env": {
"NOTION_API_KEY": "secret_your_key_here"
}
}
}
}
🐢 Standard - Node.js (NPX)
Works with any standard Node.js environment (better-sqlite3).
Add this to your claude_desktop_config.json or mcp.json.
Config using npx (Standard):
{
"mcpServers": {
"engram-notion-mcp": {
"command": "npx",
"args": ["-y", "engram-notion-mcp"],
"env": {
"NOTION_API_KEY": "secret_your_key_here"
}
}
}
}
🐍 Alternative - Python (UVX / PIPX)
If you prefer uvx or pipx or have strict Python environments:
Add this to your claude_desktop_config.json or mcp.json.
Config using uvx (Alternative):
{
"mcpServers": {
"engram-notion-mcp": {
"command": "uvx",
"args": ["engram-notion-mcp"],
"env": {
"NOTION_API_KEY": "secret_your_key_here"
}
}
}
}
Config using pipx (Alternative):
{
"mcpServers": {
"engram-notion-mcp": {
"command": "pipx",
"args": ["run", "engram-notion-mcp"],
"env": { ... }
}
}
}
Where to put it:
-
🖥️ Desktop Apps (Claude Desktop):
claude_desktop_config.json -
🆚 VS Code / Cursor / Windsurf: User Settings (
settings.json). -
Cline / Roo Code: Extension Settings -> MCP Servers.
-
Kilo Code:
.kilo/config.json. -
⌨️ Gemini CLI:
Bun (Recommended)
gemini mcp add engram-notion-mcp bunx "engram-notion-mcp" -e NOTION_API_KEY=<your_secret_key>
Node.js - NPX (Standard)
gemini mcp add engram node "npx engram-notion-mcp" -e NOTION_API_KEY=<your_secret_key>
💬 Support & Feedback
If you face any issues or have suggestions, please feel free to:
- Open an issue on this GitHub Repository.
- Reach out to me directly via my GitHub profile.
Quick Links
This MCP tool is published as a package on NPM and PyPI.
Metadata
Release files for engram-notion-mcp 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| engram_notion_mcp-1.1.1.tar.gz | 11.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| engram_notion_mcp-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.7 kB
Release files / engram_notion_mcp-1.1.1.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | engram_notion_mcp-1.1.1.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
65b69928835873189330d8cf6a3175a07dc0a12a1b33b7c33404d5f522809828
|
|
BLAKE2b-256 checksum How to use checksums |
0d316d17bf2e64c9d1fbbd6f6c4dc3959879d014e9a6ebaefd4715a6bc01d446
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.16 {"installer":{"name":"uv","version":"0.9.16","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / engram_notion_mcp-1.1.1-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | engram_notion_mcp-1.1.1-py3-none-any.whl |
|---|---|
| Size | 12.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ed21f2704f5419423981ca37e30814d6a8504fcf9680ba38b054fa61aa6c2be
|
|
BLAKE2b-256 checksum How to use checksums |
facad05c59b2110f19215ffea9cc2bc94c54344dd15c3d5d77f6de42040ab8c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.16 {"installer":{"name":"uv","version":"0.9.16","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for engram-notion-mcp 1.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 1.2.0rc2 2 files With provenance
- Added 1.1.1 2 files Without provenance
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.