Skip to content
Agentmart
Submit a tool

Memory Journal MCP

Developer journal with knowledge graphs, relationships, Git context, and semantic search

Connector by neverinfamous · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 20
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/neverinfamous-memory-journal-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Developer journal with knowledge graphs, relationships, Git context, and semantic search

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
38 read · 28 write · 7 delete
Secrets
None asked for
Install scripts
Not scanned yet
Runs as
Docker image

Tools by what they do 73

Read from the source code; the running server may list different tools.

Read 38 · Look things up without changing anything.

  • export_entries
  • get_copilot_reviews
  • get_cross_project_insights
  • get_entry_by_id
  • get_github_context
  • get_github_issue
  • get_github_issues
  • get_github_milestone
  • get_github_milestones
  • get_github_pr
  • get_github_prs
  • get_kanban_board
Show 26 more tools
  • get_recent_entries
  • get_repo_insights
  • get_statistics
  • get_vector_index_stats
  • list_backups
  • list_tags
  • search_by_date_range
  • search_entries
  • semantic_search
  • team_export_entries
  • team_get_collaboration_matrix
  • team_get_cross_project_insights
  • team_get_entry_by_id
  • team_get_flag_analytics
  • team_get_recent
  • team_get_statistics
  • team_get_vector_index_stats
  • team_list_backups
  • team_list_flags
  • team_list_tags
  • team_search
  • team_search_by_date_range
  • team_semantic_search
  • team_visualize_relationships
  • test_simple
  • visualize_relationships

Write 28 · Create, change, send or run things.

  • add_kanban_item
  • add_to_vector_index
  • backup_journal
  • close_github_issue_with_entry
  • create_entry
  • create_entry_minimal
  • create_github_issue_with_entry
  • create_github_milestone
  • export_markdown
  • import_markdown
  • link_entries
  • merge_tags
Show 16 more tools
  • move_kanban_item
  • rebuild_vector_index
  • team_add_to_vector_index
  • team_backup
  • team_create_entry
  • team_export_markdown
  • team_import_markdown
  • team_link_entries
  • team_merge_tags
  • team_pass_flag
  • team_rebuild_vector_index
  • team_resolve_flag
  • team_update_entry
  • team_update_flag
  • update_entry
  • update_github_milestone

Delete 7 · Delete, drop, revoke or wipe things.

  • cleanup_backups
  • delete_entry
  • delete_github_milestone
  • delete_kanban_item
  • mj_execute_code
  • restore_backup
  • team_delete_entry

Files it touches

  • Any path the agent passes to its tools

Tools (73)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • add_kanban_itemAdd Kanban Item

    Add an existing GitHub Issue or Pull Request to a Kanban board (GitHub Project v2). Returns the project item ID on success.

  • add_to_vector_indexAdd Entry to Vector Index

    Add a specific entry to the semantic search vector index

  • backup_journalBackup Journal Database

    Create a timestamped backup of the journal database. Backups are stored in the backups/ directory.

  • cleanup_backupsCleanup Old Backups

    Delete old backup files, keeping only the most recent N backups. Use list_backups to preview before cleanup.

  • close_github_issue_with_entryClose GitHub Issue with Resolution Entry

    Close a GitHub issue AND create a journal entry documenting the resolution.

  • create_entryCreate Journal Entry

    Create a new personal journal entry. MANDATORY: After creating, always attempt to causally link new entries to prior context (evolves_from, implements, blocked_by, resolved) using link_entries.

  • create_entry_minimalCreate Entry (Minimal)

    Minimal entry creation without context or tags

  • create_github_issue_with_entryCreate GitHub Issue with Journal Entry

    Create a GitHub issue AND automatically create a linked journal entry documenting the issue creation.

  • create_github_milestoneCreate GitHub Milestone

    Create a new GitHub milestone for tracking progress toward a project goal.

  • delete_entryDelete Entrycan change or delete data

    Delete a journal entry (soft delete with timestamp). Calling with permanent: true on a previously soft-deleted entry works. Returns success: false for nonexistent entries.

  • delete_github_milestoneDelete GitHub Milestonecan change or delete data

    Permanently delete a GitHub milestone. Issues assigned to the milestone will be un-assigned but not deleted.

  • delete_kanban_itemDelete Kanban Item

    Remove an item from a GitHub Kanban board cleanly. This untethers it from the project but does NOT close or delete the underlying Issue/PR.

  • export_entriesExport Entriesread-only

    Export journal entries to JSON or Markdown format

  • export_markdownExport to Markdown Files

    Export journal entries as individual frontmattered Markdown files (.md). Each file contains YAML frontmatter (mj_id, entry_type, tags, relationships) and the entry content. Files can be edited externally and re-imported via import_markdown.

  • get_copilot_reviewsGet Copilot Code Reviewsread-only

    Get Copilot's code review findings for a pull request. Returns review state (approved/changes_requested/commented/none) and file-level comments with paths and line numbers. Use to learn from Copilot's review patterns and create journal entries with tag "copilot-finding".

