Matrix42
Matrix42 Enterprise Service Management: query any configuration item, incident, service request, asset or user with Matrix42's fragment query API. Bearer token minted from an API token against your own instance.
7 天免费 · 无需信用卡 · EU 托管
问 Matrix42 任何事
通过 AnythingMCP 对 Matrix42 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 Matrix42Claude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Matrix42。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
配置 Matrix42
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
Setup
- In Matrix42 open Administration → Integration → API Tokens and create a token for a service account with the roles the agent needs. Matrix42 applies role-based access on top of the API, so a restricted account sees fewer fragments.
- Set
MATRIX42_URLto your instance root (e.g.https://esm.example.com/M42Services, no trailing slash) andMATRIX42_API_TOKENto the token. - The adapter exchanges that token for a short-lived bearer at
/api/ApiToken/Tokenand refreshes it automatically. AnythingMCP stores the bearer encrypted inconnector_auth_cache.
Everything is a fragment. Matrix42's data model is Configuration Items made of typed fragments: SPSActivityTypeIncident for an incident, SPSAssetClassBase for an asset, SPSScUserClassBase for a user. The query API takes the fragment name plus the columns you want, and returns rows. There is no per-entity REST path — this is why every tool here takes a fragmentName.
columns is not optional in practice. Matrix42 fragments have dozens of columns and omitting the list returns all of them. Name what you need.
where is SQL-flavoured, e.g. State = 3 AND CreatedDate > '2026-09-01'. Column names are the fragment's, which differ from the labels shown in the web UI. matrix42_get_fragment_schema returns the real names.
$skip / $top page the result. There is no cursor.
Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. A correction from anyone running this against a real system is genuinely welcome.
Self-hosted, which is the thing to plan for.
- On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch.
- On an internal host (
esm.intern,10.0.0.x), self-host AnythingMCP on the same network and add that host toSSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.