Developer · Local MCP server
Memory Journal MCP
Developer journal with knowledge graphs, relationships, Git context, and semantic search.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.neverinfamous/memory-journal-mcp- Version
- 1.1.3
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2025-10-13
- Updated
- 2025-10-13
- Publisher
- neverinfamous (GitHub) · 4 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/neverinfamous) · how
- Repository
- github.com/neverinfamous/memory-journal-mcp.git
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | docker.io/writenotenow/memory-journal-mcp:v1.1.3 | - | stdio |
How to connect Memory Journal MCP
Memory Journal MCP runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/writenotenow/memory-journal-mcp:v1.1.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm docker.io/writenotenow/memory-journal-mcp:v1.1.3.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"memory-journal-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/writenotenow/memory-journal-mcp:v1.1.3"
]
}
}
}Derived from the registry entry, not tested here. 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 from neverinfamous (GitHub)
| Server | Runs |
|---|---|
| PostgreSQL MCP ServerPostgreSQL MCP server with 203 tools, connection pooling, HTTP/SSE, OAuth 2.1, and tool filtering. | Local · stdio |
| PostgreSQL MCP ServerEnterprise PostgreSQL MCP server with 63 tools, 10 resources, 10 prompts for AI-native operations. | Local · stdio |
| Sqlite MCP ServerSQLite MCP server with 73 tools for JSONB, full-text search, geospatial, and analytics. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| MemoryShared, persistent memory for AI agents - works with Claude, Kiro, Cursor, or any MCP client. | Local · stdio |
| Memory FabricFile-first, local-first MCP memory for AI coding assistants: Markdown + YAML, no vector DB. | Local · stdio |
| Memory for AILocal codebase knowledge graph for AI agents - 162 languages, sub-ms queries, 99% fewer tokens. | Local · stdio |
| Memory FtsLong-term memory for Claude Code with SQLite FTS5 search and BM25 ranking. | Local · stdio |
| Memory KernelLocal-first memory for AI agents: SQLite FTS5, deterministic recall, no vector DB, no cloud. | Local · stdio |
| Memory MCPPersistent memory + git snapshots for Claude Code. Never lose context or code. | Local · stdio |
| Memory Poisoning ScannerScans agent code for untrusted input poisoning persistent cross-session memory. | Local · stdio |
| Memory VaultLocal-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT. | Local · stdio |