Anatomy Engine

A 3D full-body anatomy + biomechanics engine, exposed as a Model Context Protocol (MCP) server with an inline 3D viewer. It gives an AI agent (or any app) real anatomical structure, biomechanical relationships, and an interactive body to render.

⚠️ Awaiting clinician approval. The anatomical & clinical data is AI-authored and has not yet been reviewed by a licensed clinician. For educational purposes only — educational & directional, not diagnostic. See disclaimer.

What it is

• 22 MCP tools over a hand-authored knowledge core — structures, connections, innervation, blood supply, fascial chains, muscle roles, movements, postures, task activation, and correctives.

• 7 real Z-Anatomy systems (skeletal, muscular, nervous, cardiovascular, visceral, ligamentous, skin), Draco-compressed, with a mobile "lite" tier.

• A bone-identity rig — hover to identify any part, click for its biomechanical links, isolate a region, and articulate named postures (pelvic tilt, forward head, rounded shoulders…).

It's the reusable core beneath LooksLab; it has no accounts or paywall of its own.

Related MCP server: CDISC Library MCP Server

Quick start

npm install
npm run playground   # → http://localhost:4599  (every tool as a button + live 3D viewer)
npm test             # smoke tests
npm run validate-data

Use as an MCP server

Once published, point any MCP client at the package:

{
  "mcpServers": {
    "anatomy-engine": { "command": "npx", "args": ["-y", "@ajfutures/anatomy-engine"] }
  }
}

Or run straight from a local checkout — { "command": "npx", "args": ["tsx", "src/index.ts"], "cwd": "…/anatomy-engine" }.

Run it as a hosted API

The engine also ships as a deployable service — a remote MCP server + REST API with API keys, tiers and per-call metering, so it can be shared (or sold) without anyone installing anything.

npm run serve          # → http://localhost:8080  (landing page, docs, both transports)
npm run test:service   # 23 checks: tiering, quotas, clinical gate, MCP + REST

It adds three composite "one-call" tools — structure_brief, posture_brief, movement_brief — which run a whole lookup chain server-side and return one pre-joined answer, replacing 6–13 agent round-trips with a single call.

Deploying is one click — see DEPLOY.md. The 4 clinical tools are gated off by default (ENABLE_CLINICAL=false) pending the clinician review below.

The 22 tools

All reads are educational & directional, not diagnostic. Every tool returns structured JSON.

Browse & search

Connections & biomechanics

Anatomy facts

Clinical — educational & red-flag-screened, never diagnostic

Viewer

Using it with an AI agent

The point of the engine is that an agent can chain these tools to reason about a real question — turning a vague, plain-language ask into structured anatomy, then a grounded, sourced answer. Five examples:

1. "What exercises are beneficial for anterior pelvic tilt?" The agent calls get_pose("anterior_pelvic_tilt") → get_pattern("lower_crossed_syndrome") to read out which muscles are likely tight (hip flexors / iliopsoas, lumbar erectors) and likely weak (glutes, deep core), then get_interventions(...) on each. → "Release and stretch the hip flexors and low back; strengthen the glutes and deep core — here are specific correctives."

2. "My lateral hip aches when I sleep on that side — what could it be and what should I avoid?" map_symptoms("hip", "ache lying on my side") surfaces the gluteus medius and gluteal tendinopathy → list_pathologies("gluteus_medius") for signs + red flags → get_contraindications("gluteal_tendinopathy"). → "This pattern is often gluteal tendinopathy; commonly aggravated by crossing the legs and side-lying — things to be cautious with are X, Y. These red flags mean see a clinician." (Never a diagnosis.)

3. "Which muscles are the prime movers coming up out of a squat?" analyze_task("squat", "ascent"). → "Prime movers: gluteus maximus and quadriceps; synergists: hamstrings, adductor magnus, soleus; stabilizers: lumbar erectors and abdominals."

4. "I keep getting tension headaches and my upper traps are tight — what's the link?" search_anatomy("upper trap") → get_referred_pain("upper_trapezius") (refers to the temple) + get_pattern("upper_crossed_syndrome") → get_interventions(...), with list_pathologies red-flag screening for cervicogenic headache. → "The upper trapezius refers pain to the temple and is a classic driver of tension headaches with forward-head posture; here's how to release it — and these red flags warrant a professional."

5. "Show me forward-head posture in 3D and the muscles involved." get_pose("forward_head") for the tight/weak read, then show_anatomy({ systems: ["skeletal","muscular"], pose: "forward_head" }) returns the inline 3D viewer articulated into that posture, with the involved muscles highlightable. → An interactive body the user can rotate, plus the muscle-balance explanation.

In each case the engine supplies the structured anatomical facts and relationships; the agent does the plain-language conversation and turns them into recommendations — grounded, and consistently framed as educational, not diagnostic.

Disclaimer

This engine is for education and orientation only. It is not medical advice, not a diagnosis, and not a substitute for a licensed clinician. The clinical tools ship with red-flag screening and non-diagnostic framing.

Status: awaiting clinician approval — for educational purposes only. The anatomical/clinical data is AI-authored and has not yet been reviewed by a licensed clinician.

License & attribution

• Code & data: MIT — see LICENSE.

• 3D meshes: derived from Z-Anatomy (CC BY-SA 4.0), itself from BodyParts3D/DBCLS. Attribution + share-alike obligations apply wherever the meshes are displayed — see NOTICE. The meshes are not bundled in the npm package; they're built by pipeline/export.py and served from a hosted asset base.