Beat Saber Modding Tools MCP

Overview Schema Source Related Servers Discussions Admin

deploy_mod

Destructive

Copies a built Beat Saber mod into the game's Plugins folder, or into IPA/Pending/Plugins when the game is running so BSIPA can install it on next launch.

Instructions

Copy the built mod into the game: Plugins normally, or IPA/Pending/Plugins while Beat Saber is running (BSIPA moves pending files on next launch).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "deploy_mod"
  }
}

Input Schema

Name	Required	Default
`project`	Yes
`copy_pdb`	No
`game_dir`	No
`configuration`	No	Debug

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 10, 2026

TDQS

A3.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description adds real value beyond that by explaining the BSIPA pending-file mechanism and that files are moved on next launch. It still does not say whether existing files in Plugins are overwritten, which matters for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the action front-loaded and the conditional detail following it; every clause carries information and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the deployment mechanics are well covered. The gap is the four undocumented input parameters at 0% schema coverage, which leaves an agent guessing about configuration, pdb copying, and directory override.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, and the description mentions none of them. The 'game_dir' parameter in particular is left unexplained even though the description discusses game paths, and 'copy_pdb' and 'configuration' are entirely opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Copy the built mod into the game') and even names the two destination layouts, so an agent knows exactly what the operation does. It does not explicitly contrast itself with siblings like build_mod or package_mod, but the phrase 'built mod' signals the prerequisite step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a conditional rule for choosing the destination (Plugins normally, IPA/Pending/Plugins while Beat Saber is running), which is genuinely useful usage context. However, it never states when to use this tool versus building or packaging, nor any prerequisite or refusal condition beyond the runtime state.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.