grounded-motion-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROUNDED_MOTION_TRANSPORT | No | Transport mode for the MCP server. Use 'streamable-http' for HTTP appliance. | stdio |
| GROUNDED_MOTION_WORKSPACE | Yes | Absolute path to the workspace directory where motion tracking data is stored. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| track_motionA | Track every source frame with RTMW whole-body landmarks and emit review artifacts. The source must be inside GROUNDED_MOTION_WORKSPACE. Supply all four crop fields or none. Inference ends in tracked/unreviewed; it never implies motion acceptance. |
| validate_trackC | Validate schema, complete chronology, required joints, review state, and event lock. |
| inspect_trackC | Summarize coverage gaps, uncertainty, events, review state, and gate results. |
| compare_motionC | Compare candidate hips, feet, wrists, and detailed hands to source motion. |
| export_artifactsC | Verify the immutable manifest and export a deterministic review bundle. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clear and distinct purpose: tracking frames, validating schema, inspecting coverage, comparing motion, and exporting artifacts. There is no overlap in functionality.
Most tools follow a verb_noun pattern (export_artifacts, track_motion, validate_track, inspect_track), but compare_motion uses 'motion' instead of 'track', causing a slight inconsistency.
With 5 tools, the server is well-scoped for motion capture and review tasks. Each tool contributes a distinct step in the workflow without being excessive.
The tools cover tracking, validation, inspection, comparison, and export, but lack lifecycle management tools such as updating review status, deleting tracks, or listing all tracks, which creates gaps in a full workflow.