インストール不要。2分以内に動きます。
cloud.anythingmcp.com で無料トライアルを開始し、GLPI をワンクリックで追加して、AI クライアント（Claude、ChatGPT、Copilot、Cursor）を生成された MCP エンドポイントに向けるだけ。Docker も git clone も、開発経験も不要です。
Summary
GLPI open-source ITSM and asset management: tickets, computers, monitors, software, users and entities, plus GLPI's search engine. REST API on your own instance, session-token auth with an App-Token.
こう聞いてみよう
GLPI のサンプルプロンプト
プロンプトをクリックでコピー。Claude / ChatGPT / Cursor / Gemini / Copilot / OpenClaw に貼り付けて、このコネクターで実行できます。
Claude は AI のため誤ることがあります。回答をご確認ください。
💡 インストール不要? cloud.anythingmcp.com を直接利用してください。 サインインし、Connectors → GLPI をクリック、認証情報を貼り付け、MCP API キーを発行 — 完了です。Docker も
git cloneもローカルサーバーも不要。
GLPI
GLPI open-source ITSM and asset management: tickets, computers, monitors, software, users and entities, plus GLPI's search engine. REST API on your own instance, session-token auth with an App-Token.
セットアップ
GLPI needs two tokens, and both are easy to confuse.
- App-Token — identifies the application. In GLPI go to Setup → General → API, enable 'Enable Rest API' and 'Enable login with external token', add an API client, and copy its application token. Put it in
GLPI_APP_TOKEN. - User-Token — identifies the person. Open the GLPI user the agent should act as, go to the API tab of their profile, and regenerate the remote access key (personal API token). Put it in
GLPI_USER_TOKEN. - Set
GLPI_URLto the instance root (no trailing slash); the adapter appends/apirest.php.
…(continued in the in-app connector instructions)
前提条件: GLPI_URL, GLPI_APP_TOKEN, GLPI_USER_TOKEN
ローカルでコネクタをインストール
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
http://localhost:3000/connectors/store を開き、 GLPI を選択し、前提条件に記載された環境変数を入力します。
利用可能なツール
| Tool | What it does |
|---|---|
glpi_get_active_entities | Read the entities the logged-in user is currently scoped to |
glpi_list_tickets | List tickets in the active entity with their status, priority, category, requester and dates |
glpi_get_ticket | Read one ticket in full, with its description, status, urgency, impact, priority, requester, assignee and SLA dates |
glpi_get_ticket_followups | Read the follow-ups (the conversation) on one ticket, in order, with author, date and whether each is private |
glpi_search | Run a GLPI search with criteria |
glpi_list_search_options | Read the searchable field map for one item type: which field number means status, requester, serial number and so on |
glpi_list_computers | List computers from the asset inventory with their name, serial number, model, operating system and assigned user |
glpi_get_computer | Read one computer in full: hardware, OS, network interfaces, contracts, location and the user it is assigned to |
glpi_list_users | List GLPI users with their login, name, e-mail, entity and active flag, to resolve who a ticket or an asset belongs to |
glpi_list_software | List software items from the inventory with their publisher, category and the number of installations, for licence questions |
次のステップ
このガイドは役に立ちましたか?
