Is this an official GLPI MCP server?

No. It is Memtro's MCP server with Memtro's GLPI connector behind it: the connector reads GLPI through its API with the credentials you connect on Dashboard → Connections, and GLPI publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in GLPI?

Only when you ask, and only what it has been granted: create a ticket (no notification is sent); add a follow-up to a ticket, private by default (no notification is sent); change a ticket's title, description, status, urgency, impact, priority or category; delete a ticket, to the trash or purged for good; assign a technician, observer or requester to a ticket; assign a group to a ticket; solve a ticket with a solution (notifies the requester); add a task to a ticket, private by default (no notification is sent); create a problem (no notification is sent); create a change (no notification is sent); create an inventory item (computer, monitor, printer, phone, network device or peripheral); change an inventory item's name, serial, comment, status, location, manufacturer, user or technician; delete an inventory item, to the trash or purged for good. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Engineering and operations

GLPI MCP server

GLPI in any MCP client, through Memtro: GLPI does not publish this server. Memtro's GLPI connector reads GLPI through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

GLPI service desk and asset inventory on your own server: search tickets, read one ticket with its follow-ups, and list computers, network equipment, printers, phones and other assets. Can create a ticket, add a follow-up or task, change a ticket's fields, assign a technician or group, solve a ticket (which notifies the requester), delete a ticket, create a problem or change, and create, change or delete an inventory item, with GLPI notifications off wherever GLPI allows.

Reads

glpi_search_ticketsSearch GLPI tickets, most recently updated first: id, title, status, priority, category, requester, technician, entity, and when opened…
glpi_get_ticketOne GLPI ticket in full: title, status, type, priority, urgency, impact, category, entity, dates (server time zone), the description…
glpi_list_assetsGLPI assets of one type (computers, network equipment, monitors, peripherals, phones, printers or software): id, name, type, model, manufacturer…
glpi_search_usersFind GLPI users by login name, to get the user id that glpi_assign_ticket_user, glpi_add_ticket_task and the asset actions take: id, login…
glpi_search_groupsFind GLPI groups by name, to get the group id glpi_assign_ticket_group takes: id, name and full path.

Acts, when you ask

These change something in GLPI. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

glpi_create_ticketCreates a ticket in GLPI as the connection's user (who becomes the requester), with GLPI's e-mail notifications switched off for the creation…
glpi_add_followupAdds a follow-up (a comment) to a GLPI ticket as the connection's user, private by default so only technicians see it…
glpi_update_ticketChanges fields of a GLPI ticket, REPLACING what is there: title, description (the whole description is overwritten), status…
glpi_assign_ticket_userAdds a GLPI user to a ticket as its assigned technician (or, when asked, as an observer or requester), by user id from glpi_search_users.
glpi_assign_ticket_groupAdds a GLPI group to a ticket as the assigned group (or, when asked, as an observer or requester group), by group id from glpi_search_groups.
glpi_solve_ticketNOTIFIES THE REQUESTER.
glpi_add_ticket_taskAdds a task to a GLPI ticket as the connection's user: the text, private by default, and optionally the technician it is for (a user id)…
glpi_create_problemCreates a GLPI problem (root-cause record) as the connection's user, from a title and description, optionally with urgency…
glpi_create_changeCreates a GLPI change request as the connection's user, from a title and description, optionally with urgency, impact and an ITIL category…
glpi_create_assetCreates an inventory item in GLPI (a computer, monitor, printer, phone, network device or peripheral) with a name and optionally a serial, comment…
glpi_update_assetChanges fields of a GLPI inventory item, REPLACING what is there: name, serial, comment (the whole comment is overwritten), status, location…
glpi_delete_assetDESTRUCTIVE, deletes a GLPI inventory item.
glpi_delete_ticketDESTRUCTIVE, deletes a GLPI ticket.

Connect it

First connect GLPI on Dashboard → Connections, then add Memtro to your client once. The GLPI tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared GLPI connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Which GLPI tickets are open for Dan Fletcher?
› What did the technician last write on ticket 4127?
› Which laptops are assigned to Priya Nair, and what are their serial numbers?
› Add a private follow-up to ticket 4127 saying the replacement charger has been ordered
› Assign ticket 4130 to the network group and set its urgency to high

Questions

Is this an official GLPI MCP server?: No. It is Memtro's MCP server with Memtro's GLPI connector behind it: the connector reads GLPI through its API with the credentials you connect on Dashboard → Connections, and GLPI publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in GLPI?: Only when you ask, and only what it has been granted: create a ticket (no notification is sent); add a follow-up to a ticket, private by default (no notification is sent); change a ticket's title, description, status, urgency, impact, priority or category; delete a ticket, to the trash or purged for good; assign a technician, observer or requester to a ticket; assign a group to a ticket; solve a ticket with a solution (notifies the requester); add a task to a ticket, private by default (no notification is sent); create a problem (no notification is sent); create a change (no notification is sent); create an inventory item (computer, monitor, printer, phone, network device or peripheral); change an inventory item's name, serial, comment, status, location, manufacturer, user or technician; delete an inventory item, to the trash or purged for good. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.