Skip to main content
Glama
SaADii09

MCP OpsBridge

by SaADii09
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MCP OpsBridge

No user-submitted related servers found.

    Related Servers

    • mcp-github-server

      sheeryn123
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-grade MCP server providing 18 tools for comprehensive GitHub interaction, including repository management, issues, pull requests, code search, and CI/CD status, with Redis caching and rate limit handling.
      9
      MIT

    • MCP Setup Server

      lakshmidevi2016
      F
      license
      Not graded
      quality
      D
      maintenance
      A modular MCP server exposing tools for integrating with services like GitHub, Redash, Jenkins, Figma, Jira, Confluence, Teams, Datadog, PagerDuty, Slack, and Presto, enabling users to manage these platforms through natural language via an MCP client.
      -

    • mcp-guarded-tools

      ridwanspace
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that exposes 43 domain tools behind 4 meta-tools, applying guardrails such as budgets, rate limits, schema validation, human-in-the-loop confirmation for mutations, PII redaction, and an append-only audit log while reducing context window usage.
      4
      MIT

    • MCP-NG

      Lotargo
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      A high-performance Go-based MCP server that provides a microservice architecture for orchestrating diverse tools through gRPC and HTTP/REST APIs. Enables seamless integration of language-agnostic tools including ML capabilities, web search, calculations, and human interaction for intelligent agent workflows.
      2
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 30 tools

    Disambiguation5/5

    Every tool is clearly namespaced by service (github_, calendar_, db_, slack_) and performs a distinct action. No two tools have overlapping purposes; even similar actions like calendar_query_events and calendar_get_event_details are clearly differentiated.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern of domain_verb_noun (e.g., github_search_issues, db_execute_query, slack_send_message). The standalone approve_action still fits the verb_noun convention. No naming style mixing.

    Tool Count2/5

    At 30 tools, the server exceeds the 25+ threshold for 'too many'. While the tools are grouped by service, the overall count is heavy for a single MCP server and could overwhelm agents. Splitting into separate domain servers would be more appropriate.

    Completeness3/5

    Calendar, database, and Slack domains have full lifecycle coverage (CRUD and actions). However, the GitHub domain is read-only—no create/update/merge operations—which is a notable gap for an ops bridge. Also missing some actions like Slack message deletion or calendar availability beyond free slots.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources