Skip to main content
Glama
ibm-client-engineering

concert-operate-mcp

Official
by ibm-client-engineering
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to concert-operate-mcp

No user-submitted related servers found.

    Related Servers

    • IBM Concert MCP Server

      riminator
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that connects AI agents to IBM Concert, enabling autonomous workflow health monitoring, incident diagnosis, auto-remediation, CVE triage, and Slack alerting through natural language.
      Apache 2.0

    • OpenAPI MCP Server

      luciVuc
      A
      license
      Not graded
      quality
      D
      maintenance
      A generic MCP server that dynamically converts OpenAPI-defined REST APIs into tools for LLMs like Claude. It supports multiple authentication methods and transport protocols, enabling seamless interaction with any OpenAPI-compliant API.
      8 npm
      MIT

    • opsgenie-mcp

      MSPbotsAI
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Opsgenie (Atlassian's incident/alert management and on-call platform) exposing the full public Opsgenie REST API as MCP tools.
      -

    • hmc-mcp

      randomparity
      A
      license
      A
      quality
      A
      maintenance
      MCP server and CLI for IBM HMC REST API, enabling AI agents to inventory Power systems, manage LPARs/VIOS, and submit jobs like power on/off, with tools for adapters, storage, networking, and more.
      100
      1
      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

    C2.6/5.0

    Scored across 97 tools

    Disambiguation4/5

    Most tools follow a clear resource+action pattern, making them distinct. However, some tools like get-metering-job, get-metering-job-status, and get-metering-job-result provide overlapping views of the same entity, which could cause confusion.

    Naming Consistency4/5

    The naming convention is strongly consistent, using lowercase verb-noun pairs with hyphens (e.g., create-event, get-alerts, update-policy). Minor deviations like the admin- prefixed tools (admin-get-user-preferences) are systematic and do not undermine overall coherence.

    Tool Count1/5

    With 97 tools, this server is massively over-scoped. It will overwhelm agents with too many options and consume excessive context, making selection and reasoning difficult. The server should be decomposed into smaller, focused servers.

    Completeness4/5

    The tool surface is remarkably comprehensive across many modules (alerts, policies, runbooks, training, etc.), with full CRUD where appropriate. Some gaps exist, such as no delete-alert or create/delete-incident, but overall coverage is strong for the apparent domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources