Skip to main content
Glama
xunji-private-mcp

xunji-private-mcp

by Vdk1639

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
XUNJI_BODY_KEYNo训记身体指标模块的 Key,用于按日期和指标读取和写入记录。
XUNJI_ENV_FILENo指定 .env 文件的绝对路径;也可用全局参数 --env-file 指定。默认从当前目录读取 .env。
XUNJI_FOOD_KEYNo训记饮食模块的 Key,用于读取和写回饮食记录、维护自定义食物。
XUNJI_TRAIN_KEYNo训记训练模块的 Key,用于读取和写回训练记录、查询官方训练计划。
XUNJI_FOOD_SEARCH_KEYNo训记食物搜索模块的 Key,用于搜索训记官方食物。
XUNJI_AGENT_TEMPLATE_KEYNo训记 Agent 个人模板模块的 Key,用于同步、维护专属文件夹中的训练模板。

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

按用户指定的日期和范围访问训记。写入工具会请求用户确认;请提供能让用户核对的记录或变更,不要推测食物营养或未知数据。

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_trainingB

Get training for one day. Use full data for heart rate, rest times, RPE and unfinished sets.

upsert_trainingA

Create or patch up to four same-day trainings, after the user's confirmation.

Provide datestr and movements for new records. Use localid for updates and include only changed fields. If movements are supplied for an update they replace the entire list, including unfinished sets. Use verified Chinese movement names and reuse client_request_id when retrying the same write.

list_official_plansA

List official PlatformPlan and UniversalPlan instances and their plan_ref values.

get_official_planB

Read the days for a listed plan_ref. Omit dates for the default range or supply a range of at most 92 days.

query_food_recordsC

Read the requested inclusive date range of Xunji food records.

search_official_foodB

Search Xunji's official foods. Prefer foods over the compact d array in the result.

Each d row is [id, name, cal, carb, fat, protein, foodpic, uniquekey, units]. Nutrition values are per 100 g. Preserve uniquekey, ntr and units when recording a match.

upsert_food_recordsA

Add or update food records after user confirmation. Supply the record id for updates.

Obtain uniquekey, per-100g ntr and any units from official search or the saved custom food. Ask the user to resolve uncertain food matches, meal types, amounts or units. Reuse client_request_id if retrying the same request after an uncertain result.

upsert_custom_foodA

Save a custom food after user confirmation. Use a custom food when official search has no suitable match or the user requests one. For updates, supply its existing uniquekey.

Provide a real nutrition source and known kcal, protein, fat and carbohydrate per 100 g. The source is shown to the user. Omit portion units for gram-based tracking. Use food from the result when recording that food.

query_body_metricsB

Read personal Xunji body metric records. Omit types to include all metrics.

Use the wire name weist for waist circumference. Use limit and offset to paginate records.

upsert_body_metricsA

Preview and confirm adding or updating body metrics by date and type.

Use kg for weight, % for bodyfat, and cm for circumference or size. Reuse client_request_id if retrying the same request after an uncertain result.

sync_agent_templatesA

Fetch all Agent-folder templates and current versions. This never creates a folder.

mutate_agent_templatesA

Apply confirmed changes to the single Agent folder.

First sync the templates. To create, pass stable client_id, name, and public movements with official Chinese names. To update, pass template_id, its base_version, and changed name/color/movements or native movement/rules. Specified movement lists replace the entire list. A delete uses template_id and base_version. To rename the folder, pass folder_update with name and the folder's current base_version. Reuse mutation_id for the same change. A new template is allowed to recreate a missing Agent folder.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 12 tools

Disambiguation4/5

The four food tools are distinguishable by lifecycle stage (catalog search vs. record read vs. record write vs. custom-food creation), and the training/plan/body-metric/template tools each target a distinct resource. The main risk is the shared `upsert_*` verb family across four unrelated domains and the search vs. query split for food reads, which an agent could momentarily confuse.

Naming Consistency4/5

All twelve names are snake_case verb_noun (search_official_food, upsert_training, list_official_plans, query_body_metrics), so the pattern is predictable. Minor deviation: read operations use three different verbs (search, query, get, list), which slightly weakens predictability but remains readable.

Tool Count5/5

Twelve tools is squarely in the well-scoped range and each tool maps to a concrete resource-action pair (six read, six write). No tool looks redundant or like filler.

Completeness4/5

Coverage spans the full domain: food search/records/custom foods, body metrics, trainings, official plans, and agent templates, with read and write in every mutable area. Minor gaps exist — there is no explicit delete for food records or body metrics (only upsert), and plans are read-only, though that may be intentional.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues