# Matrix42 [Health: Active]

**Category:** 🎧 Support & Service Management  
**Repository:** https://github.com/sus-tech-gmbh/matrix42-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/matrix42

## Description
MCP server for Matrix42: explore the API and data model, search the service desk, act on tickets

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "matrix42": {
    "command": "npx",
    "args": ["-y","matrix42-mcp"],
    "env": {
      "M42_HOST": "",
      "M42_API_TOKEN": "",
      "M42_USERNAME": "",
      "M42_PASSWORD": ""
    }
  }
}
```

**Requires environment variables:** `M42_HOST`, `M42_API_TOKEN`, `M42_USERNAME`, `M42_PASSWORD` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Matrix42 MCP server does

The Matrix42 MCP server gives an MCP-compatible assistant access to a Matrix42 instance through the Matrix42 REST API. It supports API and data-model discovery, record queries, service-desk searches, and selected ticket operations. The server is intended for the Support & Service Management category and can help an assistant work with Matrix42 without requiring users to identify service IDs, field names, or endpoint paths manually.

The server resolves fields against the live instance schema before running queries. This lets it report unavailable attributes instead of sending an invalid request. It also provides guides as MCP resources for the data model, schema, ASQL filtering, and REST conventions.

## How it works

An MCP client starts the server over stdio, typically with `npx`. The server stores the Matrix42 connection settings and communicates with the configured instance on the assistant’s behalf. API tokens are exchanged for short-lived access tokens automatically; basic authentication is also supported, although the project advises using an API token. Credentials are not passed to the assistant.

Read-only behavior is the default. Tools that modify Matrix42 data are not registered unless `M42_ALLOW_WRITES=1` is set. When writes are enabled, ticket changes first return a preview of the request. The operation runs only after the caller supplies confirmation. Notification email is disabled by default, journal entries are internal, and cascading ticket closure must be opted into.

## Setup and configuration

The Matrix42 MCP server requires Node.js 22.19 or newer, a Matrix42 instance, and either an API token or a username/password pair. Set `M42_HOST` to the instance base URL. Authentication uses `M42_API_TOKEN`, or the alternative `M42_USERNAME` and `M42_PASSWORD` variables.

Optional settings control response language, exposed tools, write access, TLS verification, audit notes, the assistant label, the Matrix42 web-interface URL, and request timeouts. `M42_ALLOW_INSECURE_TLS=1` is intended only for development instances with self-signed certificates. The package can be run with `npx matrix42-mcp` and is documented for Claude Code, Claude Desktop, Cursor, and VS Code.

## Tools and capabilities

The Matrix42 MCP server can:

- Discover web services, operations, request contracts, return contracts, and update-safety information.
- Inspect data definitions, configuration items, pickup values, relations, and cardinality.
- Query records with ASQL filters, paging, saved views, journals, attachments, and web-interface links.
- Search seven ticket types by name, service level, curated domains, or across all supported types.
- Create, close, classify, take over, forward, pause, reopen, and update ticket deadlines, as well as track time, when write tools are enabled.

## Limitations and notes

This is an independent community project and is not affiliated with, endorsed by, sponsored by, or supported by Matrix42 AG. It is an early release provided under the MIT license, with community support through GitHub issues rather than a service-level agreement. Basic authentication may be accepted by a Matrix42 instance but still fail with HTTP 403 because of role or audience restrictions. Disabling TLS verification should be limited to suitable development environments.

_Full upstream README: https://allmcps.com/mcp/matrix42/readme_