Aidimag MCP server

Read from the package source without running it. The installed server may list more.

• aidimag_help

  Show what aidimag offers: available tools, prompts (slash commands), resources, and the companion `dim` CLI commands. Call this when the user asks what aidimag can do, how to use it, or types 'aidimag help' — then relay the overview to them.

• chat_harvest

  Harvest the CURRENT chat session on the fly: pass the messages the USER typed this session (verbatim) and durable facts are extracted and queued for human review — the live, tool-agnostic equivalent of `dim harvest`. Works from ANY IDE/agent (Copilot, Cursor, Codex, Claude, Devin, …), including cloud tools with no local transcripts. Call at session end, or after a long exchange rich in project kno

• commits_mine

  Mine git commit history for memory-worthy candidates (same as `dim mine`). Queues proposals for `dim review` — never writes active memory directly. Use after meaningful commits, or with full=true to rescan all history.

• context_note

  Capture a durable fact the USER just stated in chat. Call this IMMEDIATELY when the user shares codebase knowledge — don't wait for session end. ALWAYS trigger on: 'we use X because Y' (DECISION), 'never do X' (GUARDRAIL), 'we always X' (CONVENTION), 'we tried X, it failed' (FAILED_APPROACH), 'the architecture is...' (ARCHITECTURE). Skip task-specific requests like 'fix this bug'. User-stated fact

• knowledge_ingest_submitwrite action

  Submit the FALSIFIABLE claims you extracted from a pending knowledge doc (see the knowledge_ingest prompt). Queues them as proposals (source knowledge:<doc>), writes the durable summary, backs up the original, and clears the inbox copy. Claims become PINNED memory only after `dim review` (unless the repo opted out).

• knowledge_pending

  List documents waiting in the knowledge inbox to be summarized into pinned-on-approve memory proposals. Use with the knowledge_ingest prompt to process them in-session.

• memory_critique

  Review what you just did (or plan to do) against the project's VERIFIED memory and guardrails — a 'second critic' grounded in real, falsifiable beliefs rather than another model's opinion. Call BEFORE committing or proposing memories. Resolve guardrail violations and contradictions first.

• memory_get_for_files

  Get all memories relevant to specific files before editing them — conventions, gotchas, and invariants that apply to those paths.

• memory_propose

  Propose a memory for the human review queue. Use at SESSION END for learnings that should persist but warrant review before becoming active memory. Prefer this over memory_write for inferred/uncertain knowledge.

• memory_refute

  Mark a memory as REFUTED when you discover it no longer holds. Optionally provide the id of a new memory that supersedes it. Refuted memories are kept as negative knowledge.

• memory_search

  Search the repo's verified memory for decisions, conventions, gotchas, failed approaches, and invariants. Use BEFORE exploring the codebase — past sessions may already know the answer.

• memory_status

  Get a summary of the repo's memory store: counts by verification status and kind.

• memory_verify

  Re-run cheap evidence checks (STATIC_CHECK, COMMIT_REF) and update memory statuses. Use before relying on VERIFIED memories if the repo may have changed, or to verify specific memories by id.

• memory_writewrite action

  Persist a new memory about this codebase. Write the claim as a FALSIFIABLE statement (something that could be checked against the code). Attach evidence whenever possible. For kind=GUARDRAIL, set guardrail_level (never|always|ask-first).

• proposals_pending

  List memory proposals awaiting human review.

• scratchpad_clear

  Clear scratchpad working notes (one session key, or everything). Use when a task completes and its intermediate state is no longer needed.

• scratchpad_read

  Read short-term working notes from the current session's scratchpad (newest first). Use at session start or when resuming a task to recover in-flight state. Expired notes are purged automatically.

• scratchpad_writewrite action

  Jot a SHORT-TERM working note for the current session: intermediate findings, plans, hypotheses, task state. Auto-expires (default 24h) and is never synced. NOT durable memory — use memory_write/memory_propose for knowledge that should persist across sessions.

• ticket_get

  Fetch the ticket behind the current work (title, description, type, status) from the connected ticketing app. Use at session end: the ticket carries the WHY that commits lack. Omit the id to auto-detect it from the current branch name.

• Code scan96 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 27 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

82/100

higher than 63% of 48,255 servers

Tools

19

the typical server has 7

Tools that change things

16%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

1

more than 65% of 28,688 servers

Downloads a week

156

more than 71% of 12,191 servers with a package

Aidimag: common questions

Is Aidimag MCP server safe?

Mostly: it is graded B (82/100). Read the Aidimag safety report

How do I install Aidimag?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Aidimag need an API key?

Yes. The registry entry asks for OPENAI_API_KEY.

Is Aidimag maintained?

The last commit was 27 days ago (2026-10-08). The latest release is v1.0.22.

What can I use instead of Aidimag?

Servers from other publishers that do the same job: Deja Vu MCP server, State Memory MCP server and Knowl MCP server. Compare all Aidimag alternatives.

How does Aidimag compare with other MCP servers?

safety score 82/100 (higher than 63% of 48,255 servers); tools 19 (the typical server has 7); tools that change things 16% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.