Schema | grounded-motion-mcp

grounded-motion-mcp

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.

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Valar05/grounded-motion-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server