Skip to main content

Freshservice MCP Server

smithery badge

Overview

A powerful MCP (Model Context 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
  • Changes
  • 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, optional group_id, responder_id
update_ticket Update existing tickets ticket_id, updates
delete_ticket Remove tickets ticket_id
filter_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_by_id Retrieve single ticket details ticket_id

Change Management

Tool Description Key Parameters
get_changes List all changes with pagination page, per_page, query
filter_changes Filter changes with advanced queries query, page, per_page
get_change_by_id Retrieve single change details change_id
create_change Create new change request requester_id, subject, description, priority, impact, status, risk, change_type
update_change Update existing change change_id, change_fields
close_change Close change with result explanation change_id, change_result_explanation
delete_change Remove change change_id
get_change_tasks Get tasks for a change change_id
create_change_note Add note to change change_id, body

🚨 Important: Query Syntax for Filtering

When using get_changes or filter_changes with the query parameter, the query string must be wrapped in double quotes for the Freshservice API to work correctly:

✅ CORRECT: "status:3", "approval_status:1 AND status:<6"
❌ WRONG: status:3 (will cause 500 Internal Server Error)

Common Query Examples:

  • "status:3" - Changes awaiting approval
  • "approval_status:1" - Approved changes
  • "approval_status:1 AND status:<6" - Approved changes that are not closed
  • "planned_start_date:>'2025-07-14'" - Changes starting after specific date
  • "status:3 AND priority:1" - High priority changes awaiting approval

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
  • uvx installed (pip install uv or brew install uv)

Configuration

  1. Generate your Freshservice API key from the admin panel:

    • Navigate to Profile Settings → API Settings
    • Copy your API key for configuration
  2. Set up your domain and authentication details as shown below

Until group_id and responder_id are in the upstream freshservice-mcp release, install this fork from PyPI as freshservice-mcp-ids. The command name stays freshservice-mcp.

uvx --from freshservice-mcp-ids==1.1.1 freshservice-mcp

Usage with Claude Desktop

  1. Install Claude Desktop from the official website
  2. Add the following configuration to your claude_desktop_config.json:
"mcpServers": {
  "freshservice-mcp": {
    "command": "uvx",
    "args": [
        "--from",
        "freshservice-mcp-ids==1.1.1",
        "freshservice-mcp"
    ],
    "env": {
      "FRESHSERVICE_APIKEY": "<YOUR_FRESHSERVICE_APIKEY>",
      "FRESHSERVICE_DOMAIN": "<YOUR_FRESHSERVICE_DOMAIN>"
    }
  }
}

Important: Replace <YOUR_FRESHSERVICE_APIKEY> 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:

Tickets:

  • "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"
  • "List all critical incidents reported in the last 24 hours"
  • "Update ticket #12345 status to resolved"

Changes:

  • "Create a change request for scheduled server maintenance next Tuesday at 2 AM"
  • "Update the status of change request #45678 to 'Approved'"
  • "Close change #5092 with result explanation 'Successfully deployed to production. All tests passed.'"
  • "List all pending changes"

Other Operations:

  • "Show asset details for laptop with asset tag 'LT-2023-087'"
  • "Create a solution article about password reset procedures"

Testing

For testing purposes, you can start the server manually:

uvx freshservice-mcp --env FRESHSERVICE_APIKEY=<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 uvx command 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-ids 1.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for freshservice-mcp-ids 1.1.1
File Size Uploaded Provenance
freshservice_mcp_ids-1.1.1.tar.gz 32.8 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for freshservice-mcp-ids 1.1.1
File Interpreter ABI Platform
freshservice_mcp_ids-1.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 52.3 kB

Release files / freshservice_mcp_ids-1.1.1.tar.gz

Download URL freshservice_mcp_ids-1.1.1.tar.gz
Size 32.8 kB
Tags Source
SHA-256 checksum
How to use checksums
02e130d8621a2411eb7ca87b407856ad4fb2d13d2f45f80bbce2e2e061db275d
BLAKE2b-256 checksum
How to use checksums
4c3a0fe63523caa1196503ea0fbe35efa18e1b39495602337f68fd376b88ed5f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / freshservice_mcp_ids-1.1.1-py3-none-any.whl

Download URL freshservice_mcp_ids-1.1.1-py3-none-any.whl
Size 19.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a93862f4fa9c76a2ee6d4def2086af5f3b8534cffbdc16c9628432d18dc02c89
BLAKE2b-256 checksum
How to use checksums
9e6fba5b649912277ffe2ffbe38bd81552ca26ac595a65a08337cdf7796a635e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Security for freshservice-mcp-ids 1.1.1

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for freshservice_mcp_ids-1.1.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

1.1.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page