Skip to main content
Glama
raylann-lopes

MCP Movidesk Server

by raylann-lopes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP Movidesk Server

No user-submitted related servers found.

    Related Servers

    • mcp-movidesk

      ferronicardoso
      A
      license
      A
      quality
      B
      maintenance
      Enables natural language interaction with the Movidesk public API for managing tickets and persons/organizations, including CRUD operations and file attachments.
      10
      13 npm
      2
      MIT

    • Freshdesk MCP Server

      Sidd07Dev
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to interact with Freshdesk, supporting ticket management, customer and company operations, agent lookup, and knowledge base search through natural language.
      19
      MIT

    • Freshdesk MCP Server

      nikhilchintawar
      A
      license
      A
      quality
      D
      maintenance
      Enables fetching and searching Freshdesk tickets, including details like conversations, attachments, and custom fields, via natural language queries.
      3
      244 npm
      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

    A4.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a clear, distinct resource and action: ticket creation, ticket retrieval, knowledge search, interaction addition, ticket listing by client, client lookup, status change, and agent assignment. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in Portuguese, using snake_case throughout (e.g., criar_ticket, consultar_ticket, alterar_status_ticket). The naming is predictable and readable, with no mixed conventions.

    Tool Count5/5

    With 8 tools, the server provides a focused set that covers the core ticket management workflow without being bloated or too thin. Each tool serves a distinct function, making the count well-scoped for the domain.

    Completeness4/5

    The core ticket lifecycle is covered: create, retrieve, list by client, add interactions, change status, and assign. Minor gaps include lack of a general list-all-tickets endpoint and no update/delete for tickets, but these are workable for a support-focused toolset.

    Resources