Skip to main content
Glama
JonnadulaNagaSambaSivaRao

Customer Support MCP Server

by JonnadulaNagaSambaSivaRao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Customer Support MCP Server

No user-submitted related servers found.

    Related Servers

    • DataBook

      Ethan2298
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage and query SQLite databases through MCP tools, supporting CRUD operations, schema management, and saved views.
      4 npm
      MIT

    • @lubo3395/mcp-sqlite-server

      lubo3395
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a set of MCP tools to let AI assistants like Claude, Cursor, and VS Code Copilot interact with SQLite databases, supporting querying, schema management, and data import/export.
      17 npm
      MIT

    • agent-crm

      clayton
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage CRM data including companies, contacts, prospects, pipelines, forecasts, and tasks via typed MCP tools, with local SQLite storage and a JSON CLI.
      MIT

    • OpsBridge MCP

      ivantagesam
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to search and retrieve customer and support-ticket data from a SQLite database, and to create support tickets only when an explicit approval flag is supplied, with all actions validated and audit-logged.
      -

    • mcp-sqlite

      mgcrea
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP tool server providing SQLite database access for AI agents.
      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.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: create, retrieve by ID, search with filters, and update. No overlapping functionality, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: create_ticket, get_ticket, search_tickets, update_ticket. Minor pluralization in search_tickets is acceptable and consistent with typical search APIs.

    Tool Count5/5

    Four tools cover the essential ticket operations without bloat. The count is well-scoped for a customer support server, fitting the ideal range of 3-15 tools.

    Completeness5/5

    The server provides full CRUD-like coverage (create, read, search, update) for tickets. Closing a ticket is achievable via update_ticket's status parameter, so no critical lifecycle gaps exist.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources