Skip to main content
Glama
sus-tech-gmbh

matrix42-mcp

by sus-tech-gmbh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to matrix42-mcp

No user-submitted related servers found.

    Related Servers

    • MCP IT Ops Server

      m3yyyyy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to perform safe, read-only IT diagnostics and retrieve local runbooks, asset records, and knowledge articles through MCP, with allowlisted network checks and audit logging.
      MIT

    • SQL Server MCP Server

      Claritas-LLC
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to inspect schemas, analyze performance, check security, and troubleshoot SQL Server 2019+ databases through a safe, controlled interface.
      -

    • MCP SQL Server

      WendellOttoni
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to explore SQL Server schemas, relationships, and execute safe SQL queries with read-only mode by default and optional write control.
      1
      MIT

    • dynatrace-bridge-mcp

      yunusemregul
      A
      license
      A
      quality
      A
      maintenance
      Lets AI assistants query Dynatrace Managed environments — services, traces, metrics, pods, and problems — by running read-only GET requests through your already logged-in browser session, so no API tokens are needed. All traffic stays on your machine between the AI client, a local server, and a browser extension.
      39
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool maps to a distinct layer: connection info, API metadata, schema metadata, generic data queries, and curated service-desk reads. The potential overlap between data_query and service_desk is explicitly resolved by framing data_query as the ASQL/record-level interface and service_desk as the curated domain interface.

    Naming Consistency5/5

    All tool names are lowercase snake_case two-word compounds (server_info, webservice_discovery, schema_discovery, data_query, service_desk) with no mixed conventions or vague verbs. The naming pattern is predictable and matches each tool's role in the set.

    Tool Count5/5

    Five top-level tools is well-scoped for a Matrix42 integration; each tool covers a coherent area and earns its place. The internal actions are many, but grouping them by capability keeps the surface manageable.

    Completeness4/5

    The read and discovery side is very comprehensive: API conventions, schema exploration, ASQL validation, generic queries, views, journal/attachements, ticket search/SLA, and curated domain browsing all chain together cleanly. The only notable limitation is that the entire server is read-only—no create/update/delete or ticket-lifecycle actions—so agents that need to act on Matrix42 records will dead-end unless this is intentionally a read-only assistant.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources