Create a new journal entry. Content must be well-structured markdown using ## section headers. Select the most accurate entry_type (e.g., retrospective, personal_reflection, technical_note). For session summaries, use entry_type "retrospective" with tag "session-summary" and structure content as: ## Accomplished, ## Unfinished / Blocked, ## Context for Next Session. REQUIRED: You MUST include project_number. Extract this by querying memory://agent-id. REQUIRED: You MUST include impact_score, trust_score, and validation_status. REQUIRED: You MUST use related_to to anchor the entry to a session summary or nearby context.

Retrieve a specific entry by its ID

Get the most recent journal entries

Retrieve the revision history of an entry (last 10 edits).

List all unique tags used across all entries

A simple echo tool for testing connection and basic parameter parsing.

Triggers a sequence of progress notifications to verify the transport layer supports them.

Throws a specific type of error to verify the server formats and returns them correctly over MCP.

Update the status of multiple anchors (e.g. to stale or invalidated) based on validation rules or git history checks.

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.

Search journal entries within a date range with optional filters

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.

Get statistics about the semantic search vector index

List recently soft-deleted entries that can be restored

Search across multiple configured team databases simultaneously. Returns results with team_db labels.

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

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

Create a relationship between two journal entries

Generate a Mermaid diagram visualization of entry relationships

Export journal entries to JSON or Markdown format

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.

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.

Import knowledge management exports (Notion, Obsidian, Logseq) into the journal. Normalizes wikilinks, YAML frontmatter, and block hierarchies automatically. Use dry_run: true to preview what would happen without writing.

Update an existing journal entry. When updating content, preserve the existing markdown structure (## section headers). Do NOT restructure or add new top-level sections unless explicitly requested. Pass null to clear a metadata field. Supports content, type, tags, and 11 metadata fields including significance, project, issue, PR, and workflow.

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.

Restore a soft-deleted journal entry.

Create multiple journal entries at once. Max 50 per batch. Use this for imports or bulk creation. Select the most accurate entry_type for each. REQUIRED: You MUST include project_number. Extract this by querying memory://agent-id. REQUIRED: You MUST include impact_score, trust_score, and validation_status. REQUIRED: You MUST use related_to to anchor entries to previous context.

Update multiple existing journal entries in a single transaction. Max 50 per batch. REQUIRED: You MUST include project_number. Extract this by querying memory://agent-id.

Delete multiple existing journal entries in a single transaction. Max 50 per batch.

[REQUIRES ADMIN SCOPE] Rebuild the semantic search vector index from all existing entries

Add a specific entry to the semantic search vector index

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.

Search operational telemetry audit logs by tool name, user, date range, status, or category. Returns the most recent matches up to the limit.

Manually trigger the autonomous pruning and cleanup routines. This evaluates entry importance, archives old entries, and hard-deletes stale softly-deleted ones.

Register a new project in the global registry. This is required before the agent can switch context to this repository.

Update the details (path, number, or name) of an existing project in the registry.

Remove a project from the global registry.

List all registered projects.

Get details of a specific registered project.

Dynamically update the MCP server configuration (instruction level, tool filters, briefing preferences) without restarting the server.

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

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 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 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 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.

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

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

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

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.

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

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

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

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

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

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

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

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 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".

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

List all available backup files with their sizes and creation dates

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.

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

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. Content must be well-structured markdown using ## section headers. Select the most accurate entry_type (e.g., retrospective, technical_note). For session summaries, use entry_type "retrospective" with tag "session-summary" and structure content as: ## Accomplished, ## Unfinished / Blocked, ## Context for Next Session. REQUIRED: You MUST include project_number. REQUIRED: You MUST include impact_score, trust_score, and validation_status. REQUIRED: You MUST use related_to to anchor the entry to a session summary or nearby context. Requires TEAM_DB_PATH.

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

Get recent entries from the team database. Requires TEAM_DB_PATH.

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

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.

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.

List recently soft-deleted team entries that can be restored. Requires TEAM_DB_PATH.

Update a team entry. When updating content, preserve the existing markdown structure (## section headers). Do NOT restructure or add new top-level sections unless explicitly requested. Pass expected_version for optimistic locking. Pass null to clear a metadata field. Supports content, type, tags, and 11 metadata fields. Requires TEAM_DB_PATH.

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.

Restore a soft-deleted team entry. Requires TEAM_DB_PATH.

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.

Create multiple team journal entries at once. Max 50 per batch. Select the most accurate entry_type for each. REQUIRED: You MUST include project_number. REQUIRED: You MUST include impact_score, trust_score, and validation_status. REQUIRED: You MUST use related_to to anchor entries to previous context.

Update multiple existing team journal entries in a single transaction. Max 50 per batch. Can only update entries you authored. Pass expected_version for optimistic locking.

Delete multiple existing team journal entries in a single transaction. Max 50 per batch. Can only delete entries you authored.

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

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

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

Create a relationship between two team entries. Requires TEAM_DB_PATH.

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

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

Export team entries as frontmattered Markdown files

Import frontmattered Markdown files into the team journal

Import knowledge management exports into the team journal

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

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

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.

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

Rebuild the team semantic search vector index from all existing team entries. Requires TEAM_DB_PATH. [REQUIRES ADMIN SCOPE]

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

Add a new member to the team with a specific role. Bootstraps the first user as admin if table is empty. Requires TEAM_DB_PATH.

Remove a member from the team. Requires TEAM_DB_PATH.

Update the role of an existing team member. Requires TEAM_DB_PATH.

List all registered team members and their roles. Requires TEAM_DB_PATH.

Get details about a specific team member. Requires TEAM_DB_PATH.

Map a raw author name to a canonical identity. Requires admin role. Used to consolidate attribution for team analytics when one person uses multiple usernames.

Remove an author alias mapping. Requires admin role.

List all registered author aliases. Requires admin role.

Resolve a raw author name to its canonical identity using registered aliases. Requires admin role.

Retroactively rewrite all past entries matching an author's aliases to the canonical author name. Requires admin role. This operation modifies database entries.

Run arbitrary JavaScript to automate tasks in a secure sandbox. IMPORTANT: You MUST use the mj object (NOT api, journal, or mcp) to access tools. DO NOT use import() or require(); the mj tools are globally available in the sandbox. Available tools are mapped directly from MCP tool names, converted to camelCase (e.g., create_entry -> mj.createEntry(), search_entries -> mj.searchEntries()). Anti-Hallucination Hint: DO NOT GUESS parameter keys (e.g., passing repo instead of repo_name will fail). ALWAYS inspect the schema first if unsure: return await mj.createEntry.schema(). Execution limit: 30s. Network access (fetch) disabled. Example: return await mj.searchEntries({ query: "PowerShell" })

Retrieve commit history for the current repository

Search commit history by query

Get latest release commits

Get commits since the last tag/release

Analyze patterns in a list of commits or recent history

Check if a journal entry's anchors have been modified or deleted in git since the entry was created.

Fallback handler for read_resource when invoked as an MCP tool instead of a protocol resource read.

Fallback handler for mj_read_resource when invoked as an MCP tool instead of a protocol resource read.

Fallback handler for memory_read_resource when invoked as an MCP tool instead of a protocol resource read.

Fallback handler for load-briefing when invoked as an MCP tool instead of an MCP prompt.

Fallback handler for mj_session_summary when invoked as an MCP tool instead of an MCP prompt.