Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the GLPI in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
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.
Try asking
Example prompts for GLPI
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → GLPI, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
GLPI + Microsoft Copilot
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.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
GLPI_URL, GLPI_APP_TOKEN, GLPI_USER_TOKEN
Step 1 — Get credentials
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)
Step 2 — Install the adapter
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
Step 3 — Add the connector in Microsoft Copilot
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
GLPItools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
Available tools
| 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 |
FAQ
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
- Connector landing page
- Connect to Claude
- Connect to ChatGPT
- Connect to Cursor
- Connect to Gemini
- Connect to Meta Muse
Was this guide helpful?