Skip to main content
Glama

sdp-mcp

MCP server for the ManageEngine ServiceDesk Plus v3 REST API.

Configure

Requires Node.js 22 or newer. Keep credentials in a restricted environment file (such as ~/.admin/.env, mode 600), never in command arguments or committed files.

npm ci
# Set SDP_BASE_URL and one authentication variable in the client environment.
npm start

Set one authentication variable:

Variable

Purpose

SDP_AUTHTOKEN

Native SDP v3 authtoken (preferred).

SDP_API_KEY

Backward-compatible alias; sent as both authtoken and TECHNICIAN_KEY.

SDP_OAUTH_TOKEN

OAuth bearer token.

SDP_EMAIL

Acting technician email for OAuth.

SDP_TIMEOUT_MS

Positive request timeout in milliseconds; default 30000.

Related MCP server: Freshservice MCP Server

Tools

Dedicated tools cover the following v3 routes; availability and permissions depend on the SDP version and tenant:

  • Requests: list, get, create, update, close, assign, pickup, trash, restore, summary, resolution, notes, and tasks.

  • Changes, projects, general tasks, and users: list, get, create, update, and delete.

  • Change trash and restore.

assign_request uses PUT /requests/{id}, not the tenant-specific /assign action. Provide both technician and group objects. The group must belong to the target technician; do not reuse the request's current group when handing off between L1 and L2. For example, Pramod Patil uses { "id": "315", "name": "L2-Server Administrator", "site": null } for non-Webwerks sites.

save_request_draft saves an unsent public reply in the ticket's draft panel. It requires the recipient addresses and a description; a plain-text description is treated as plain text and converted to HTML (newlines become <br />, special characters are escaped). For an HTML description, set description_format to html to pass it through unchanged. It never sends the message.

Every other endpoint

Use sdp_call. It accesses any path after /api/v3/; all write payloads are sent as URL-encoded input_data. Object bodies are JSON-serialized; string bodies are sent verbatim, including an empty string for change restoration. Query parameters accept strings, numbers, booleans, and null (omitted).

The base URL may include a deployment context path, but must not include credentials, a query, or a fragment. Dedicated IDs must be positive integers (use strings for large IDs). API paths must not contain dot segments, percent escapes, whitespace, backslashes, queries, or fragments.

Calls reject redirects, honor MCP cancellation, and time out without automatic retries. A timed-out write may already have reached SDP; check its state before retrying. HTTP errors, SDP failure statuses, and non-JSON responses are tool errors. Configured authentication tokens are redacted from tool output. For internal CAs, set NODE_EXTRA_CA_CERTS; do not disable TLS verification.

Example:

{
  "method": "POST",
  "endpoint": "requests/123/conversations",
  "body": { "conversation": { "content": "Update", "is_public": true } }
}

Development

npm test

The test suite uses isolated credentials and local mock servers to check MCP registration, validation, wire formats, API failures, redirects, redaction, timeouts, and cancellation. It does not verify live tenant permissions or writes.

Available Tools

46 tools
add_request_noteAdd Request noteD

Add a request note.

Inputs: body (required), request_id (required).

add_request_resolutionAdd Request ResolutionC

Add or update a resolution.

Inputs: body (required), request_id (required).

add_request_taskAdd Request taskD

Add a request task.

Inputs: body (required), request_id (required).

assign_requestAssign RequestB

Assign through the normal request update route. The group must belong to the target technician; do not copy the request's current group when changing L1/L2 ownership.

Inputs: group (required), request_id (required), technician (required).

close_requestClose RequestD

Close with closure_info.

Inputs: request_id (required), closure_info (required).

create_changeCreate changeD

Create a change.

Inputs: body (required).

create_projectCreate projectD

Create a project.

Inputs: body (required).

create_requestCreate RequestD

Create a request.

Inputs: body (required).

create_taskCreate taskD

Create a task.

Inputs: body (required).

create_userCreate userD

Create a user.

Inputs: body (required).

delete_changeDelete changeC

Delete a change.

Inputs: change_id (required).

delete_projectDelete projectC

Delete a project.

Inputs: project_id (required).

delete_requestDelete RequestA

Trash a request, or permanently delete it with force.

Inputs: request_id (required), force.

delete_request_noteDelete Request noteC

Delete a request note.

Inputs: note_id (required), request_id (required).

delete_request_taskDelete Request taskD

Delete a request task.

Inputs: task_id (required), request_id (required).

delete_taskDelete taskC

Delete a task.

Inputs: task_id (required).

delete_userDelete userD

Delete a user.

Inputs: user_id (required).

get_changeGet changeD

Get a change.

Inputs: change_id (required).

get_projectGet projectD

Get a project.

Inputs: project_id (required).

get_requestGet RequestD

Get a request.

Inputs: request_id (required).

get_request_noteGet Request noteD

Get a request note.

Inputs: note_id (required), request_id (required).

get_request_resolutionGet Request ResolutionD

Get a resolution.

Inputs: request_id (required).

get_request_summaryGet Request SummaryD

Get request counts.

Inputs: request_id (required).

get_request_taskGet Request taskD

Get a request task.

Inputs: task_id (required), request_id (required).

get_taskGet taskD

Get a task.

Inputs: task_id (required).

get_userGet userD

Get a user.

Inputs: user_id (required).

list_changesList changesD

List changes.

Inputs: list_info.

list_projectsList projectsD

List projects.

Inputs: list_info.

list_request_notesList Request notesD

List request notes.

Inputs: request_id (required), list_info.

list_requestsList RequestsC

List requests.

Inputs: list_info.

list_request_tasksList Request tasksD

List request tasks.

Inputs: request_id (required), list_info.

list_tasksList tasksD

List tasks.

Inputs: list_info.

list_usersList usersC

List users.

Inputs: list_info.

pickup_requestPick Up RequestC

Assign to the authenticated technician.

Inputs: request_id (required).

restore_changeRestore ChangeC

Restore a change from trash.

Inputs: change_id (required).

restore_requestRestore RequestC

Restore a request from trash.

Inputs: request_id (required).

save_request_draftSave Request Reply DraftB

Save an unsent public reply draft. It never sends the message.

Inputs: to (required), subject (required), request_id (required), description (required), +3 more.

sdp_callGeneric SDP API CallB

Call any SDP v3 endpoint. Write bodies are form-encoded as input_data; string bodies are sent verbatim.

Inputs: method (required), endpoint (required), body, params.

trash_changeTrash ChangeC

Move a change to trash.

Inputs: change_id (required).

update_changeUpdate changeD

Update a change.

Inputs: body (required), change_id (required).

update_projectUpdate projectD

Update a project.

Inputs: body (required), project_id (required).

update_requestUpdate RequestD

Update a request.

Inputs: body (required), request_id (required).

update_request_noteUpdate Request noteD

Update a request note.

Inputs: body (required), note_id (required), request_id (required).

update_request_taskUpdate Request taskD

Update a request task.

Inputs: body (required), task_id (required), request_id (required).

update_taskUpdate taskD

Update a task.

Inputs: body (required), task_id (required).

update_userUpdate userD

Update a user.

Inputs: body (required), user_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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.

    Related MCP Connectors

    Related MCP Servers

    • 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
    • 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
      293 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      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.
      4
      -