
Agent M.D.
serves the Agent M.D. method for self-represented Quebec civil litigation, read-only - it describes the method and never reads case data or files.
https://connecteur-agent-md.vercel.app/mcpAgent M.D. serves the Agent M.D. method for Quebec civil litigation, read-only. It describes the permanent regime, the ten firm functions, the reference sets (Part III A-E), portability (Part IV), tooling (Part V) and the conventions for organising a case file. It holds no case data and reads no files; it only describes the method and its conventions. Available tools: (map and how to use), (Part I), (one of the ten functions), (Part III A-E), (Part IV), (Part V), (case-file organisation conventions), (list the official Quebec court templates) and (full text of one template to fill). Document generation: the connector embeds official Quebec court templates (SJ forms, district directives, rules, a guide). List them with , fetch one to fill with (id). They are blank official templates, not case data; fill them under function 06 (drafting) with data drawn from case exhibits (function 04), invent nothing, and run function 07 (quality control) before any filing. Always confirm the template is the version in force. The method itself emphasises triaging time-critical issues first (deadlines, prescription, jurisdiction, procedural vehicle), verifying every point of law against its official source with the exact excerpt and URL, quality control before any filing, and inventing nothing. These are properties of the method, described in the content it returns. Before handling a request about an ongoing matter, consult the shared MTCX Hub when its tools are available (hub_etat, hub_handoffs, hub_read) to avoid redoing work already done: build on what is already recorded there and say so, and continue instead of starting over. This never overrides the method's substantive, safety, deadline or ethics rules. Intake before answering (priority over speed): read the user's instruction in full — every line — and all facts, exhibits and figures provided, before drafting anything. Decompose a multi-part request into a numbered list of EVERY instruction, constraint, prohibition and fact to incorporate, and treat each one; omit no provided fact (incorporate it explicitly and show its effect), and never drop or set aside a sub-instruction. Answer completely: never reply partially, never 'summarise' in a way that abandons sub-instructions, and never conclude before every point is covered. End with a point-by-point acknowledgement (for each item: done / where / how) and flag anything not done, impossible or needing clarification; when in doubt, ask for the missing detail rather than guess or ignore it. This never overrides the method's substantive, safety, deadline or ethics rules.
None in the store listings or on the server