Conventions MCP

Save only a durable coding convention, standing instruction, correction, or workflow preference that should govern future sessions or repeated work — e.g. style rules ('always use 2-space indent') or standing directives ('never force-push to main'). Never capture directions specific to the current task, temporary decisions, current status, incident history, commands used for one job, or descriptions of how an individual job was completed; those belong only in the conversation. A preference mentioned while directing one task is not durable unless the user clearly states or confirms that it should apply in the future. Condense each durable rule to one sentence, two if absolutely necessary — no incident stories, user quotes, or example code. Call this when the user establishes or corrects a durable rule, or explicitly asks to retain a genuinely long-lived convention. Classify it yourself using the type/topics/projectScoped fields below, based on the conversation the thought came from. If a single message states multiple distinct durable rules, call this once per rule — don't merge them into one capture — and relay each one individually the same as a single capture, not summarized together. After every successful call, state the captured content verbatim and its project back to the user (the response text already contains both) — this is how they catch a misinterpreted rule and correct or delete it immediately, rather than discovering it wrong much later. Call shape — four top-level arguments, not one wrapped/stringified object: {"content": "Never assign innerHTML; build with DOM methods.", "type": "convention", "topics": ["dom", "security"], "projectScoped": false}

Permanently delete a specific captured thought by its ID. This is destructive and irreversible — no undo, no trash. Only call this when the user explicitly asks to delete, remove, or forget a specific thought. Never call it proactively, as a side effect of another action, or on a guess at which ID they mean — if the ID isn't already known from context, use search_thoughts or list_thoughts first and confirm with the user which one before deleting.

Retrieve every convention, instruction, correction, and preference that applies right now — everything global plus anything scoped to the current project — in one call. A deterministic direct lookup (no embeddings, no ranking), so it won't miss anything a semantic search_thoughts query might rank low. Prefer this over several search_thoughts calls when you want the full standing rule set at once, e.g. at the start of unfamiliar work.

List all captured conventions/instructions, optionally filtered by type.

Look up previously stored coding conventions, standing instructions, and preferences, by meaning and by exact keyword match (hybrid search). Call this proactively before starting unfamiliar coding work, or when uncertain about a style/convention choice in a project — don't wait for the user to ask. Also call it when the user references a past preference or rule ('like we discussed', 'the usual way', 'you know how I like it').

Get a summary of all captured durable rules: totals, types, top topics, and per-project counts.

Correct or refine an existing thought's content in place — same id, re-embedded and re-tagged from the new content. Condense the rule to one sentence, two if absolutely necessary — no incident stories, user quotes, or example code. Use this instead of delete_thought + capture_thought whenever the user is correcting, refining, or replacing what a specific existing thought says (a stale convention, a preference that's since changed) rather than adding an unrelated new one. If the id isn't already known from context, use search_thoughts or list_thoughts first and confirm with the user which one before updating. Re-classify using the type/topics/projectScoped fields below, based on the corrected content and the conversation it came from. After a successful call, state the updated content verbatim and its project back to the user (the response text already contains both) — this is how they catch a misinterpreted rule and correct or delete it immediately. Call shape — five top-level arguments, not one wrapped/stringified object: {"id": 4, "content": "Never assign innerHTML; build with DOM methods.", "type": "convention", "topics": ["dom", "security"], "projectScoped": false}