Skip to main content
Glama
Guipegoraro

totvs-tickets-mcp

by Guipegoraro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to totvs-tickets-mcp

No user-submitted related servers found.

    Related Servers

    • thinker-mcp by thinker-ci

      thinker-mcpofficial

      thinker-ci
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for thinker-ci, exposing tickets, CI/CD pipelines, project management data, and AI-agent sessions as tools and resources for Claude Code and other MCP clients.
      -

    • pipedrive-pj

      hguareromanoo
      F
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server that exposes the Poli Júnior Pipedrive CRM to Claude as composable tools.
      -

    • brasil-data-mcp

      alanpcf
      A
      license
      A
      quality
      A
      maintenance
      MCP server providing access to Brazilian public data (CNPJ, CEP, banks, holidays) via BrasilAPI. For Claude Desktop, Claude Code, Cursor, and other MCP-compatible clients.
      15
      22 npm
      8
      MIT

    • MCP Tool Agent

      chigurupatiakhil5
      F
      license
      Not graded
      quality
      D
      maintenance
      A custom MCP server exposing database, ticketing, and external-API tools to both Claude Desktop and a self-built autonomous agent powered by Groq's free-tier LLaMA 3.3.
      -
    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.9/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: contact info, departments, notifications count, ticket comments, ticket detail, filter options, ticket listing, priority reasons, status list, user search, and identity info. No two tools overlap in functionality.

    Naming Consistency4/5

    All tools start with 'totvs_' followed by a descriptive noun or noun_action. There is a minor inconsistency between singular and plural forms (e.g., 'totvs_ticket_comentarios' vs 'totvs_tickets_listar'), but the overall pattern is predictable and clear.

    Tool Count5/5

    With 11 tools covering identity, search, filtering, and ticket details, the count is well-scoped for a ticket support portal. It provides sufficient functionality without being excessive.

    Completeness2/5

    The tool set is heavily read-oriented, lacking essential create, update, or close operations for tickets. While it covers querying and listing well, there are no tools to modify tickets, making the surface incomplete for full ticket lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources