Noetive vs Engram
A side-by-side look at the Noetive and Engram MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Noetive for knowledge & memory work as a local process; choose Engram for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Noetive when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
NOETIVE_KEY_SECRET. - You want tools like
noetive_publish, noetive_search, noetive_subscribe.
Choose Engram when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You want tools like
create_conversation, append_messages, search.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 57/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | NOETIVE_KEY_SECRET | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 18 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 5 | 6 |
| Full listing | View Noetive | View Engram |
Tools & capabilities
Noetive tools 5
noetive_publishPublish a message so peers can find it by meaningnoetive_searchSearch a namespace with SemQL and read the matching messagesnoetive_subscribeWatch a namespace for live matches for a bounded windownoetive_lintCheck a SemQL query before running itnoetive_healthCheck that the editor can reach Noetive and its key is accepted
Engram tools 6
create_conversationStart a new conversation with optional title, tags, metadataappend_messagesAdd messages to an existing conversationsearchSemantic search across all conversationsget_conversationRetrieve a conversation with its messageslist_conversationsList conversations with filtering and paginationdelete_conversationRemove a conversation and its data
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Noetive
{
"mcpServers": {
"noetive": {
"command": "npx",
"args": [
"-y",
"@noetive/mcp-server"
],
"env": {
"NOETIVE_KEY_SECRET": "YOUR_NOETIVE_KEY_SECRET_HERE"
}
}
}
}
Engram
{
"mcpServers": {
"engram-2": {
"command": "npx",
"args": [
"-y",
"@getengram/cli"
]
}
}
}
Frequently asked questions
Noetive is categorized under Knowledge & Memory and uses a local stdio subprocess. Engram belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Noetive for knowledge & memory work and Engram for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Noetive is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Engram has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add noetive and engram-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Noetive has a quality signal of 57/100 (Good) with 0 views, 0 installs and 2 GitHub stars. Engram has 57/100 (Good) with 2 views, 0 installs and 18 GitHub stars.