CoreMem

MCP server: coremem

{
  "url": "https://api.coremem.app/api/mcp",
  "headers": {
    "Authorization": "Bearer ${COREMEM_API_KEY}"
  }
}

Create a brand-new mem in the user's CoreMem library. Use only when the user explicitly asks to save or create something new in CoreMem. The proposal is queued for their review — it is never saved automatically.

Propose a new mem using $ARGUMENTS as guidance.

1. Parse $ARGUMENTS to identify the name and content for the new mem
   - If $ARGUMENTS is empty, ask the user for the mem name and what it should contain
2. Call `create_mem` with the name, content, and `is_public: false` unless the user explicitly asked for it to be public
3. Confirm the proposal was submitted and remind the user to review it in the CoreMem dashboard before it is saved

Note: proposals are never applied automatically. The user reviews and approves all changes at coremem.app.

Propose an update to an existing CoreMem mem. Use when the user wants to correct or add to an existing mem. Do NOT use this to create a new mem — use create for that.

Propose an update to a CoreMem mem using $ARGUMENTS as guidance.

1. Parse $ARGUMENTS to identify the target mem and the proposed content
   - If a mem name or slug is provided, look it up directly with `get_mem`
   - Otherwise, use `search_mems` to find the most relevant mem
2. Read the current mem content with `get_mem` so the proposal is coherent with what is already there
3. Draft the proposed update — incorporate new information rather than replacing existing content unless the user explicitly asked to replace it
4. Call `propose_update` with the mem ID and the proposed new content
5. Confirm the proposal was submitted and remind the user to review it in the CoreMem dashboard before it is applied

If $ARGUMENTS is empty, ask the user what they want to update and what the new content should be.

Note: proposals are never applied automatically. The user reviews and approves all changes at coremem.app.

List all available CoreMem mems in the user's account.

List the user's CoreMem mems.

Call `list_mems` and present the results as a clean list showing each mem's name and slug. Note the total count. Do not show IDs.

If $ARGUMENTS is provided, filter the list to mems whose name contains that string.

Load relevant CoreMem mems into context. Use when starting a new task, when the user mentions "mems" or "context", when the task involves a domain the user may have documented, or when background knowledge would improve your response.

Load relevant context from the user's CoreMem mem store.

1. Call `search_mems` with 2-3 keywords that describe the current task or topic
2. If no relevant results, call `list_mems` to browse what is available
3. Call `get_mem` on any mems that look relevant
4. Briefly acknowledge what context was loaded before proceeding

If $ARGUMENTS is provided, treat it as the search query instead of inferring keywords from context.

Do not load mems that are clearly unrelated to the current task. Prefer relevance over completeness.