Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Integrates with Service Desk Plus Cloud API to enable AI assistants to manage IT service requests, technicians, and communications via natural language.

README.md

Service Desk Plus MCP Server

A Model Context Protocol (MCP) server that integrates with Service Desk Plus Cloud API, enabling AI assistants to perform CRUD operations on all Service Desk Plus entities.

🚀 Current Status (January 2025)

🎉 PRODUCTION READY - Complete Service Desk Plus MCP Server ✅ ALL 16 TOOLS WORKING PERFECTLY (100% Success Rate) ✅ Enterprise Grade - Full ITSM integration with comprehensive OAuth scopes ✅ Email Communication - Reply to requesters with ticket conversation integration ✅ Zero OAuth Issues - Bulletproof token management with rate limit protection ✅ Complete Testing - All tools validated through comprehensive client testing ✅ Production Ready - Robust error handling and business rule compliance

Recent Improvements

  • 🔧 Fixed Authorization header format from Bearer to Zoho-oauthtoken
  • 🔧 Added subcategory as mandatory field for request creation
  • 🔧 Implemented proper list_info structure with search_criteria
  • 🔧 Added advanced search capabilities with complex criteria
  • 🔧 Created comprehensive OAuth and search documentation
  • 🔧 Mock API now perfectly replicates real API behaviors
  • 🔧 NEW: Email communication tools for requester replies
  • 🔧 NEW: Private notes and first response functionality
  • 🔧 NEW: Full conversation history retrieval

Tool Status

  • list_requests - Working with proper search_criteria
  • get_request - Working
  • search_requests - Enhanced with advanced criteria support
  • get_metadata - Working
  • add_note - Working
  • reply_to_requester - NEW - Email reply functionality working
  • add_private_note - NEW - Private notes working
  • send_first_response - NEW - First response with email working
  • get_request_conversation - NEW - Conversation history working
  • list_technicians - Working with fallback to /users endpoint
  • get_technician - Working
  • find_technician - Working
  • create_request - Fixed with subcategory support
  • update_request - Working (priority updates blocked by API design)
  • close_request - Working with proper closure handling
  • claude_code_command - Working

Working Implementation

  • Architecture: Direct MCP protocol over Server-Sent Events (SSE)
  • Location: sdp-mcp-server/src/working-sse-server.cjs
  • Status: All Service Desk Plus tools operational
  • Client: Successfully tested with Claude Code

📋 Available Tools

Request Management

  1. list_requests - List service desk requests with optional filters
  2. get_request - Get detailed information about a specific request
  3. search_requests - Search requests using various criteria
  4. create_request - Create new service desk requests
  5. update_request - Update existing requests
  6. close_request - Close requests with closure information
  7. add_note - Add notes to existing requests

Email Communication (NEW)

  1. reply_to_requester - Send email reply to requester (appears in ticket conversation)
  2. add_private_note - Add private note not visible to requester
  3. send_first_response - Send first response with email notification
  4. get_request_conversation - Get full conversation history

Technician Management

  1. list_technicians - List available technicians for assignment
  2. get_technician - Get detailed technician information
  3. find_technician - Find technician by name or email

Utilities

  1. get_metadata - Get valid field values for dropdowns
  2. claude_code_command - Execute Claude Code commands

🔧 Recent Fixes & Improvements

OAuth Authentication

  • Fixed authorization header format: Zoho-oauthtoken instead of Bearer
  • Implemented singleton OAuth client to prevent rate limiting
  • Added global refresh lock to prevent concurrent token refreshes
  • Tokens now properly reused until expiry

API Field Handling

  • Added mandatory subcategory field for request creation
  • Fixed status filtering using proper search_criteria format
  • Implemented API maximum of 100 rows per request
  • Added support for complex search queries with logical operators

Mock API Server

  • Complete replication of real API behaviors
  • Includes all error responses and business rules
  • Test data includes Clay Meuth technician (ID: 216826000000006907)
  • Supports both /technicians and /users endpoints

🔧 Quick Start

Prerequisites

  • Node.js 18+
  • Service Desk Plus Cloud account with OAuth credentials
  • Permanent refresh token (never expires!)

Setup

  1. Clone the repository
git clone https://github.com/PTTG-IT/SDP-MCP.git
cd SDP-MCP/sdp-mcp-server
  1. Install dependencies
npm install
  1. Configure environment
cp .env.example .env
# Edit .env with your OAuth credentials
  1. Start the server
./start-sse-server.sh

The server will start on port 3456.

Client Configuration

For Claude Code or other MCP clients:

{
  "mcpServers": {
    "service-desk-plus": {
      "command": "npx",
      "args": ["mcp-remote", "http://localhost:3456/sse", "--allow-http"]
    }
  }
}

For remote access: ``json { "mcpServers": { "service-desk-plus": { "command": "npx", "args": ["mcp-remote", "http://192.168.2.10:3456/sse", "--allow-http"] } } } ``

For Windows VS Code: ``json { "mcpServers": { "service-desk-plus": { "command": "npx", "args": ["-y", "mcp-remote", "http://10.212.0.7:3456/sse", "--allow-http"] } } } ``

🧪 Testing with Mock API

The project includes a complete mock API server for safe testing:

# Start mock API server (port 3457)
npm run mock:api

# Use mock API with SSE server
export SDP_USE_MOCK_API=true
./start-sse-server.sh

The mock API:

  • Replicates exact error responses from real API
  • Enforces same business rules (can't update closed tickets)
  • Includes test data with is_mock: true identifier
  • Perfect for development and testing

📚 Documentation

Knowledge Base

  • example/knowledge/service-desk-plus-authentication.md - OAuth implementation guide
  • example/knowledge/service-desk-plus-oauth-complete.md - Complete OAuth reference
  • example/knowledge/service-desk-plus-search-criteria.md - Advanced search guide
  • example/knowledge/service-desk-plus-mandatory-fields.md - Required fields reference
  • example/knowledge/service-desk-plus-sse-implementation.md - SSE server details

API Documentation

  • Main Documentation: https://www.manageengine.com/products/service-desk/sdpod-v3-api/
  • OAuth Guide: https://www.manageengine.com/products/service-desk/sdpod-v3-api/getting-started/oauth-2.0.html

🔑 OAuth Configuration

Required Environment Variables

# Service Desk Plus Configuration
SDP_BASE_URL=https://helpdesk.yourdomain.com   # Custom domain
SDP_INSTANCE_NAME=itdesk                       # Instance name
SDP_PORTAL_NAME=yourportal                     # Portal name
SDP_DATA_CENTER=US                             # Data center (US, EU, IN, AU, JP, UK, CA, CN)

# OAuth Credentials
SDP_OAUTH_CLIENT_ID=your_client_id
SDP_OAUTH_CLIENT_SECRET=your_client_secret_here
SDP_OAUTH_REFRESH_TOKEN=your_permanent_refresh_token_here

# Optional: Use mock API for testing
SDP_USE_MOCK_API=false

OAuth Setup Steps

  1. Create a self-client OAuth app in Service Desk Plus
  2. Generate authorization code with required scopes
  3. Exchange code for permanent refresh token
  4. Configure .env with credentials

See docs/OAUTH_SETUP_GUIDE.md for detailed instructions.

🏗️ Architecture

Current Implementation (Single-Tenant)

  • Direct MCP protocol implementation over SSE
  • OAuth tokens configured via environment variables
  • Singleton OAuth client prevents rate limiting issues
  • Smart token refresh only on 401 errors
  • Production-ready and fully tested

Future Multi-Tenant Architecture

When MCP protocol evolves to support stateless connections:

  • Multiple clients connecting to single server
  • Per-tenant OAuth token management
  • Complete tenant isolation
  • Database-backed token storage

🐛 Troubleshooting

Common Issues

  1. OAuth Rate Limiting
  • Error: "You have made too many requests continuously"
  • Solution: Wait 5-15 minutes, server implements proper token reuse
  1. Field Validation Errors (4012)
  • Error: Missing mandatory fields
  • Solution: Check instance configuration for required fields
  1. Priority Update Errors (403)
  • Error: "Cannot give value for priority"
  • Solution: This is an API limitation, priority may not be updatable
  1. Authentication Errors (401)
  • Error: "UNAUTHORISED"
  • Solution: Verify OAuth tokens and custom domain configuration

Debug Mode

# Enable debug logging
export DEBUG=sdp:*
./start-sse-server.sh

🤝 Contributing

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

🙏 Acknowledgments

  • ManageEngine for Service Desk Plus API
  • Anthropic for the Model Context Protocol
  • Claude Code for testing and integration

📞 Support

For issues and questions:

  • GitHub Issues: https://github.com/PTTG-IT/SDP-MCP/issues
  • Documentation: Check example/knowledge/ folder
  • API Reference: https://www.manageengine.com/products/service-desk/sdpod-v3-api/

---

Note: This is for Service Desk Plus Cloud (SDPOnDemand), not on-premises installations.

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Cloud & DevOps servers.