Show 58 more tools
  • get_cross_project_insightsGet Cross-Project Insightsread-only

    Analyze patterns across all GitHub Projects tracked in journal entries. Use for architecture planning.

  • get_entry_by_idGet Entry by IDread-only

    Get a specific journal entry by ID with full details

  • get_github_contextGet GitHub Repository Contextread-only

    Get current repository context including branch, open issues, and open PRs. IMPORTANT: Leave owner/repo empty to auto-detect from git, OR specify the repository name if working in a multi-project registry.

  • get_github_issueGet GitHub Issue Detailsread-only

    Get detailed information about a specific GitHub issue. IMPORTANT: Do NOT guess owner/repo values - leave them empty to auto-detect from the current git repository.

  • get_github_issuesGet GitHub Issuesread-only

    List issues from a GitHub repository. IMPORTANT: Do NOT guess owner/repo values - leave them empty to auto-detect from the current git repository.

  • get_github_milestoneGet GitHub Milestone Detailsread-only

    Get detailed information about a specific GitHub milestone including progress and linked issue counts.

  • get_github_milestonesList GitHub Milestonesread-only

    List GitHub milestones for the repository with completion percentages and due dates.

  • get_github_prGet GitHub PR Detailsread-only

    Get detailed information about a specific GitHub pull request, including live prStatus. IMPORTANT: Do NOT guess owner/repo values - leave them empty to auto-detect from the current git repository.

  • get_github_prsGet GitHub Pull Requestsread-only

    List pull requests from a GitHub repository. IMPORTANT: Do NOT guess owner/repo values - leave them empty to auto-detect from the current git repository.

  • get_kanban_boardGet Kanban Boardread-only

    View a GitHub Project v2 as a Kanban board with items grouped by Status column. Returns all columns with their items.

  • get_recent_entriesGet Recent Entriesread-only

    Get recent journal entries

  • get_repo_insightsRepository Insightsread-only

    Get repository insights: stars, forks, traffic (clones/views), referrers, and popular paths. Use "sections" to control token usage: stars (~50 tokens), traffic (~100), referrers (~100), paths (~100), or all (~350).

  • get_statisticsGet Statisticsread-only

    Get journal statistics and analytics (Phase 2: includes project breakdown)

  • get_vector_index_statsGet Vector Index Statsread-only

    Get statistics about the semantic search vector index

  • import_markdownImport from Markdown Files

    Import frontmattered Markdown files (.md) into the journal. If a file has an mj_id in its frontmatter and the entry exists, it is updated. Otherwise, a new entry is created. Tags and relationships are reconciled automatically. Use dry_run: true to preview what would happen without writing.

  • link_entriesLink Entries

    Create a relationship between two journal entries

  • list_backupsList Journal Backupsread-only

    List all available backup files with their sizes and creation dates

  • list_tagsList Tagsread-only

    List all available tags. Tags are auto-formatted to kebab-case. Returns only name and count. Does not return orphan tags with zero usage.

  • merge_tagsMerge Tags

    Merge one tag into another to consolidate similar tags (e.g., merge "phase-2" into "phase2"). The source tag is deleted after merge. Only updates non-deleted entries.

  • mj_execute_codeExecute Code (Code Mode)

    Description is built at runtime.

  • move_kanban_itemMove Kanban Item

    Move a Kanban item to a different status column. Requires the project board to have a Status field.

  • rebuild_vector_indexRebuild Vector Index

    Rebuild the semantic search vector index from all existing entries

  • restore_backupRestore Journal from Backupcan change or delete data

    Restore the journal database from a backup file. WARNING: This replaces all current data. Enforce single-writer / single-instance only for restore-capable deployments. An automatic backup is created before restore.

  • search_by_date_rangeSearch by Date Rangeread-only

    Search journal entries within a date range with optional filters

  • search_entriesSearch Entriesread-only

    Search journal entries. Use sort_by: "importance" to surface structurally significant entries before major decisions. Supports modes: auto (default), fts, semantic, hybrid. Optional filters for GitHub Projects, Issues, PRs, and Actions. FTS5 syntax: "exact phrase", prefix*, OR/NOT/AND. Word-boundary matched. Automatically merges team DB results when TEAM_DB_PATH is configured.

  • semantic_searchSemantic Searchread-only

    Perform semantic/vector search on journal entries using AI embeddings. Supports find-related-by-ID (entry_id) and metadata filters (tags, entry_type, date range). Threshold default is 0.25 (try 0.15-0.2 for broader matches, 0.4+ for strict matches). Entries are auto-indexed on creation. If index drifts, use rebuild_vector_index.

  • team_add_to_vector_indexAdd Team Entry to Vector Index

    Add a specific team entry to the semantic search vector index. Requires TEAM_DB_PATH.

  • team_backupBackup Team Database

    Create a timestamped backup of the team database. Requires TEAM_DB_PATH.

  • team_create_entryCreate Team Entry

    Create an entry in the team database for sharing with collaborators. ONLY use when explicitly requested by the user. Default to personal create_entry instead. Requires TEAM_DB_PATH.

  • team_delete_entryDelete Team Entrycan change or delete data

    Soft-delete a team entry (marks as deleted, preservable). Calling with permanent: true on a previously soft-deleted entry works. Returns success: false for nonexistent entries. Requires TEAM_DB_PATH.

  • team_export_entriesExport Team Entriesread-only

    Export team entries in JSON or Markdown format with optional date range, type, and tag filters. Requires TEAM_DB_PATH.

  • team_export_markdownTeam Export to Markdown

    Export team entries as frontmattered Markdown files

  • team_get_collaboration_matrixTeam Collaboration Matrixread-only

    Analyze cross-author collaboration: activity heatmap per period, cross-linking patterns between authors, and impact factor (inbound links). Requires TEAM_DB_PATH.

  • team_get_cross_project_insightsTeam Cross-Project Insightsread-only

    Analyze patterns across all GitHub Projects tracked in team entries. Use for architecture planning. Requires TEAM_DB_PATH.

  • team_get_entry_by_idGet Team Entry by IDread-only

    Get a specific team entry by ID with full details including relationships and importance score. Requires TEAM_DB_PATH.

  • team_get_flag_analyticsFlag Analyticsread-only

    Get aggregate Hush Protocol flag analytics: resolution velocity, type distribution, per-user workload, staleness counts, and period-over-period trend comparison.

  • team_get_recentGet Recent Team Entriesread-only

    Get recent entries from the team database. Requires TEAM_DB_PATH.

  • team_get_statisticsGet Team Statisticsread-only

    Get statistics for the team database including entry counts, types, top tags, and contributor breakdown. Requires TEAM_DB_PATH.

  • team_get_vector_index_statsTeam Vector Index Statsread-only

    Get statistics about the team vector search index (item count, model, dimensions). Requires TEAM_DB_PATH.

  • team_import_markdownTeam Import from Markdown

    Import frontmattered Markdown files into the team journal

  • team_link_entriesLink Team Entries

    Create a relationship between two team entries. Requires TEAM_DB_PATH.

  • team_list_backupsList Team Backupsread-only

    List all available backup files for the team database. Requires TEAM_DB_PATH.

  • team_list_flagsList Team Flagsread-only

    List and filter Hush Protocol flags with structured metadata. Filter by status (active/resolved/all), flag_type, target_user, or author. Returns enriched flag objects — no manual auto_context parsing needed.

  • team_list_tagsList Team Tagsread-only

    List all tags used in the team database with usage counts. Requires TEAM_DB_PATH.

  • team_merge_tagsMerge Team Tags

    Merge a source tag into a target tag in the team database. All entries with the source tag will be re-tagged with the target tag. Only updates non-deleted entries. Requires TEAM_DB_PATH.

  • team_pass_flagPass Team Flag

    Create a machine-actionable flag in the team database. Flags replace communication noise with structured, searchable signals. Vocabulary: blocker, needs_review, help_requested, fyi (configurable via FLAG_VOCABULARY).

  • team_rebuild_vector_indexRebuild Team Vector Index

    Rebuild the team semantic search vector index from all existing team entries. Requires TEAM_DB_PATH.

  • team_resolve_flagResolve Team Flag

    Mark a team flag as resolved with an optional resolution comment. Idempotent — resolving an already-resolved flag returns success with the existing state.

  • team_searchSearch Team Entriesread-only

    Search entries in the team database by text and/or tags. Requires TEAM_DB_PATH. 🛑 WARNING: Team DB is a shared multi-tenant domain. You MUST specify project_number to isolate results to the target project.

  • team_search_by_date_rangeSearch Team Entries by Date Rangeread-only

    Search team entries within a date range with optional filters for entry type and tags. Requires TEAM_DB_PATH. 🛑 WARNING: Team DB is a shared multi-tenant domain. You MUST specify project_number to isolate results to the target project.

  • team_semantic_searchTeam Semantic Searchread-only

    Perform semantic/vector search on team entries using AI embeddings. Supports find-related-by-ID (entry_id) and metadata filters. Threshold default is 0.25 (try 0.15-0.2 for broader matches, 0.4+ for strict matches). Entries auto-indexed on creation. Requires TEAM_DB_PATH.

  • team_update_entryUpdate Team Entry

    Update a team entry (content, type, tags, and 11 metadata fields including significance, project, issue, PR, and workflow). Pass null to clear a field. Requires TEAM_DB_PATH.

  • team_update_flagUpdate Team Flag

    Update a flag's metadata without resolving it. Escalate severity (fyi → blocker), reassign target_user, edit message, add/update link, or reopen a resolved flag. Returns the updated flag with a list of changes made.

  • team_visualize_relationshipsVisualize Team Relationshipsread-only

    Generate a Mermaid diagram showing relationships between team entries. Filter by entry ID, tag, or traverse to a specified depth. Requires TEAM_DB_PATH.

  • test_simpleTest Simpleread-only

    Simple test tool that just returns a message

  • update_entryUpdate Entry

    Update an existing journal entry (content, type, tags, and 11 metadata fields including significance, project, issue, PR, and workflow). Pass null to clear a field.

  • update_github_milestoneUpdate GitHub Milestone

    Update a GitHub milestone (title, description, due date, or state). Use state "closed" to close a completed milestone.

  • visualize_relationshipsVisualize Relationshipsread-only

    Generate a Mermaid diagram visualization of entry relationships

Signals

Stars
20
Forks
7
Open issues
2
Contributors
2
Last commit
Jun 17, 2026 (4 months ago)
Last release
May 31, 2026 (5 months ago)
Last package publish
May 31, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.neverinfamous/memory-journal-mcp
Version
1.1.3
Auth
No auth
Packages
oci docker.io/writenotenow/memory-journal-mcp:v1.1.3
License
MIT
Repository
github.com/neverinfamous/memory-journal-mcp
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
Official MCP Registrygithub-graphql

More from neverinfamous

Cite this page

Memory Journal MCP. Agent Mart. https://agentmart.dev/connectors/neverinfamous-memory-journal-mcp (last updated 2026-10-24)