Freshservice Operational Integration Hub (MCP Implementation)

Overview

This package establishes a robust Model Control Protocol (MCP) endpoint designed to interface directly with the Freshservice ecosystem. It facilitates programmatic control over core IT Service Management (ITSM) functions, allowing sophisticated AI reasoning engines to autonomously handle incident processing, service request fulfillment, and configuration item tracking within your Freshservice instance.

Core Capabilities

Direct Freshservice API Conduit: Provides secure, low-latency communication pathways to Freshservice's backend infrastructure.
Generative AI Enablement: Empowers large language models (like Claude) to initiate and modify Freshservice records and data.
Automated ITSM Lifecycle Management: Facilitates end-to-end handling of service requests, encompassing creation, status transition, resolution notes, and associated asset linkage.
Efficiency Enhancement: Significantly reduces the necessity for manual data entry and routine administrative tasks performed by support staff.

Supported Freshservice Subsystems

The integration toolset currently spans a comprehensive set of Freshservice functional areas:

Service Requests & Incidents (Tickets)
Inter-Agent/Customer Communication Logs (Conversations)
Service Catalog Offerings (Products)
End-User Management (Requesters)
Support Personnel (Agents & Agent Groups)
Customer Segments (Requester Groups)
Standardized Reply Templates (Canned Responses & Folders)
Organizational Contexts (Workspaces)
Knowledge Base Structure (Solution Categories, Folders, and Articles)

Available Functionality (Toolset)

The server exposes the following methods for external invocation:

Ticket Manipulation Functions

Tool	Purpose	Mandatory Inputs	Optional Inputs
`create_ticket`	Initiate a new support record	`subject`, `description`	`source`, `priority`, `status`, `email`
`update_ticket`	Modify an existing ticket's properties	`ticket_id`, `updates` (JSON object)	N/A
`delete_ticket`	Permanently erase a service record	`ticket_id`	N/A
`search_tickets`	Execute customized filtering on tickets	`query` (Freshservice search syntax)	N/A
`get_ticket_fields`	Fetch schema definitions for ticket forms	None	N/A
`get_tickets`	Retrieve paginated lists of tickets	`page`, `per_page`	N/A
`get_ticket`	Fetch granular details for a single record	`ticket_id`	N/A

Deployment and Configuration

Installation via Smithery CLI

Use the Smithery command-line utility for rapid setup:

bash npx -y @smithery/cli install @effytech/freshservice_mcp --client claude

Prerequisites Checklist

Active Freshservice subscription (obtainable from freshservice.com)
A valid, non-expired Freshservice API Access Token.
The uvx runtime environment installed (pip install uv or equivalent).

Credential Setup

API Key Acquisition: Navigate to the administration settings within your Freshservice portal (Profile Settings -> API Settings) and generate/copy your token.
Environment Definition: Configure the necessary authentication and domain pointers.

Integration within Claude Desktop

To enable the AI client to utilize this service, incorporate the following structure into your claude_desktop_config.json file:

"mcpServers": { "freshservice-mcp": { "command": "uvx", "args": [ "freshservice-mcp" ], "env": { "FRESHSERVICE_APIKEY": "", "FRESHSERVICE_DOMAIN": ".freshservice.com" } } }

Mandatory: Substitute <YOUR_GENERATED_API_KEY> and <YOUR_INSTITUTION_SUBDOMAIN> with your actual credentials and domain name.

Operational Examples

After successful setup, interact with Claude using natural language requests such as:

"File a new Level 1 incident ticket concerning marketing team Wi-Fi failure. Priority must be set to High and the description should detail user inability to access shared drives."
"Change the lifecycle state of change request ID 45678 to 'Authorized for Deployment'."
"Display all high-severity operational alerts logged within the last calendar day."
"Lookup configuration details associated with CI asset tag LT-2023-087."
"Draft a change proposal for essential system patch deployment scheduled for the upcoming Tuesday at 02:00 UTC."

Local Server Activation

For testing or direct execution, use this command line invocation:

bash uvx freshservice-mcp --env FRESHSERVICE_APIKEY= --env FRESHSERVICE_DOMAIN=

Troubleshooting Guide

Confirm the integrity of the API key and the correct domain format.
Verify network pathways are open to Freshservice endpoints.
Monitor API call quotas to avoid throttling.
Ensure uvx is correctly initialized and accessible in the system PATH.

Legal & Credits

Distributed under the permissive MIT License. See the repository's LICENSE file.

References

Developed by effy

freshservice_operational_integration_hub

Author

effytech

Quick Info

Actions

Tags