Skip to main content
Glama
rushikeshsakharleofficial

sdp-mcp

by rushikeshsakharleofficial
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to sdp-mcp

No user-submitted related servers found.

    Related Servers

    • Service Desk Plus MCP Server

      PTTG-IT
      F
      license
      Not graded
      quality
      F
      maintenance
      Integrates with Service Desk Plus Cloud API to enable AI assistants perform CRUD operations on service desk entities, including request management, technician management, and email communication.
      3
      -

    • Freshservice MCP Server

      tannertm0
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to connect with Freshservice ITSM for managing tickets, assets, agents, and organizational data through natural language. It provides a comprehensive set of tools for performing CRUD operations on service desk records and searching across the Freshservice platform.
      53
      61 npm
      1
      MIT

    • Tiflux

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query and operate a help desk and service desk through MCP over HTTP, including tickets, requester communications, internal notes, attachments, stage and SLA history, time entries, clients, requesters, desks, knowledge base, contracts, and billing/satisfaction reports.
      MIT

    • Freshservice MCP Server

      LeeMangold
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models to interact with Freshservice IT service management platform, allowing automated ticket management, change requests, asset tracking, and solution article operations through natural language commands.
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    C2/5.0

    Scored across 46 tools

    Disambiguation3/5

    Several tools operate on the same resource with overlapping but distinguishable actions (update_request, assign_request, pickup_request, close_request), and get_task vs get_request_task plus delete_change vs trash_change create boundary confusion. The generic sdp_call overlaps with every specific tool, which can cause an agent to bypass them entirely.

    Naming Consistency4/5

    Most tool names follow a clear snake_case verb_noun pattern (list_requests, create_change, update_project, delete_user). Minor deviations exist: sdp_call breaks the verb_noun convention, and delete_change vs trash_change uses different verbs for similar removal semantics.

    Tool Count2/5

    46 tools is well above the 25-tool threshold for 'too many', even for a broad ITSM domain. Many CRUD and sub-resource operations could be consolidated, and the presence of sdp_call as a catch-all makes the large specific surface less necessary.

    Completeness3/5

    The surface covers core CRUD for requests, changes, projects, tasks, and users, including sub-resources like notes and request tasks. However, gaps exist: no list for request resolutions, inconsistent trash/delete semantics across resources, and missing approval or workflow operations. The sdp_call escape hatch can fill gaps but requires endpoint knowledge.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources