Freshservice MCP Server
Overview
A powerful MCP (Model Control Protocol) server implementation that seamlessly integrates with Freshservice, enabling AI models to interact with Freshservice modules and perform various IT service management operations. This integration bridge empowers your AI assistants to manage and resolve IT service tickets, streamlining your support workflow.
Key Features
- Enterprise-Grade Freshservice Integration: Direct, secure communication with Freshservice API endpoints
- AI Model Compatibility: Enables Claude and other AI models to execute service desk operations through Freshservice
- Automated ITSM Management: Efficiently handle ticket creation, updates, responses, and asset management
- Workflow Acceleration: Reduce manual intervention in routine IT service tasks
Supported Freshservice Modules
This MCP server currently supports operations across a wide range of Freshservice modules:
- Tickets
- Conversations
- Products
- Requesters
- Agents
- Agent Groups
- Requester Groups
- Canned Responses
- Canned Response Folders
- Workspaces
- Solution Categories
- Solution Folders
- Solution Articles
Components & Tools
The server provides a comprehensive toolkit for Freshservice operations:
Ticket Management
| Tool | Description | Key Parameters |
|---|---|---|
create_ticket |
Create new service tickets | subject, description, source, priority, status, email |
update_ticket |
Update existing tickets | ticket_id, updates |
delete_ticket |
Remove tickets | ticket_id |
search_tickets |
Find tickets matching criteria | query |
get_ticket_fields |
Retrieve ticket field definitions | None |
get_tickets |
List all tickets with pagination | page, per_page |
get_ticket |
Retrieve single ticket details | ticket_id |
Getting Started
Installing via Smithery
To install freshservice_mcp automatically via Smithery:
npx -y @smithery/cli install @effytech/freshservice_mcp --client claude
Prerequisites
- A Freshservice account (sign up at freshservice.com)
- Freshservice API key
uvxinstalled (pip install uvorbrew install uv)
Configuration
-
Generate your Freshservice API key from the admin panel:
- Navigate to Profile Settings → API Settings
- Copy your API key for configuration
-
Set up your domain and authentication details as shown below
Usage with Claude Desktop
- Install Claude Desktop from the official website
- Add the following configuration to your
claude_desktop_config.json:
"mcpServers": {
"freshservice-mcp": {
"command": "uvx",
"args": [
"freshservice-mcp"
],
"env": {
"FRESHSERVICE_API_KEY": "<YOUR_FRESHSERVICE_API_KEY>",
"FRESHSERVICE_DOMAIN": "<YOUR_FRESHSERVICE_DOMAIN>"
}
}
}
Important: Replace <YOUR_FRESHSERVICE_API_KEY> with your actual API key and <YOUR_FRESHSERVICE_DOMAIN> with your domain (e.g., yourcompany.freshservice.com)
Example Operations
Once configured, you can ask Claude to perform operations like:
- "Create a new incident ticket with subject 'Network connectivity issue in Marketing department' and description 'Users unable to connect to Wi-Fi in Marketing area', set priority to high"
- "Update the status of change request #45678 to 'Approved'"
- "List all critical incidents reported in the last 24 hours"
- "Show asset details for laptop with asset tag 'LT-2023-087'"
- "Create a change request for scheduled server maintenance next Tuesday at 2 AM"
Testing
For testing purposes, you can start the server manually:
uvx freshservice-mcp --env FRESHSERVICE_API_KEY=<your_api_key> --env FRESHSERVICE_DOMAIN=<your_domain>
Troubleshooting
- Verify your Freshservice API key and domain are correct
- Ensure proper network connectivity to Freshservice servers
- Check API rate limits and quotas
- Verify the
uvxcommand is available in your PATH
License
This MCP server is licensed under the MIT License. See the LICENSE file in the project repository for full details.
Additional Resources
Built with ❤️ by effy
Metadata
Release files for freshservice-mcp 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| freshservice_mcp-1.0.0.tar.gz | 18.9 kB | Without provenance | Details for freshservice_mcp-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| freshservice_mcp-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for freshservice_mcp-1.0.0-py3-none-any.whl |
Total release size: 33.3 kB
Release files / freshservice_mcp-1.0.0.tar.gz
| Download URL | freshservice_mcp-1.0.0.tar.gz |
|---|---|
| Size | 18.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
500ffe59245e0d23126dd415ab5f1e556622f1b835ebd80799298ba92746fe28
|
|
BLAKE2b-256 checksum How to use checksums |
4ca1961e5304d776b25c626998eed0141d4661d3052e8d8fc568d22d97de87bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.16
|
Release files / freshservice_mcp-1.0.0-py3-none-any.whl
| Download URL | freshservice_mcp-1.0.0-py3-none-any.whl |
|---|---|
| Size | 14.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
02b42f4e9f32b4830ab6958ee63b557a095a7cd41b5b19d9f38987967a2ced5a
|
|
BLAKE2b-256 checksum How to use checksums |
9f791b600b482101b3d1840c51e6c11b2f53e080a46e105a4ad00fe652aa87db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.16
|
Security for freshservice-mcp 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.