> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/jp/keeper-msp/commander-cli-sdk.md).

# コマンダーCLI/SDK

Keeperコマンダーは、コマンドラインおよびSDKのインターフェイスです。Keeper環境の制御や、プラットフォーム上の各種機能の自動化に利用できます。企業テナントとMSPテナントの両方に適用できる機能が多数あります。

セットアップとインストールについては、[コマンダーの概要](/keeperpam/jp/commander-cli/overview.md)をご参照ください。

コマンダーの[MSP専用コマンド](/keeperpam/jp/commander-cli/command-reference/msp-management-commands.md)の一部は、以下のとおりです。

**MSPコマンド**

| コマンド                  | 内容                       |
| --------------------- | ------------------------ |
| `msp-info` or `mi`    | MSPの詳細表示                 |
| `msp-down` or `md`    | サーバーからローカルMSPデータの更新      |
| `msp-license` or `ml` | MSPライセンスの表示と管理           |
| `msp-add` or `ma`     | 管理対象企業の作成                |
| `msp-remove` or `mrm` | 管理対象企業の削除                |
| `msp-billing-report`  | MSP請求レポートの作成             |
| `switch-to-mc`        | 管理対象企業コンテキストへの切り替え       |
| `switch-to-msp`       | MSPコンテキストへの切り替え          |
| `msp-convert-node`    | エンタープライズノードの管理対象企業への変換   |
| `msp-copy-role`       | MSPからMCへのロール強制適用ポリシーのコピー |
| `distributor`         | ライセンスの編集、MSPおよびMCの詳細表示   |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/enterprise-guide/jp/keeper-msp/commander-cli-sdk.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.