adv2mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADV2MCP_DUPE_DIR | Yes | Path to the Garry's Mod Advanced Duplicator 2 data directory where dupe files are stored. | |
| ADV2MCP_REVISION | No | AdvDupe2 revision to use when creating dupe files. Example value: "4". | |
| ADV2MCP_REQUIRE_ALLOWLIST | No | Whether writing builds without an allowlist profile is blocked. Example value: "1". |
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 |
|---|---|
| get_statusA | Show configured game/dupe paths, format versions and filesystem availability. |
| get_prop_policyA | Show the server allowed-prop profile, reloaded on each call. Missing profiles block writes. Never infer server permission from local installation or a screenshot. |
| list_dupesA | List .txt duplications recursively, filtered by filename, without decoding every file. |
| inspect_dupeB | Read metadata, model counts and paginated positions/angles from an existing dupe. |
| read_dupeB | Return a lossless adv2mcp-json-v1 document. Tables have typed keys and IDs; vectors/angles are tagged. Large dupes may produce large responses; inspect_dupe is paginated. |
| write_dupeA | Save a lossless document returned by read_dupe, preserving unknown addon data. Revision defaults to the source document or the server default. Overwrites create backups. |
| create_buildA | Build prop_physics entities with positions, angles, color, material and Weld/NoCollide. Use weld_to_head for a connected contraption. preview_only validates and reports counts without writing. Unknown models are reported, since Workshop GMA/external mounts may supply them. |
| transform_dupeB | Rotate simple prop builds around the copy origin, then translate their local positions. Supports single-body prop_physics with Weld/NoCollide only. Saves a new file unless explicitly overwriting. |
| search_modelsA | Find server-allowed models by default (all query words must match). allowed_only=false searches installed models without implying permission. Captured profiles can include Workshop models absent from the local VPK index. |
| model_infoA | Read unrotated MDL hull bounds and dimensions in Source units for accurate prop placement. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| design_build | Plan and save a Garry's Mod construction using installed models. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| build_schema | JSON Schema for the build parameter of create_build. |
TDQS
Scored across 10 tools
Most tools target distinct actions (list, read, inspect, write, transform, create, search, status, policy, model info). The main overlap is inspect_dupe vs read_dupe, but their descriptions distinguish paginated summary from lossless full document, and create_build vs write_dupe are separated by build-from-parameters vs save-document semantics.
Nine of ten tools follow a clear verb_noun pattern in snake_case (list_dupes, read_dupe, write_dupe, transform_dupe, create_build, search_models, etc.). model_info is the sole noun-only exception, but its meaning remains clear.
Ten tools is well-scoped for a dupe/prop build manipulation server, covering discovery, inspection, read/write, transformation, creation, model search, and environment/policy checks without obvious filler.
The surface covers core lifecycle operations: list, inspect, read, write/update, transform, create, search models, and policy/status checks. Minor gaps like explicit delete or rename for dupe files are not covered, but common workflows can be handled and write_dupe backups mitigate overwrite risks.