{"$schema":"https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json","name":"vet.praxis/praxis","description":"Read and draft against one veterinary practice's clinical record: consultations, notes, transcripts, patients, schedule, referrals and reports. Writes into the practice management system are proposed for a clinician to approve, never performed directly.","version":"5.87.0","packages":[],"_meta":{"vet.praxis/about":{"because":"This document uses the MCP registry's `server.json` format, which is a real schema. The location it is served from is not a ratified standard — there is no agreed well-known path for MCP server discovery — so treat the path as this product's convention rather than something to assume elsewhere."},"vet.praxis/install":{"transport":"stdio","command":"bun run --filter @praxis/mcp start","environment":[{"name":"PRAXIS_API_KEY","description":"A workspace API key, created under Settings › API & keys and shown once. The key identifies the practice; no tool takes a workspace argument.","required":true,"secret":true},{"name":"PRAXIS_BASE_URL","description":"Where the Praxis API is served.","required":false,"secret":false}],"because":"`@praxis/mcp` is not published to npm or any package registry, so there is no `npx` install and this card claims none. It runs from a checkout of the Praxis repository. Publishing it is recorded as J3b in the parity plan."},"vet.praxis/remote":{"transport":"streamable-http","path":"/mcp","authorization":"Bearer <workspace API key>, or the x-praxis-api-key header. The key is created under Settings › API & keys and identifies the practice; no tool takes a workspace argument.","because":"The same tools, resources and prompts as the stdio server, over MCP's Streamable HTTP transport on the origin serving this document — so a host that cannot spawn a local process can still reach the practice. Sessions are not kept: each request is answered on its own, so there is no resumable stream and no server-initiated notification. An unauthenticated request is refused with 401 and a WWW-Authenticate header rather than answered, including the initialize call."},"vet.praxis/surface":{"tools":["discover_capabilities","read_data","run_operation","propose_change","list_skills","read_skill","read_skill_file","submit_feedback"],"resources":["praxis://practice","praxis://catalog","praxis://patient/{patientId}","praxis://consultation/{consultationId}","praxis://skills","praxis://skill/{slug}","praxis://wiki","praxis://wiki/{slug}","praxis://rota/mapping"],"prompts":["prepare_for_consultation","letters_we_owe","unfiled_work_review","before_archiving_an_employee","reconcile_rota_with_spreadsheet"]},"vet.praxis/write-policy":{"summary":"Reads are answered directly. Proposal-gated tools do not perform their requested write: they create a proposal for a clinician to review. Medical-record and billing proposals execute only after approval. Task creation remains fail-closed until the task and its approval can commit atomically. A queued proposal is a real outcome to report, not a failure to retry.","tools":["propose_change"]}}}