Skip to main content
Glama
sudohakan

infoset-mcp

by sudohakan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to infoset-mcp

No user-submitted related servers found.

    Related Servers

    • amoCRM MCP Server

      DocAtWork2026
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for amoCRM integration, enabling AI assistants to manage leads, contacts, companies, tasks, and more via natural language.
      4
      MIT

    • Bitrix24 MCP Server

      Ostor
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for integrating AI assistants with Bitrix24, enabling retrieval and management of CRM entities, tasks, scrum, and knowledge bases through natural language.
      5 npm
      1
      -

    • mcp-creatio

      CRACKISH
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Creatio CRM that enables AI assistants to read, create, update, delete records, execute business processes, and manage settings via OData and REST APIs.
      18
      30 npm
      6
      MIT

    • Nimbus Copiloto MCP Server

      ruben-salas20
      F
      license
      A
      quality
      B
      maintenance
      MCP server for the Nimbus helpdesk that enables an AI assistant to manage support tickets, search cases, escalate issues, send responses, and track SLA compliance.
      3
      -

    • GHL MCP Server

      northrosetech
      A
      license
      B
      quality
      D
      maintenance
      A comprehensive MCP server that connects AI assistants to GoHighLevel CRM, enabling management of contacts, conversations, calendars, pipelines, payments, and more through 60+ tools.
      64
      39 npm
      1
      MIT

    • 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

    A3.5/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools are distinct, with clear single vs batch and get vs list/search separations. The only potential confusion is between list_tickets and search_tickets, but their descriptions (filters vs keyword) delineate their purposes.

    Naming Consistency5/5

    All tool names follow the consistent pattern infoset_<verb>_<noun>, using snake_case throughout. Verbs like get, list, search, create, update, and batch_get are used predictably, and batch operations are uniformly prefixed with 'batch_get'.

    Tool Count4/5

    With 16 tools, the server is slightly over the typical 3-15 range, but the domain encompasses tickets, contacts, companies, emails, and SLA data, justifying the count. The batch operations add a few extra tools but serve a clear performance purpose.

    Completeness4/5

    Core ticket workflows (create, read, update, list, search, logs, SLA) are covered, along with contact/company read operations. Minor gaps exist such as no delete endpoints and no write operations for contacts or companies, but these do not impede primary use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources