Provides integration with Atlassian products (beyond Jira) through a unified interface, handling authentication and API interactions.
Enables interaction with Jira instances through a unified API, providing capabilities for accessing issues, managing tickets, and integrating with Jira workflows.
Allows connection to Zendesk instances to manage tickets and support requests through a standardized interface that abstracts away Zendesk-specific API complexities.
MCP ITSM Integration
A Model Context Protocol (MCP) implementation for IT Service Management (ITSM) tools, designed to work with Smithery.
Overview
This project provides a unified interface for LLMs to interact with multiple ITSM systems (ServiceNow, Jira, Zendesk, Ivanti Neurons for ITSM, and Cherwell) using the Model Context Protocol (MCP). Instead of requiring LLMs to learn different APIs for each ITSM system, this integration provides a standardized set of tools that work across all systems.
MCP Server Information
This is an MCP-compliant server that implements the Model Context Protocol specification. It provides a standardized interface for Large Language Models to interact with multiple ITSM systems through a unified set of tools.
MCP Compatibility
Protocol Version: MCP 1.0
Tool Format: JSON Schema compliant
Runtime: Node.js
Transport: HTTP and stdio
Authentication: API key
MCP Server Usage
The server can be used directly with any MCP-compatible client, including:
MCP Inspector CLI tool
Claude via MCP integration
Any LLM with MCP support
To inspect the server locally:
Features
Unified Interface: Consistent tool definitions across all ITSM systems
Intelligent Routing: Automatically routes requests to the appropriate ITSM system
Context Management: Maintains context across interactions
MCP Compliant: Follows the Model Context Protocol specification
Smithery Integration: Designed to work seamlessly with Smithery
Prerequisites
Node.js (v14 or higher)
Smithery CLI
Access to ITSM systems (ServiceNow, Jira, Zendesk, Ivanti Neurons for ITSM, Cherwell)
Installation
Clone the repository:
git clone https://github.com/yourusername/mcp-itsm.git cd mcp-itsmInstall dependencies:
npm installConfigure your ITSM credentials (see Configuration section)
Deploy to Smithery:
smithery deploy
Configuration
ITSM Credentials
Create a .env
file with your ITSM credentials:
Smithery Configuration
The smithery.yaml
file configures how your tools are deployed to Smithery:
Available Tools
This integration provides the following tools:
create_ticket: Create a new ticket in any ITSM system
get_ticket: Retrieve ticket details
update_ticket: Update an existing ticket
list_tickets: List tickets with filtering options
assign_ticket: Assign a ticket to a user
add_comment: Add a comment to a ticket
search_knowledge_base: Search the knowledge base for relevant articles
See tools.json
for the complete tool definitions.
Usage
Once deployed to Smithery, LLMs can use these tools to interact with your ITSM systems. Here's an example of how an LLM might create a ticket:
Debugging
This project includes several debugging tools:
debug_smithery_mcp.bat
: Diagnoses MCP-specific issues with Smitheryforce_redeploy_smithery.bat
: Forces redeployment with MCP configurationtest_tools.js
: Tests MCP tool calls locally
Documentation
MCP Integration: Details of the Model Context Protocol implementation
MCP Quick Reference: Quick reference guide for MCP concepts
ITSM Systems Reference: Detailed information about each supported ITSM system
OpenAI to MCP Conversion: Guide for converting from OpenAI function calling to MCP
Diagrams
MCP ITSM Architecture: Overall architecture of the integration
System Fragmentation: The challenge of ITSM system fragmentation
LLM Reasoning: How LLMs select the appropriate ITSM system
Benefits Comparison: Comparison of traditional vs. MCP approach
Smithery Integration: How MCP integrates with Smithery
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Resources
This server cannot be installed
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
MCP FOR ITSM TOOL INTEGRATION
- Overview
- MCP Server Information
- Features
- Prerequisites
- Installation
- Configuration
- Available Tools
- Usage
- Debugging
- Documentation
- Diagrams
- Contributing
- License
- Resources
Related Resources
Related MCP Servers
- MIT License
- MIT License