Skip to main content
Glama
ruben-salas20

Nimbus Copiloto MCP Server

by ruben-salas20
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Nimbus Copiloto MCP Server

No user-submitted related servers found.

    Related Servers

    • soporte-ti-mcp

      raulperez0798
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides IT support tools to search known incidents, check ticket status, and create ticket drafts, enabling an AI assistant to help users with IT support queries.
      -

    • servicedesk-plus

      kaattaalan
      A
      license
      A
      quality
      C
      maintenance
      MCP server for ManageEngine ServiceDesk Plus that lets AI agents list, search, create, update, and manage help desk tickets and technical notes in real-time.
      6
      MIT
    • tickiti-mcp by tickiti

      tickiti-mcpofficial

      tickiti
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that exposes the Tickiti helpdesk API to AI assistants, enabling ticket management and helpdesk operations via natural language.
      11
      MIT

    • MCP Server for Intercom

      raoulbia-ai
      A
      license
      A
      quality
      D
      maintenance
      An MCP-compliant server that enables AI assistants like Claude Desktop to access and analyze Intercom support tickets with full conversation history.
      4
      8
      Apache 2.0

    • nimbus-ops

      vasanthadevi
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Nimbus Operations Copilot that enables AI agents to search help docs, customer data, invoices, and tickets, and propose refunds/tickets with human approval for writes.
      -
    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.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: ping checks server liveness, listar_estados_de_ticket provides reference information about ticket states, and consultar_ticket retrieves a specific ticket's data. There is no ambiguity or overlap between them.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern (ping, listar_estados_de_ticket, consultar_ticket). Although 'ping' is a single verb, it is a standard convention and the other two follow the same style, ensuring predictability.

    Tool Count5/5

    With 3 tools, the server is appropriately scoped for its narrow purpose of ticket status lookup and retrieval. Each tool is essential and there are no redundant or missing operations for the stated functionality.

    Completeness4/5

    The server covers the core read operations: checking health, listing possible ticket states, and fetching a specific ticket. A notable gap is the lack of a 'list_all_tickets' tool, but given the description, the server appears intentionally focused on individual ticket queries, so this is a minor omission rather than a critical failure.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources